Current implementation

Tinwheel privacy information

This page describes what the current app does with car photos and saved result records. It separates repository evidence from arrangements that still need owner confirmation.

Recognition is currently blocked. The current guest photo flow is browser-local.

01 · Selection

Local in the browser

JPEG, PNG, and WebP files up to 10 MB are checked in the browser and previewed with a browser-local object URL.

02 · Recognition

No photo upload

The availability check is an empty request. It does not accept, upload, or forward the selected image.

03 · Results

Structured records

Saved results are records about a result, not the original car photo.

How the current photo flow works

When you select a photo, Tinwheel validates its file type in the browser. The current guest flow accepts JPEG, PNG, and WebP files up to 10 MB. The selected image is previewed through a browser-local object URL, so the preview is created on your device.

If you ask Tinwheel to check recognition availability, the app sends an empty availability-check request. The selected photo is not included in that request. Recognition is blocked because no owner-approved make-and-model provider is configured. The current flow therefore does not accept, upload, or forward the selected photo, and it does not claim a recognition result.

Third-party recipients

No configured recognition provider or other third-party service receives car photos in the current implementation. The repository does not establish a hosting or infrastructure provider, processing vendor, data location, or future provider arrangement for car photos. Those details are pending owner confirmation.

Saved results and retention

Saved results are structured app records rather than original images. Fields can include the make, model, visible color, uncertainty and uncertainty details, ownership linkage, and timestamps such as when a result was collected or added to a garage. The current result record does not contain the original photo.

Authenticated delete controls remove the app record owned by the signed-in user. The repository establishes no automatic expiry for saved results. It also does not establish an exact operational, log, or backup retention period, or deletion from those systems. Those retention and deletion arrangements are pending owner confirmation.

Training use

Car images are not used for training without explicit user opt-in. Current repository evidence shows that recognition is blocked, no model has been trained from an approved dataset, and no active product photo-training use is configured. The recorded baseline also says no unapproved data was used.

Details awaiting confirmation

Legal operator: The legal name of the operator is pending owner confirmation.
Processing and hosting providers: No recognition provider is configured. The repository does not establish infrastructure providers, processing vendors, or their locations; any future arrangement is pending owner confirmation.
Operational, log, and backup retention: The repository establishes no exact retention period and no process for deleting copies from logs or backups. These arrangements are pending owner confirmation.
Other policy arrangements: Legal basis, data-subject request handling, international transfers, and any future recognition-provider terms are pending owner confirmation.
Privacy contact: tinwheel@polsia.app is the supplied Tinwheel contact address. The legal entity responsible for the service remains pending owner confirmation.