Built for spotting. Not tracking.
SeenCars starts with private collections and strict product boundaries around plates, owners, and public location output.
Your saved spots start private.
When you ask SeenCars to identify a car, the original photo you selected is uploaded and sent to OpenAI through a temporary access link. It may include people, number plates, surroundings, location or camera metadata. The original is not first processed by the saved-image redaction step.
After recognition, SeenCars creates a separate image for display. That derivative has EXIF metadata removed and the service attempts to blur detected faces and number plates. Detection can miss details or blur the wrong area, so do not rely on this derivative to protect the identity of everyone in the original photo.
You can use a photo's location, allow device location, or continue without coordinates. Exact coordinates are private. A spot saved without coordinates remains private and is not eligible for location-based rewards. Plate text, VINs and vehicle-owner identities are not looked up.
Read the current Privacy Notice and Terms of Use for the formal rules that apply to the beta.
Private by default
A new collection is not published as a public activity feed.
Redacted display derivative
Plate and face detection is attempted after recognition; it can miss or misidentify details.
No owner lookup
SeenCars identifies vehicles, not the people connected to them.
No public map or feed
The current beta does not publish a public map or activity feed.
Limited service analytics. No advertising tracking.
SeenCars measures launch and camera timings, photo-quality check outcomes, first opening and onboarding completion to improve performance and usability. Events use a random installation identifier; onboarding completion can be linked to your account. Event properties exclude photos, precise location and free-text content.
Events stay in SeenCars' backend and database and are not forwarded to a separate analytics provider. Weekly recap notifications respect your Profile preference and appear in the in-app inbox. Read the Privacy Notice for collected fields, retention and your rights.
Public output requires different safeguards.
Public map and community feed features are planned only after enough public spot data exists and separate safety, moderation, delay, precision, suppression, and privacy controls are approved.
Public output is intended to use delayed and privacy-safe location derivatives rather than expose a live exact map.
This page summarizes the product approach. The current Privacy Notice and Terms of Use are available on the SeenCars app site.