Privacy Policy

Filme: AI Movie Generator

Last updated: November 8, 2026

Filme: AI Movie Generator (“we,” “our,” or “us”) is committed to protecting your privacy. This Privacy Policy explains how information is collected, used, and disclosed when you use our mobile applications for iOS and Android and any related services we operate (collectively, the “Service”). By using the Service, you agree to this Privacy Policy. If you do not agree, please do not use the Service.

1. What the Service does

Filme lets you create, manage, and export AI-assisted videos and related content from your text prompts and the inputs you provide. Some features require an internet connection and send your inputs to our backend so that specialized third-party AI providers can process them and return the requested output.

2. Information we collect

2.1 Information you provide

• Creative inputs: Text you enter (such as prompts, titles, character descriptions and style descriptions) and choices you make in the app.
• Photos and media you upload (optional): If a feature lets you add an image — for example, a selfie or reference photos when you create a character — that file is captured when you choose to add it and is sent to our backend and to the AI providers named in Section 2.3 to generate the requested output. Photos you upload may contain a face; see Section 2.3 for exactly who receives them and how face imagery is and is not used, and Section 7 for how long uploads are kept.
• Voice recordings (optional): If you give a character your own voice, the short recording you make (or the audio file you choose) is captured only when you tap Record or choose a file, and only after you confirm it is your voice or that you have permission to use it. It is stored on our servers and sent through Kie.ai to MiniMax’s video model (Section 2.3) so the movie clips can speak that character’s lines in that voice. We do not use it to identify you, we do not create a voiceprint from it, and we do not use it to train any model of our own. See Section 7 for how long it is kept.
• Profile information (optional, local): You may set a display name and similar profile fields, stored on your device. We do not require an account or email to use core features.
• Public username and shared films (optional): If you choose an Explore username or offer a film to the Explore feed, we receive the username and the film. See Section 2.7.
• Content reports and blocks (only if you make one): If you report something or block a creator from inside the app, we receive the report. See Section 2.8.
• Support communications: If you contact us, we receive whatever information you send (for example, your email address and message content).
• Refund and credit-restore requests (only if you make one): If you send us such a request — by email, or with the code form in the Android app — we receive the email address you give us, any code you entered, and (from the Android form) a one-way hash of your device identifier so we can match the request to the purchase. We use it to answer that request and for nothing else.

2.2 Information collected automatically

• Device and app data: Such as device type, operating system, app version, language, and general usage information needed to run and improve the app.
• Device identifier: The app creates a random identifier the first time it runs — stored in the Keychain on iOS and in the app’s private storage on Android. It is not your name, email address, phone number or advertising identifier; the Service has no accounts, so this identifier is what keeps your films, characters, credits and rewards together. It is sent with requests to our backend (to run your requests, enforce free-tier limits and subscription state, and prevent abuse), it is set as the user identifier in our analytics tools (Firebase Analytics and Mixpanel) while usage analytics are on, and Google AdMob passes it back to our server when you finish a rewarded ad (Section 2.6). It is not used to track you across other companies’ apps or websites. On iOS, limited entitlement or usage-related values may sync via Apple’s iCloud Key-Value Storage where enabled. On Android, the identifier, your credit balance and the app’s local database are included in Android’s backup of the app (to your Google account, if backup is on) so they can be restored on a new device; your videos and cached media are not.
• Analytics events: We use Google Firebase Analytics and Mixpanel (product analytics) to log events such as app launches, navigation, generation start/complete/fail (with non-sensitive metadata), paywall views, and purchase completion, together with status properties such as your credit balance, subscription status and whether you have made a purchase. Firebase also records some events automatically (for example, first open and session start). Mixpanel also receives your push-notification token. These events are tied to the device identifier above, are not used for advertising or cross-app tracking, and help us understand product usage and reliability. They never contain your photos, your voice, your prompt text, or your generated media. On Android, Firebase’s collection of the advertising ID is turned off. You can turn usage analytics off at any time with Settings → Share usage analytics; while it is off, the app stops Firebase Analytics and Mixpanel collection on that device. Approximate location: the app never uses your device’s Location Services and Mixpanel’s IP-based location is turned off; Firebase Analytics may still derive a coarse, city-level location from the IP address of each request, which Google uses for aggregate analytics only.
• Remote configuration: We use Google Firebase Remote Config to deliver feature flags, limits, and links (for example, policy URLs) without requiring an app update.
• App integrity checks: To protect paid features from abuse, the app uses Google Firebase App Check, which asks Apple App Attest (iOS) or Google Play Integrity (Android) to confirm that requests come from a genuine copy of the app. Those services process device and app integrity signals; our backend receives only a short-lived token saying whether the check passed.
• Push notifications: If you grant permission, we use Google Firebase Cloud Messaging to deliver notifications. Your push token is sent to our backend so we can tell you when a film or character is ready. Promotional notifications are off unless you turn them on in the app’s Settings. A local notification history (a limited number of recent entries) may be stored on your device. You can turn off notifications in your device settings.
• Credit and purchase records: Your credit balance and a history of credit purchases, spends and refunds are kept on your device and are also sent to our backend (with your app version and push token) so we can support you, restore credits, and handle refunds correctly. For Google Play purchases this includes the purchase token, order ID and product ID (Section 3).
• Network status: The app may check connectivity to show offline states and avoid failed requests.
• Diagnostics: Error descriptions or technical context may be included in analytics events to help fix bugs.

