Snap2Park App Privacy Disclosure
Last updated: 25 September 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: Snap2Park does not use your data to track you across other companies' apps or websites, and does not ask for App Tracking Transparency permission.
- 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 and diagnostics, scan-result uploads, DVLA lookup requests, app-store purchase validation data, and advertising data handled by Google AdMob.
- Data linked to device-generated identifiers: analytics and scan-upload records are associated with random installation and session identifiers when you have turned analytics on.
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 on-device text recognition is unavailable and the app uses cloud OCR instead | App Functionality |
| Other User Content | Recognized sign text, scan mode, decoded rules, parking summary, matched rules | When you have turned analytics on | App Functionality, Analytics |
| Precise Location | Current parked location coordinates and accuracy | Not collected by us; kept on your 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 you have turned analytics on | 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 you have turned analytics on | 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 | Whenever ads are shown (unless you have bought the no-ads upgrade) | 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 on-device text recognition is available, sign text is read on your device and the image is not sent anywhere. Where it is not available, Snap2Park uses cloud OCR instead: the selected image is sent to our cloud service (hosted on Microsoft Azure), which passes it to our OCR provider, OCR.space, to extract the text. The app shows which OCR mode was used for each scan.
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. This data is stored on your device and is not sent to us or used for analytics or advertising.
When the app shows your parked location on a map, the map is provided by Apple Maps on iOS and Google Maps on Android. To draw the map, your device downloads map tiles for the area being shown from Apple or Google, which can reveal the general area you are viewing to them. If you choose to open directions, the location is passed to the maps app you select.
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 sends the registration number, through our cloud service, 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.
7. Identifiers, Analytics, Diagnostics, and Scan Uploads
When you first open Snap2Park, a consent screen asks you to accept the data and advertising terms needed to use the app, and lets you choose separately whether to turn on analytics. Analytics is off unless you turn it on, and you can turn it off at any time in Settings. While analytics is off, no analytics events, diagnostics, or scan uploads are sent.
If you turn analytics on, Snap2Park sends product-interaction events (such as screens and features used), app errors and error logs, sanitised OCR training samples, and scan-result records to Microsoft Azure Application Insights and to our cloud service hosted on Microsoft Azure. Training samples and scan-result records include the recognised sign text, scan mode, app language, the decoded parking outcome, and matched-rule summaries. They do not include the sign image or your location.
These records use random identifiers generated on your device, such as session and installation IDs. They do not contain your name or an account profile, but in App Store terms they may be treated as data linked to your device. They are used for product improvement and diagnostics, not for advertising profiles.
Snap2Park also keeps an app log on your device. It leaves your device only if you export it yourself from Settings.
8. Advertising and In-App Purchases
Snap2Park displays Google AdMob banner, full-screen, and app-open adverts unless you have bought the no-ads upgrade. Snap2Park requests non-personalised ads only. Even so, to deliver and measure these ads, Google AdMob and its advertising partners may process data such as your device's advertising identifier, IP address (which can indicate your approximate location), general device information, and ad interaction data under their own privacy terms.
If you buy or restore the no-ads upgrade, the purchase is processed by the App Store or Google Play. Snap2Park sends the purchase receipt to our cloud service so it can confirm the purchase with Apple or Google.
9. Notifications
If you grant notification permission, Snap2Park can schedule local reminders for parking sessions and vehicle MOT or tax dates. These notifications are generated by the app on your device from the dates and settings stored there; they are not sent from our servers.
10. Data Sharing
Depending on the features you use, data may be shared with the following services:
- Microsoft Azure, which hosts our cloud service and Application Insights, for cloud OCR, DVLA lookups, purchase validation, and (if you turn analytics on) analytics, diagnostics, and scan uploads.
- OCR.space, for cloud text recognition when on-device recognition is unavailable.
- The DVLA Vehicle Enquiry Service, when you request vehicle details.
- Google AdMob, for ad delivery.
- Apple Maps or Google Maps, for displaying maps.
- Apple App Store or Google Play, for in-app purchase processing and restoration.
- Expo (our app update service), which the app contacts to check for updates, receiving technical information such as the app version and platform.
Snap2Park also downloads the list of UK bank holidays from GOV.UK; no personal data is sent with that request. We do not sell personal data.
11. Tracking
Snap2Park does not use collected data for tracking as Apple defines that term, such as linking app data with third-party data for targeted advertising or advertising measurement across other companies' apps or websites. It does not ask for App Tracking Transparency permission, and it requests non-personalised ads only.
12. Retention and Controls
Data stored on your device stays there until you delete it in the app, clear the app's data, or uninstall the app. In Settings you can turn analytics off, withdraw your consent, and clear stored analytics records and training samples. Analytics, diagnostic, and scan-upload records that have already been sent are kept only as long as needed for product improvement and diagnostics. OCR images and DVLA lookups are processed to answer your request.
13. UK and EU Privacy Rights (GDPR)
If the UK GDPR or EU GDPR applies to you, you may have rights relating to your personal data, including rights to access, correct, erase, restrict, or object to certain processing, to request portability where applicable, and to withdraw consent at any time. You can withdraw consent for analytics by turning analytics off in Settings. You also have the right to complain to your local data protection authority; in the UK, this is the Information Commissioner's Office (ICO).
14. Contact
For questions about Snap2Park privacy, contact:
Softkey Solutions Ltd
Email: privacy@softkeylabs.com
Website: www.softkeylabs.com