Privacy Policy

When you create an account, we collect:

• Your name (or chosen display name)
• Your email address
• Authentication credentials (managed by Supabase Auth)
• Optional profile information you choose to provide (organization name, avatar, etc.)

When you subscribe to a paid tier or make a one-off purchase, our payment processor Stripe collects payment card details, billing address, and transaction history.

Filmion does not directly store payment card numbers. Stripe processes payments and we receive only tokenized references, billing receipts, and transaction status.

When you upload User Content (prompts, reference images, reference videos, audio files, product assets, brand materials), we collect and store that content to provide the Service to you. User Content ownership and licensing is governed by the Terms of Service.

When the Service produces Generated Output in response to your prompts, we store the output in your account. Generated Output that meets specific reusability criteria may be incorporated into a shared library where it serves as a starting reference for other users' generations (see Section 4.4).

When you use the Service, we automatically collect:

• IP address (used for security, abuse prevention, and approximate geographic localization)
• Browser type, operating system, device identifier
• Pages viewed, features used, time of access
• Generation operations performed (which engine, which template, credit cost)
• Errors and crash reports (collected via Sentry)
• Cookies and similar technologies (see Section 7)

On the Clips page you can connect accounts you own — Google Drive and Dropbox to import your own videos; YouTube, TikTok, Instagram and Facebook only to post your clips (we do not import from them) and any other finished video you make in Filmion. You can connect several accounts on the same platform; each is its own connection. Each connection is your own sign-in on that company's page; we never see a password. We store an encrypted access key per connection (AES-256-GCM, key held outside the database), the account or channel name, picture and ID, and the list of items you pick from. The video you pick is copied to Cloudflare Stream so we can cut it and deleted 72 hours after import. Account and channel details are refreshed or deleted within 30 days; everything from a connection is deleted within 7 days of you disconnecting or revoking it.

Posting, scheduling and Auto-post. For each post you make, schedule or queue with Auto-post, we keep which video it is (a clip, a Filmion Edit export or a video you generated), the account it goes to, the title, description, hashtags and who-can-see-it you set (or your Auto-post settings with the clip's title filled in), the time it is due, whether you or Auto-post created it, its status, and once it is posted, the platform's post ID and link. For each Auto-post setting we keep the account it is for, your chosen settings and a record of when you turned it on or off and the wording you agreed to. For videos posted to YouTube, we read each video's view count once a day through the same connection and show it only to you, marked as coming from YouTube. We keep only the latest count, and we never use view counts to rank or choose clips, to train AI, or for anything else.

How long we keep it. Waiting and posted records are kept while the video is in your library. Cancelled and failed posts are deleted after 90 days. View counts are deleted when you disconnect YouTube, when YouTube stops returning the video, or if we cannot refresh them for 30 days. When you disconnect an account, its waiting posts are cancelled, its Auto-post setting is deleted, and the platform's post IDs and links for that account are deleted within 7 days (we keep only "posted to [platform] on [date]"). Records of your Auto-post choices are kept while you have an account and for 4 years after, as proof of what you asked us to do.

Why (EU/UK). Posting, scheduling, Auto-post and view counts are needed to perform our contract with you (GDPR Art. 6(1)(b)). The record of your Auto-post choices serves our legitimate interest in proving your instruction (Art. 6(1)(f)).

Filmion's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use it only to show you your own files and channels, to import or post the item you choose, and to show the view counts of the videos you posted. We do not sell it, use it for advertising, let humans read it (except with your permission or for security or legal reasons), or use it to train AI. Filmion uses YouTube API Services; Google's Privacy Policy applies to the data Google shares with us, and you can revoke our access at security.google.com/settings/security/permissions. Meta, TikTok and Dropbox data is used the same way and deleted on disconnect. Lawful basis in the EU/UK: performance of our contract with you (GDPR Art. 6(1)(b)). Processors: Cloudflare Stream (the imported video), Supabase (the encrypted key).

When you contact us, we collect the content of your communications and any information you choose to provide.

We may receive limited information from:

• Authentication (Supabase Auth passes us your email and verified-email status)
• Payment processors (Stripe may notify us of payment status changes)
• AI engine providers (where applicable, status updates on generation jobs)

We do not buy personal information from data brokers, ad networks, or similar sources.

To be explicit:

• We do not train AI models on your data. The AI engines we use are third-party services accessed via API. Filmion does not operate proprietary trained AI models.
• We do not sell your personal information. We do not sell, rent, or trade your personal information for monetary or other valuable consideration.
• We do not share your User Content with other users. Your User Content (uploads) is private to your account. Only the limited Library Compounding mechanism described in Section 4.4 allows certain Generated Output to be served as a starting reference to other users.
• We do not display advertising to you on the Service. The Service is ad-free.

We engage trusted third-party service providers ("subprocessors") to perform functions on our behalf. These subprocessors are contractually bound to use your information only as needed to provide their services to us. A current list is in Section 5.

When you initiate a generation, your prompt and (where applicable) your reference assets are transmitted to the AI engine provider you have selected. The AI engine provider processes this content and returns it to us. Whether AI engine providers retain or use your prompts and reference content for their own purposes is governed by their respective privacy policies.

We may disclose your information if required by law or in good-faith belief that disclosure is necessary to comply with a legal obligation, protect rights or property of Filmion, prevent wrongdoing, or protect personal safety.

This Section explains a novel data flow specific to the Service. Please read it carefully.

(a) What it does. Generated Output you produce that meets the Terms of Service Section 6.4(b) reusability criteria may be stored in a shared library and used as a starting reference for AI generations requested by other users.

(b) What is shared. The shared library entry contains: the R2 URL of the asset itself, the prompt that generated it, the engine used, semantic tags assigned by our automated classifier, and an internal owner-account identifier that is used ONLY to prevent serving an asset back to its originator. The owner-account identifier is NEVER surfaced to other users, never displayed in the user-facing UI, and never included in the user-facing output.

(c) What other users see. When another user's generation uses your library entry as a starting reference, that user receives a NEW AI-generated output derived from your entry. The output is generated fresh; it is not a copy of your output. The other user receives no information about you and cannot determine that your account was the source.

(d) Eligibility floor. A Generated Output is eligible for the shared library only if (i) no User Content you uploaded was used as a direct input to the generation, (ii) the prompt does not contain proper nouns suggesting brand- or person-specific intent, and (iii) the Service's automated classifier confirms the output does not depict a recognizable face, a trademarked brand mark, or any personally-identifiable content.

(e) Opt-out. You may opt out of Library Compounding for individual generations at the time of generation by checking the "Do not contribute to library" option (where available). You may also request manual removal of a specific library entry attributable to your account by emailing privacy@filmion.ai.

(f) Retention. Library entries are retained according to the eviction policy described in the Terms of Service Section 13.4.

If Filmion is involved in a merger, acquisition, bankruptcy, or sale of all or substantially all of its assets, your information may be transferred as part of that transaction. This includes moving Filmion into a company we form to run it, such as a Florida limited liability company. That company will be bound by this Privacy Policy, and we will tell you by email and on this page.

We may share your information with third parties where you have given us your explicit consent.