2.3 Information processed on our servers and by third-party AI providers

When you request AI generation, relevant inputs (for example, prompts, parameters, any photos you uploaded and any voice recording you gave a character) are transmitted over HTTPS to our backend. Our backend then forwards them to the specific third-party companies listed below. These are the same companies the app names in its AI Data Processing notice before anything is sent.

The companies whose AI models Kie.ai runs for us. Kie.ai passes each request to the model that does the job, so these companies receive the data that model needs:

• OpenAI (GPT Image) — draws character images, sets, props and scene stills. Receives the photos you upload, the images made from them, and the written prompts.
• xAI (Grok Imagine) — makes movie clips. Receives scene stills and the written prompts. xAI’s Grok language model is also the last-resort backup above.
• Google (Veo) — makes movie clips when you choose it. Receives scene stills and the written prompts.
• ByteDance (Seedance) — makes movie clips when you choose it. Receives scene stills, character images and the written prompts.
• Kuaishou (Kling) — makes movie clips when you choose it. Receives scene stills and the written prompts.
• MiniMax (Hailuo) — makes movie clips. Receives scene stills, character images, the written prompts and, when a character who speaks in the clip has one, that character’s voice recording. MiniMax is the only company that receives voice recordings.
• Suno — composes the instrumental score. Receives only a short text summary of your story’s mood; never your photos or voice.
• Anthropic (Claude) — through Kie.ai, as the first backup route above.

If we start using a model from a company not listed here, we will update this section and the in-app notice before the change ships, and ask for your agreement again.

Every company above processes your data only on our instructions and only to carry out the request you made — not for their own purposes and not to advertise to you. Each is bound by a written agreement requiring it to protect your data to the same or an equivalent standard as this policy describes, including confidentiality, security and international-transfer safeguards. We do not use your photos, voice recordings or prompts to train any model of our own.

About photos that contain a face: If a photo you upload contains a face, it is used only as a visual reference so the AI can generate your character’s appearance, and so Claude can describe that appearance in words. We do not perform facial recognition, and we do not create faceprints, biometric identifiers, or any face geometry data — on your device or on our servers. We do not use your photos to train any model of our own, and photos are never used for advertising or analytics — our analytics providers receive usage events only, never your photos or generated content. Outputs (for example, generated video or metadata) are returned to the app.

2.4 AI Data Processing & consent

The app shows an AI Data Processing notice that names each company in Section 2.3 and states what that company receives. It is offered once on the Home screen after onboarding and, if you have not agreed yet, it appears again the moment you first tap to create something that would send a photo, a voice recording or your text — before anything is sent. You can reopen the full notice at any time from the ⓘ button at the top of the New Character screen.

Nothing you type, upload or record is sent for AI processing until you tap “I Agree & Continue” on that notice; your agreement is recorded on your device. If you do not agree, swipe the notice away — nothing is sent and no credits are used. When we change who receives your data or what they receive, the notice is updated and the app asks for your agreement again.

2.5 Photos and voices of other people

If you upload a photo, you confirm the photo is of you, or that you have explicit permission from the person shown — and, for a child, from their parent or guardian. Do not upload photos of public figures, do not upload another person’s photo without their consent, and never use the Service to impersonate, deceive, or harm anyone. The same applies to voices: record or upload only your own voice, or a voice you have the speaker’s explicit permission to use. We may remove content and suspend AI features for misuse.

2.6 Optional rewarded ads

Where available, the Rewards Center lets you watch a short ad to earn free credits. Ads are shown only when you choose to watch one, and are served by Google AdMob. When an ad is requested or shown, Google receives information such as your IP address, device and app information and, on Android, the App Set ID, and uses it to deliver and measure the ad, prevent fraud and, where permitted, personalize ads. We do not collect your device’s advertising identifier: the Android app does not request the advertising-ID permission, and the iOS app does not ask for App Tracking Transparency permission, so the iOS advertising identifier is not available to it. In the EEA and UK, Google’s consent message (the Google User Messaging Platform) asks for your choices before any ad is requested. When you finish a rewarded ad, Google’s servers tell ours, together with your device identifier, so we can add the reward. Google describes how it uses this information at policies.google.com/technologies/partner-sites. We never reward you for granting a permission, following us, or rating the app.

