Snap2Park App Privacy Disclosure
Last updated: April 14, 2026
This page describes how Snap2Park handles data using terminology that more closely follows Apple's App Store privacy-label categories. Snap2Park helps users scan UK parking signs, decode restrictions, save parked locations, manage vehicle reminders, and optionally remove ads. This disclosure should be read together with our website Privacy Policy.
For App Store privacy-label purposes, data that stays on device and is not transmitted off device is generally not treated as "collected." This page distinguishes on-device processing from data that may be collected off device by us or our third-party partners.
1. Summary
- Data used for tracking: We do not intend Snap2Park data to be used for tracking as implemented.
- On-device only and not normally "collected": parked-location data, saved vehicles and notes, reminder schedules, consent state, and most app preferences.
- Data that may be collected off device: cloud OCR requests, consent-based analytics, training-sample sync, scan-result uploads, DVLA lookup requests, app-store purchase validation data, and third-party advertising data where ads are enabled.
- Data linked to device-generated identifiers: analytics and scan-upload records may be associated with installation or session identifiers when those features are enabled.
2. Apple Privacy-Label Oriented Summary
| Apple data type | Examples | When collected off device | Likely App Store purpose |
|---|---|---|---|
| Photos or Videos | Parking sign images captured with the camera or chosen from the photo library | When cloud OCR fallback is used instead of fully on-device processing | App Functionality |
| Other User Content | Recognized sign text, scan mode, decoded rules, parking summary, matched rules | When analytics is enabled and backend endpoints are configured for telemetry or scan uploads | App Functionality, Analytics |
| Precise Location | Current parked location coordinates and accuracy | Current reviewed implementation keeps this on device for the parking-location feature | On-device feature use only |
| Other Data Types / request data | Vehicle registration numbers used for DVLA lookups and locally stored vehicle records | When you request vehicle-detail lookups from DVLA services | App Functionality |
| User ID | Anonymous analytics user IDs, session IDs, and scan-upload installation IDs | When analytics, telemetry, or scan-upload features are enabled | Analytics, App Functionality |
| Product Interaction | Feature usage, tab changes, function usage, and scan outcomes | When analytics is enabled and consent is valid | Analytics |
| Diagnostics | App errors, warnings, exception-style telemetry, and diagnostic logs | When analytics or telemetry backends are configured and enabled | Analytics, App Functionality |
| Purchase History | No-ads purchase state, restore-purchase checks, and optional receipt-validation payloads | When you purchase, restore, or validate premium entitlement | App Functionality |
| Advertising Data | Ad requests and ad-delivery related data handled by Google AdMob | When ads are enabled and the AdMob SDK is active | Third-Party Advertising |
3. On-Device Data That Is Not Normally "Collected"
The current reviewed implementation keeps several data types on device unless a separate upload or service request is triggered. This includes saved parked locations, locally stored vehicle records, reminder schedules, consent records, locale and theme settings, and similar local preferences.
If a future version starts transmitting any of this data to our servers or a third-party partner beyond the immediate servicing of a request, the App Store disclosure position may change.
4. Photos, Camera, and OCR
Snap2Park asks for camera or photo-library access only so you can scan parking signs. Where native on-device text recognition is available, sign text is processed on the device. In some environments, Snap2Park can fall back to a cloud OCR provider. When that fallback is used, the selected image is sent to the OCR service to extract text.
Cloud OCR may use a service key configured by us or a key supplied in the app settings by a developer or tester. If you do not want images processed remotely, do not use cloud OCR fallback.
5. Location and Maps
Snap2Park requests foreground location access only when you use the feature to save your parked location. The app records latitude, longitude, accuracy, and saved time so it can show you where you parked. In the current reviewed implementation, this data is stored on your device for app use and is not reported to our backend for analytics or advertising.
6. Vehicle Data and DVLA Lookups
If you add vehicles to Snap2Park, the app stores registration numbers and any service, insurance, or accident notes you enter on your device. When vehicle-detail features are used, Snap2Park may send a registration number to the DVLA Vehicle Enquiry Service to retrieve information such as make, fuel type, MOT status, and tax due dates.
Retrieved vehicle dates may also be stored locally so the app can schedule reminder notifications.