Privacy in this preview
A description of the current implementation. Operator contact details and a final privacy notice must be completed before public launch.
Design data
The server stores uploaded artwork, saved project settings, names and generated exports in its configured data directory. Browser storage keeps draft settings and pending generation identifiers. An HTTP-only session cookie associates guest data with your browser and is configured to last up to one year.
Accounts and AI
Account providers and AI are not connected in the current preview. If account configuration is enabled, authentication is handled through Supabase and configured sign-in providers. If AI is enabled, your prompt and any selected reference image are sent to the configured image-generation provider. Their policies also apply.
Public versus private
Projects start private. Publishing copies the selected artwork and design settings into the community collection. Community listings expose design names, vehicle details, publish dates and aggregate likes/views, rather than private project history or prompts. Voter and daily viewer identifiers are hashed and kept server-side. One like is recorded per account; detail views are deduplicated per browser/account each day. Other users may download or remix published artwork.
Storage, retention and deletion
There is currently no automatic retention schedule or self-service account/data deletion tool. Clearing browser storage does not delete server files and may remove your access to guest projects. Ask the preview operator to remove stored data; downloaded copies held by other users cannot be recalled.
Operational data
Session identifiers support ownership checks and request limits. The host may keep operational logs. No advertising tracker has been intentionally added to this application. A complete review of hosting, providers, retention and contact details is required before public launch.