2.7 Explore: public username and shared films (optional)

You can choose a public username and offer a film you made to the in-app Explore feed. Your username and the films you offer are stored on our servers. We review every film before it appears; if we approve it, it is published on Explore under your @username — visible to everyone who uses the app, and through share links on the web, which show its poster, title and description. What becomes public is the film, its poster, its title and logline or description, and your username — never your device identifier, the photos or voice recordings you uploaded, or the prompt you wrote. You can take a film out of Explore at any time with Remove from Explore in the app, or ask us to remove a film or your username (Section 9).

2.8 Reporting and blocking

You can report a film, an Explore title, a character or a creator from inside the app (⋯ → Report in Explore). A report sends our backend your device identifier, what you reported (its identifier and any creator name shown on it), the reason you chose, any details you type, and your platform and app version. A film you report is hidden on your device at once.

You can also block a creator (⋯ → Block in Explore). The list of creators you blocked is kept on your device, hides their films from you, and can be undone in Settings. Blocking also sends our backend a report on that creator (the same details as above), so we can review the account.

We use reports only to review and moderate content, to remove content and ban abusive usernames or devices, and to prevent misuse of the reporting feature. Reports are seen only by us; we do not tell the person whose content you reported or blocked who you are.

2.9 Cookies and similar technologies

Our web pages — this Privacy Policy, our Terms, and the page that opens when someone taps a link to a shared film — do not set cookies and do not load advertising, analytics or tracking scripts.

Inside the app, similar technologies are used only as described in this policy: the random device identifier (Section 2.2), settings and records stored on your device, and the software development kits (SDKs) of the services named in Section 5, which store identifiers needed for analytics, push notifications, app integrity checks and, only if you choose to watch one, rewarded ads (Section 2.6). You can reset or limit ad-related identifiers in your device settings, turn usage analytics off in the app’s Settings, and turn off notifications at any time.

3. How we use information

• Provide, operate, and improve the Service.
• Enforce free-tier limits, paid subscription entitlements, consumable credit balances, and abuse prevention tied to your device.
• Process in-app purchases through Apple’s App Store (iOS) and Google Play (Android). Our paid offerings may include auto-renewing subscriptions and consumable credit packs. Apple and Google handle payment and billing details — we never receive your card or other payment details. On iOS we receive subscription status, transaction identifiers, and purchase results through Apple’s StoreKit APIs, and may receive notifications from Apple about refunds and renewals. On Android the app sends our backend each purchase’s purchase token, order ID and product ID, and we may ask Google Play whether a purchase was later refunded or cancelled. We use this to unlock features, keep your credit records correct, handle refunds, and prevent fraud.
• Grant the rewards you earn in the Rewards Center, including credits for rewarded ads you chose to watch.
• Publish films you offered to Explore once we have approved them, review content reports, and remove content or ban usernames and devices that break our Terms.
• Send push notifications you have allowed (promotional ones only if you turned them on).
• Analyze aggregated or de-identified usage via analytics services to improve stability and product design, while usage analytics are on.
• Comply with law, respond to lawful requests, and protect our rights and users.

4. Legal bases (EEA / UK users)

Where the GDPR or UK GDPR applies, we rely on:

• Contract / steps prior to contract: Providing the Service you request (for example, running a generation job).
• Consent: Sending your photos, voice recordings and text to the AI providers in Section 2.3 (the in-app AI Data Processing notice), publishing a film you offered to Explore, push notifications, and personalized ads collected through Google’s consent message in the EEA and UK (or App Tracking Transparency if we ever use the advertising identifier for cross-app tracking).
• Legitimate interests: Securing the Service, debugging, analytics that do not override your rights, improving the product, and reviewing content reports to keep the Service safe.
• Legal obligation: Where we must retain or disclose information by law.

5. Sharing of information

• Service providers who assist us in operating the Service: the companies named in Section 2.3 — Anthropic, our AI processing partner Kie.ai and the model makers it runs our requests on (OpenAI, xAI, Google, ByteDance, Kuaishou, MiniMax and Suno), our storage and delivery provider Cloudflare and our film-assembly host Fly.io — plus Google Firebase (analytics, push notifications, remote configuration and App Check), Mixpanel (product analytics) and Google AdMob (optional rewarded ads — see Section 2.6). They process data on our instructions, under written agreements requiring the same or an equivalent standard of protection as this policy describes.
• Apple for App Store purchases, related receipt validation and App Attest, and Google for Google Play purchases (Google Play Billing) and Play Integrity.
• Other users and the public — only what you choose to publish: your Explore username and the films we approve for Explore (Section 2.7).
• Authorities if required by law or to protect safety and rights.

