Privacy Policy
How Flying Car AI handles car photos, accounts, payments and completed videos.
Last updated: October 18, 2026
Who operates this service
Flying Car AI is operated by the Flying Car AI team. Contact support@flying-car-ai.com with questions or privacy requests.
Your photos and videos
We use your uploaded photograph with the fixed Ramp Stunt motion reference to process your requested video. Uploaded photos are automatically deleted 24 hours after upload. Completed videos are retained for 14 days after completion, then automatically deleted. Download your finished MP4 during that period if you want to keep it.
These periods apply to files stored by Flying Car AI. Account, order and task metadata have separate retention where needed for your account, security, purchase refunds and recordkeeping. A generation provider receives the media access needed to fulfill the request and processes information under its own policies.
Temporary browser drafts
Your browser keeps a temporary photo draft, video quality and permission choice so they can survive sign-in and checkout in the same tab. Drafts expire after 24 hours and expired drafts are removed when the site next opens its draft storage. A draft is cleared after a generation is accepted. This local draft is separate from the server-upload retention period.
Your selected credit pack and checkout request reference are kept temporarily in tab session storage to resume checkout and avoid duplicate requests. Browser storage settings can prevent this feature; the interface then provides an explanation and a way to retry.
Accounts and service providers
Google sign-in supplies the account details needed to identify you, such as your email address, name and profile image. We use them to maintain your credit balance, orders and generation history. Authentication cookies keep your session active.
Cloudflare provides hosting and storage. KIE supplies access to the video-generation model. Waffo processes payments. Information necessary for the requested service is shared with the relevant provider. Payment-card details are handled by the payment provider rather than stored as complete card information in this application.
Operational diagnostics and analytics
The diagnostic system records limited events such as photo and quality choices, credit-pack views and clicks, sign-in, checkout creation, task status and download requests. Random browser and journey references help connect the steps; signed-in server records can be linked to internal account and order references. Hosting can provide an approximate country, while sanitized campaign labels and referring hostnames identify visit sources.
These records exclude photo content, filenames, raw IP addresses, account email addresses, passwords, authentication codes, full card information, payment tokens, full checkout URLs and raw error messages or stack traces. Limited error categories, application asset names, line and column numbers and request references help diagnose failures. Operational access is restricted to authorized administrators. Diagnostic events cannot authorize a payment or generation.
Optional analytics are enabled only with the applicable site settings and consent controls. An explicit analytics refusal stops optional browser journey tracking. Essential account, order and task records still support the service you request. Media-deletion periods are separate from analytics and transaction-record retention.
Your choices
You can clear temporary browser data through your browser settings and download completed videos during their retention period. Email support@flying-car-ai.com to request access, correction or account deletion, or to ask a privacy question. Use the account email so ownership can be verified. Some transaction records may need to be retained for legal or accounting obligations. Do not send passwords or full payment-card details.