OV-fiets Beschikbaarheid Security & Privacy Scorecard
Android
User location is used to display nearby OV-fiets station availability via Google Maps. The app collects no personal account data and shares nothing with advertising or marketing services. Map interactions go to Google Play Services, which is standard for any app showing a map.
Best for
Daily OV-fiets users who want quick bike availability checks
Findings
- 0 critical
- 0 high
- 0 medium
- 1 low
- 2 info
1 issue identified across security and privacy analysis.
Top security issues
- Android Backups Enabled Without Exclusions
Top privacy issues
- Google Maps API Key Visible in APK
Full analysis
OV-fiets Beschikbaarheid
nl.ovfietsbeschikbaarheid | Version 3.7.0 | Scanned: March 10, 2026
Security: 99/100 | Privacy: 100/100
What This Means for You
User location is used to display nearby OV-fiets station availability via Google Maps. The app collects no personal account data and shares nothing with advertising or marketing services. Map interactions go to Google Play Services, which is standard for any app showing a map.
Recommendation: Very Secure
Best For: Daily OV-fiets users who want quick bike availability checks
Key Findings
Data Security - 1 finding (1 low)
Network Security - 0 findings
Code Safety - 0 findings
Privacy - 0 findings
Privacy Concerns
What Data is Collected
Device location is used solely to show nearby OV-fiets station availability on the map. No account details, names, or usage history are stored by the app.
Third-Party Data Sharing
Google Play Services receives location data to render the map. No data is shared with advertising, marketing, or analytics services.
Understanding the Scores
- Security: 99/100
- Privacy: 100/100
- Data Security: 99/100
- Network Security: 100/100
- Code Safety: 100/100
- Data Collection: 100/100
- Data Sharing: 100/100
- User Control: 100/100
Positive Security Features
- No advertising or marketing service integrations
- Minimal data collection limited to what is needed for map display
- No behavioral tracking or user profiling
Areas for Improvement
- Location data sent to Google Maps is subject to Google's own privacy practices. Reviewing device-level Google location settings provides additional control over how this data is used.
- A low-priority improvement in local data handling could further reduce the already-minimal chance of any data exposure on the device.
About This Analysis
This scorecard is based on static analysis of the app's code and configuration. Results reflect practices observed as of the scan date.
App Details
- Package: nl.ovfietsbeschikbaarheid
- Version: 3.7.0 (build 28)
- Developer: Not listed
- Scan Date: March 10, 2026
- Third-Party Services: Google Play Services (Maps), Ktor HTTP Client, Koin, Compass, AndroidX Jetpack, Kotlin stdlib + Coroutines
Versions & scan history
| Scan | Date | Overall score |
|---|---|---|
| #1 (current) | 100/100 |