We do not sell your personal information as that term is commonly defined under U.S. state privacy laws.

6. International transfers

We and our providers may process data in countries other than your own, including the United States and the countries where the companies in Section 2.3 operate. Where required, we use appropriate safeguards (such as standard contractual clauses) for transfers from the EEA, UK, or Switzerland.

7. Retention

• On-device data remains until you delete the app or delete items inside the app, subject to how local storage behaves on your device.
• Photos and voice recordings you upload (including selfies, reference photos and a character’s voice) and the characters made from them are kept on our servers so your characters keep working in later films. When you delete a character in the app — or use Settings → Delete my data — it is removed from your app straight away; the photos, voice recordings and records behind it stay on our servers until our team erases them, which we do when you ask us to (Section 9). Copies in delivery caches expire within 7 days.
• Films and other generation content: Prompts, job records and generated media are kept on our servers so your films keep working and so we can troubleshoot, comply with law and keep the Service secure. Deleting a film in the app removes it from your device; the server copy stays until our team erases it, which we do when you ask us to (Section 9).
• Explore username and shared films: Kept until you remove the film from Explore, ask us to remove them, or we take them down.
• Content reports and blocks: Reports are kept as moderation records; contact us to ask for deletion. Your block list stays on your device until you unblock or delete the app.
• Purchase and credit records: Kept as long as needed for accounting, refund handling, fraud prevention and legal obligations.
• Android backup: If backup is on, the copy of the app’s data described in Section 2.2 is kept by Google under your Google account’s backup settings.
• Analytics: Retained according to our analytics providers’ standard policies.
• AI providers: The companies in Section 2.3 keep the data they receive only as long as their written agreements with us allow for carrying out and securing the request.

8. Security

We use industry-standard measures such as HTTPS for network traffic and secure storage where appropriate (for example, the iOS Keychain, or the app’s private storage on Android, for sensitive device state). Media you upload is stored encrypted at rest under randomized, unguessable identifiers; only our backend reads your original uploads. Finished films, posters and the images made for your film are served over HTTPS at unguessable links so the app and the share links you create can play them — anyone who has such a link can open it, so share links only with people you trust. No method of transmission or storage is 100% secure.

9. Your choices and rights

Depending on your region, you may have rights to access, correct, delete, restrict, or object to certain processing, or to data portability. You may:

• Turn promotional notifications on or off in the app’s Settings, and disable all push notifications in your device’s Settings (iOS or Android).
• Limit ad tracking through your device privacy settings (and App Tracking Transparency if applicable). Rewarded ads are optional: they appear only when you choose to watch one.
• Re-read what is sent to which company from the ⓘ button at the top of the New Character screen.
• Take a film out of Explore with Remove from Explore on the film, or delete everything you shared from Settings → Shared to Explore; the copy you shared with us is deleted with it. Unblock creators in Settings.
• On Android, turn off backup for the app in your device’s backup settings.
• Delete an individual character or film in the app — it disappears from your app immediately. The photos, voice recordings and files behind it stay on our servers until we erase them; email us (below) to have that done.
• Email us (below) with your User ID (Settings → My Account) to have everything deleted: the content tied to your device, your characters, and the records kept on our servers — for example your characters and the photos and voice recordings they were made from, films you generated, purchase and credit records, your Explore username and shared films, or content reports — or data held by our analytics providers.
• Delete the app to remove locally stored data (export anything you need first).

To exercise privacy rights — including asking us to erase your data from our servers, or to remove a shared film or your username — or to ask questions, contact us at techhunt.bridge@gmail.com. Because the Service has no accounts, tell us what you want deleted and anything that helps us find it (for example, your Explore username, a character’s name, or roughly when you made a purchase or a film). We will respond as required by applicable law.

10. Children’s privacy

The Service is not directed at children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children. Do not upload a photo or voice recording of a child unless you are their parent or guardian or have their consent. If you believe we hold a child’s information, contact us and we will take steps to delete it.

11. AI-generated content disclaimer

Outputs from AI features may be inaccurate, inappropriate, or incomplete. They are for creative and entertainment purposes only and are not professional advice (legal, medical, financial, or otherwise). You are responsible for how you use and share generated content.

12. Third-party links

The Service may link to websites or services we do not control. Their practices are governed by their own policies.

13. Changes to this policy

We may update this Privacy Policy from time to time. We will post the new version and update the “Last updated” date. If changes are material — for example a new company receiving your photos, voice or text — we will also update the in-app AI Data Processing notice and ask for your agreement again, and provide any other notice required by law.

14. Contact us

• Data controller: Filme: AI Movie Generator
• Email: techhunt.bridge@gmail.com