Effective August 6, 2026
Privacy Policy
This policy describes the current private field-test build of Car App, a working-title mobile application developed by Simon Crowner.
Field-test scope: the current build operates locally on the tester's device. It does not contain production vehicle identification, cloud accounts, advertising, analytics, or remote image processing. This policy will be updated before any version introducing those services is distributed.
1. Who is responsible
Car App is currently developed and operated by Simon Crowner. “Car App” is a temporary working title used for private testing.
Privacy contact: farmshorts123@gmail.com
2. Information used by the current app
Camera and photographs
The app requests camera access so a tester can photograph a vehicle. Accepted photographs are stored locally on the device as an Original Sighting associated with the tester's collection.
Collection and profile information
Prototype collection records, progress, favorites, profile preferences, and Showroom selections are stored locally on the device. The current build does not create an online account or public profile.
Device permissions
The current app requests camera access for its capture feature. It does not request precise location for the field-test experience described by this policy.
3. Information not transmitted by the current app
The current private field-test build does not transmit photographs, collection records, profile information, or identifiers to a Car App server. It does not use third-party advertising or product-analytics SDKs. Vehicle-identification results in this build are development fixtures rather than remote analysis.
Apple, Google, mobile carriers, and device manufacturers may process app-store, operating-system, crash, or device information under their own policies. That processing is controlled by those providers rather than Car App.
4. Sharing
The app can ask the operating system to share a privacy-safe collectible export when the tester chooses that action. The tester selects the destination and controls the resulting copy. The export is designed not to include the Original Sighting, precise location, or hidden photo metadata.
5. Retention and deletion
Locally stored app records and photographs remain on the device until they are removed through available app or operating-system controls, the application data is cleared, or the app is uninstalled. Copies may remain in device backups controlled by Apple, Google, or the tester. Shared exports remain wherever the tester chose to send or save them.
Because the current build does not create a Car App server account, Car App does not hold a server-side account record to delete.
6. Security
The current field build reduces exposure by keeping prototype data on the device. Device security, backups, and access remain the tester's responsibility. No method of storage is completely secure.
7. Future processing
Production identification, privacy processing, cloud storage, accounts, subscriptions, or analytics are not covered as active features by this version of the policy. Before any such feature is released, this policy and the applicable in-app notices and app-store disclosures will be updated to identify the data involved, its purpose, service providers, retention, sharing, and user controls.
8. Changes to this policy
Material changes will be published on this page with a revised effective date. Testers may also receive an in-app or testing-channel notice when a change affects how their information is handled.
9. Questions
Privacy questions can be sent to farmshorts123@gmail.com.