Back to home

Privacy Policy | Livery Generator

How Livery Generator handles car photos, prompts, generated images, private storage, third-party processing and deletion requests.

Last updated: 2026-11-12

Current service

Livery Generator is an online service for exploring car livery concepts. Image generation is available during a limited pilot while capacity remains; paid checkout is not open. One successful concept is free per browser visitor without signup. The maker shows current availability before you submit. This policy describes the current deployment.

Photos, prompts and results

A selected car photo stays in your browser until you submit it. Our Cloudflare Worker checks the file, converts it to JPEG, removes embedded metadata such as EXIF, and saves the cleaned image in a private Cloudflare R2 bucket. We store the style, color, creative direction, task status, anonymous visitor identifier and related task metadata in Cloudflare D1. Generated images are saved in the private R2 bucket. We do not automatically publish your original photo or result.

A random livery_visitor cookie identifies the browser that owns a task and tracks its one free concept. Newly issued cookies last up to one year and are marked HttpOnly and SameSite=Strict; on HTTPS they are also marked Secure. Existing cookies keep their original expiry until replaced. Clearing cookies or using another browser creates a new visitor identity. The API lets only the matching visitor retrieve a private image or result while it is available. If you register, the authentication system also stores account information in the site database.

External image processing

When generation is available and you explicitly submit a photo with consent, we send the cleaned photo and an editing prompt to deeprouter.top for processing by gpt-image-2. Text-only and model-based requests send the prompt without an uploaded photo. We receive the generated image in the provider response. We do not use uploaded photos to train a model of our own. We have not verified the provider's retention period or whether it uses submitted data for training, so we cannot promise that the provider does not retain or train on it. Do not submit an image if that uncertainty is unacceptable to you.

Access and deletion

The application stops serving an uploaded original after 24 hours and a generated image after seven days. An hourly scheduled cleanup removes expired private R2 images and their asset records. A separate R2 lifecycle rule is configured to expire objects under livery/ after eight days; deletion timing may vary. Job records, prompts and free-usage counters remain in D1 without a configured deletion deadline. Provider copies, if any, are outside this cleanup process.

To request a review or deletion of site data, use the signed-in support tickets page and include the result ID if you have it. We do not yet offer a self-service deletion button or a fixed response time. Clearing the visitor cookie may prevent us from matching an anonymous task to your browser, so keep the result ID if you need help with it.

Faces and license plates

The app does not automatically detect or blur faces and license plates. Check the photo and blur those details yourself before uploading. The upload form requires you to confirm this check; that confirmation does not perform image masking.

We will update this policy if storage, providers, retention, account features or payment handling change.