Coins let you create videos in the app. The cost varies by video type and is shown before generation.

To receive coins and create videos, purchase a subscription. Each plan grants a set amount of coins (based on the tier you choose) that renew automatically every billing cycle. After subscribing, you can also buy additional coin packs as needed.

How can I contact you?

For any question, reach out to us at support@gimiapp.com.

Where is the app available?

Gimi AI is available on the App Store and Google Play.

Privacy Policy - Gimi AI

Last updated: 5 Jul 2026

Who we are

App: Gimi AI (iOS & Android)

Controller: Amir Landau, individual developer based in Israel

Contact: [email protected]

Audience: General; not directed to children under 13.

What this policy covers

This policy explains what we collect, how we use it, which service providers process data for us, how we handle advertising attribution and tracking, how long we keep it, your rights, how anonymous and legacy account data are handled, and how to delete your account and data. It is written to align with Google Play’s Data safety + in-app account deletion and Apple’s App Privacy + in-app account deletion requirements.

Data we collect and why

Media you provide (may include faces, voices, music, or other audio)

Data: Photos/images you upload; source videos you upload; and audio embedded in uploaded source videos.
Use: Safety screening of required inputs; generation of your requested output via our processors; delivery of outputs that may be video-only or audiovisual depending on the selected feature.

Notes: In this policy, a "feature" is the specific generation type you select — shown in the app as a template, style, or mode. For motion-control family features, including Motion Control, Custom Dance, and Lip Sync, the full uploaded source video, including its audio track, and the uploaded source photo are sent to FAL to generate the output. For other features, required media, prompts, and generation parameters may also be sent to Vidu or other processors used for the selected feature. Depending on the selected feature, outputs may be visual-only, may preserve the original audio track from an uploaded source video, or may include provider-generated audio. We do not intentionally create biometric identifiers, face geometry/“faceprints,” voiceprints, or perform identity recognition.

Text prompts and other generation request input

Data: Text prompts, free-form text, and other request parameters you submit for generation.
Use: Safety screening and moderation of prompts and generation requests; generation of your requested output via our processors; storage with request or generation records where applicable; troubleshooting, abuse prevention, analytics relating to blocked or rejected requests where applicable, and support where related request records are retained.

Legacy account/profile information (if applicable)

Data: Email, display name, and signed-in account user ID, where you create or still use a signed-in account (including legacy accounts from older app versions).
Use: Support/manage legacy signed-in accounts.

Identifiers and basic app/device data

Data: Anonymous app/user ID or signed-in/legacy user ID; preferred language, country, and app-profile/account timestamps such as creation and last activity/login times; device push-notification tokens; and basic app/device technical data such as app version, platform, OS version, device brand/model, physical/emulator indicators, and related token/update timestamps where tied to your app profile or account.
Use: Core functionality, app-profile/account management, notifications, compatibility, localization, security, abuse prevention, and troubleshooting.

Purchases & entitlements (from app stores via our subscription provider)

Data: Subscription status/expiry, premium/access flags, product-change events, and provider sync/status metadata and timestamps from our subscription/paywall providers; we do not receive your card details.
Use: Manage subscriptions/credits; access control; troubleshoot purchase, entitlement, paywall, and restore/recovery flows.

Refund requests (Apple App Store)

Data: If you request a refund from Apple for an in-app purchase, our subscription provider (RevenueCat) may share with Apple, on our behalf, information about your usage and consumption of the purchased content — for example, whether the purchase was delivered and is working properly, whether a free sample or trial of the content or information about its functionality was provided before purchase, and our preferred resolution for the refund request.
Use: To help Apple make an informed decision on your refund request, as part of Apple's refund process. Apple makes the final decision on whether to grant or decline the refund under its own policies.
Consent: By using our app and making in-app purchases, you consent to this sharing of usage and consumption data with Apple in connection with refund requests. This data is shared only with Apple, only when a refund request is made, in compliance with Apple's policies and only as necessary to process the request, and is not used for advertising.

Android purchase recovery records (Android only; created after a purchase where applicable)

Data: A one-way hashed device-derived identifier based on ANDROID_ID; purchase/recovery linkage data such as the Firebase user ID at the time of purchase, RevenueCat transaction identifiers, product ID, purchase date, expiration date, store name, and migration/recovery status.
Use: Link an old anonymous Android account to a new anonymous Android account on the same device for purchase reconciliation and credit recovery where applicable; prevent duplicate recovery; troubleshoot restore/recovery issues.

Notes: The raw ANDROID_ID is not stored on our servers. This mechanism is Android-only, is not used for advertising, and is not intended for cross-device tracking.

Credits & usage

Data: Credit/usage history (amounts, type, reason, timestamps, balance, and where applicable adjustment, transfer, or reconciliation records); per-day request counters and moderation outcomes (pass/fail only) to enforce daily/request limits and safety rules.
Use: Show balance; apply credit costs; record transfer/adjustment events where applicable; enforce limits and safety blocks (daily counters reset at 00:00 UTC); reconcile restore/recovery outcomes where applicable.

Generation records and related metadata

Data: Minimal technical metadata needed to run and display results (e.g., task IDs, model/provider, selected feature/template, status, timestamps, and requested duration where applicable), related request records such as selected parameters or stored prompt text where applicable, and links to provider-hosted outputs or other media records we store.
Use: Provide and display results; troubleshoot issues; support deletion, restore, and recovery flows where applicable.

Paywall interactions

Data: Impressions, taps, experiment variant.
Use: Render paywalls, run A/B tests, measure conversion, troubleshoot purchase flows, and support analytics/attribution described in this policy.

Diagnostics & analytics (release builds)

Data: Crash logs and usage analytics via Firebase Analytics, including screen/feature usage, onboarding and permission funnels (for example, tracking-permission and notification-permission prompt and result events), paywall interactions, and where applicable moderation-related prompt data from blocked requests and limited internal app rating/feedback-related analytics. Some of these events are also forwarded to our attribution partners (see "Advertising, attribution & tracking identifiers").
Use: Improve stability, diagnose issues, understand feature usage, measure onboarding and conversion funnels, investigate blocked requests, and improve the product. Product analytics are used regardless of your ATT choice; IDFA-based advertising attribution is used only if you grant the iOS tracking permission.

Advertising, attribution & tracking identifiers

Data: On Android, the Google Advertising ID (AAID). On iOS, the Identifier for Advertisers (IDFA) only if you grant permission through Apple's App Tracking Transparency (ATT) prompt, plus the vendor identifier (IDFV), your IP address, ATT consent status, and the device/app data described elsewhere in this policy. Attribution SDKs may also collect or derive technical and network signals such as attribution-provider device IDs and ID types, App Set ID where available, IP-based country or region, locale, time zone, screen properties, carrier, and network/connectivity information, depending on platform, permissions, device settings, SDK behavior, and applicable law. We also share certain in-app and purchase events (for example: install, generation activity, subscription start/renewal, and revenue) with our attribution partners.
Use: To measure the performance of our marketing and influencer campaigns — i.e., to understand which campaign led you to install or subscribe — and to attribute installs and conversions. This is "tracking" as Apple defines it, because device identifiers and event data may be combined by our attribution partners with data from other apps or websites. We do not serve third-party ads inside the app.
Partners: Singular and Airbridge (mobile measurement / attribution partners). On iOS we also use Apple's SKAdNetwork, a privacy-preserving attribution framework that reports aggregate campaign results without identifying you, used as a fallback when ATT permission is not granted.
Your control: On iOS you can decline the ATT prompt, or change it any time in Settings → Privacy & Security → Tracking; if you decline, we do not use the IDFA and rely on aggregate SKAdNetwork attribution instead. On Android you can reset or limit your Advertising ID in your device settings.
Attribution records we store: When attribution is received or needs later reconciliation, we may store campaign, channel, ad group, creative, content, term, source, attribution timestamps, current/pending attribution status, and related purchase attribution records in our own systems. We use these records for marketing measurement, referral/influencer attribution, commission and payout reporting, purchase-attribution reconciliation, fraud prevention, support, compliance, and dispute resolution.

Support communications

Data: Emails/forms you send us (including deletion requests).
Use: Respond to you; maintain a compliance record that we acted on your request.

Internal app rating/feedback submissions and promotional/redemption codes

Data: Rating values and feedback text you submit through our internal app rating/feedback flow, whether feedback text was included, promotional or coupon codes you submit, and related redemption, transaction, or audit records.
Use: Understand product feedback, improve the service, send limited feedback text to analytics where applicable, process redemptions and related credits/adjustments, prevent abuse/fraud, and support account, billing, or deletion requests where relevant.

Content reports and complaints

Data: If you submit a report or complaint, we may collect selected report reasons, free-form descriptions/details, reported video/content identifiers, reporting user/app-profile identifiers where applicable, timestamps, and related review/enforcement records.
Use: Investigate allegedly fake, misleading, abusive, infringing, or otherwise violating content; enforce our rules; respond to complaints; and maintain safety/compliance/legal-defense records.

We do not sell your personal data for money. We do use mobile measurement / attribution partners (Singular and Airbridge) and, on iOS, may ask for your permission to track via Apple's App Tracking Transparency prompt — see "Advertising, attribution & tracking identifiers" above. Under some U.S. state laws (for example, California), the use of advertising identifiers for cross-context attribution may be considered "sharing"; where required, you can opt out as described in "Your privacy rights."

Legal bases for EEA/UK users

Contract — to provide the service you request (anonymous or legacy account/app profile, purchases, restore/recovery where applicable, and video generation).
Legitimate interests — security, abuse handling, complaint investigation, fraud prevention, duplicate-recovery prevention, diagnostics, and non‑advertising product analytics.
Legal obligation — retain specific records for tax, fraud‑prevention, or legal‑defense purposes.
Consent — where required (e.g., notifications on iOS, access to camera/photos, and App Tracking Transparency permission for advertising attribution on iOS). For users in the EEA/UK, advertising attribution using device identifiers relies on your consent (the ATT permission on iOS), not on legitimate interests.

Moderation & safety processing

We use third‑party content‑moderation services (such as Google Cloud Vision SafeSearch and provider‑side moderation from FAL, Vidu, or their partners) to determine whether text prompts, uploaded images/videos/audio, and other required inputs and generation requests can proceed, depending on the selected feature.
We store moderation logs to enforce daily/request limits and to prevent abuse; depending on the feature and implementation, those logs may include pass/fail outcomes, counters, and moderation-related prompt data from blocked requests. Counters reset at 00:00 UTC.
Where a provider blocks content under its rules, we receive the block status and minimal context to apply our limits.

Temporary media handling

Uploaded source media and generated outputs may be processed and temporarily hosted by our providers to run a generation and deliver the result.
File and link availability may depend on provider settings and our configured retention settings. We do not promise a fixed availability period unless we expressly state that one applies.
Generated images/videos may be available temporarily (including temporary display in your profile/history) to deliver your result and allow re-download, but links may expire and temporary copies may be deleted without notice.
Please save your media to your device promptly. If we delete media or links under our control, we cannot remove copies already downloaded to your device.

How we collect data

You provide it when you use an anonymous app profile or a legacy signed-in account, sign in through Google or Apple where available, purchase, upload media, submit prompts or other generation inputs, submit feedback through our internal app rating/feedback flow, enter promotional/redemption codes, submit support requests or content reports, or generate videos.
Automatically for core functions (push token; paywall analytics; crash/usage analytics in release), app/deep-link routing, attribution, and fraud-prevention/reconciliation.
From app stores via our subscription provider (receipt/entitlement signals only).
From sign-in providers where available, such as Google or Apple, when you choose to use those sign-in methods.
On Android only, and only after a purchase where applicable, we may create a hashed device-linked recovery record to support reinstall credit recovery/reconciliation for anonymous users.

Cookies and Local Storage (Website Only)

When you visit our website, we use a first-party preference cookie named gimiLangPref to remember your selected interface language (English or Hebrew) and to keep navigation consistent. This cookie expires after 12 months, uses SameSite=Lax, and applies to Path=/. It is not used for advertising, tracking, analytics, or sharing information with third parties.

We also store the same language preference in your browser’s localStorage under the key gimiLangPref, which is used only to support the client-side language toggle.

You may block or delete this cookie at any time. If you choose to do so, the website will use your browser’s Accept-Language settings to determine the default language.

We do not use any third-party cookies or advertising cookies. If we add analytics or additional cookies in the future, we will update this policy and request consent where required by law.

Device permissions (asked only when needed)

Camera — capture a source image for generation.
Photos/Library — select images or source videos to upload.
Notifications — alert you when a video is ready.
Tracking (iOS) — we ask, via Apple's App Tracking Transparency prompt, for permission to use your IDFA for advertising attribution. Declining does not reduce app functionality; we then rely on Apple's aggregate SKAdNetwork attribution instead.

Data retention while your account or anonymous app profile is active

We retain the data required to operate your account or anonymous app profile and provide the service. This includes:

Legacy account/profile information, if applicable (email, display name)
App/user identifiers and device/app data tied to your account or anonymous app profile (e.g., preferred language, country, push tokens, timestamps, counters)
Internal subscription and entitlement records that we store for your account or anonymous app profile (not Apple/Google’s store records)
Credit balances, credit/transfer/reconciliation records, and Android purchase recovery linkage records where applicable
Campaign, referral, influencer-link, attribution, pending purchase-attribution, and attribution-reconciliation records tied to your user ID or app profile, where applicable
Generation records, stored prompts/request records where applicable, media links/references, and related metadata
Support communications, internal app rating/feedback submissions, promotional/redemption code records, content reports/complaints, and related review/enforcement records where applicable
Usage and safety counters (e.g., request limits, abuse-prevention flags)
Technical logs required to keep the service secure and functioning normally

We keep this data for as long as your account or anonymous app profile is active because it is necessary for operating the service, enforcing limits, delivering videos, managing subscriptions and credits, and supporting restore/recovery flows where applicable.

How to request deletion

In the app: Settings → Delete Account
If you cannot access the app: email [email protected] or use our account-deletion page

What is deleted when you delete your account or app profile

When you request account deletion, we delete the personal data we control, including:

Your legacy account/profile data, if applicable
Links and references we store to your generated videos, related media records, and stored generation-request records tied to your user ID or app profile
Your usage and credit history, including transfer/reconciliation and promotional/redemption records tied to your user ID or app profile
Device identifiers, push tokens, and Android purchase recovery linkage records tied to your account or app profile
Campaign, referral, influencer-link, attribution, pending purchase-attribution, and attribution-reconciliation records tied to your account or app profile
Support communications, internal app rating/feedback submission records, report records, and complaint records tied to your user ID or app profile, except where retention is required for legal, safety, fraud-prevention, or compliance reasons
Internal subscription and entitlement records
Any data tied to your user ID or app profile that can identify you

We delete the personal data and media references we control.

We cannot delete purchase records stored by Apple or Google, and provider-hosted media or provider-side records may remain temporarily under providers’ own policies unless separately deleted or expired.

Data we may retain after deletion (without identifying you)

Some records may be retained without your user ID or any direct identifiers. These may include:

Technical logs needed for security, stability, and troubleshooting
Aggregated or pseudonymised usage statistics
Non-identifying job metadata (for example: duration, resolution, template, processing time)
Accounting or tax records that legally must be preserved

In these cases, we remove the user ID and any direct identifiers so the data no longer relates to you as an identifiable individual. This does not allow us to recreate or restore your account.

Data retained for legal, tax, fraud-prevention, or compliance purposes

Some data must be retained under applicable law or legitimate interests, even after account deletion. This may include:

Non-identifying purchase records (e.g., product ID, store transaction ID)
Proof of your request (such as deletion-request emails)
Minimal operational logs confirming that we carried out your deletion request
Limited analytics, internal app rating/feedback submission records, attribution/revenue reconciliation records, or moderation records required for abuse-prevention, troubleshooting, fraud prevention, dispute resolution, or legal defense
Support, complaint, moderation, or report records required for abuse-prevention, safety enforcement, or legal defense
Records required for tax, fraud-prevention, duplicate-recovery prevention, or legal defense

These records are stored in restricted systems and are not used for marketing or product improvement. We do not retain identifiers longer than required by law.

Timing of deletion

Unless a longer legal retention period applies:

Data tied to your user ID or app profile is deleted within 30 days after account deletion, except records retained for legal, tax, fraud-prevention, attribution-integrity, payout, dispute-resolution, or compliance reasons
Non-identifying technical logs may be retained for up to 12 months for troubleshooting and dispute resolution
Minimal operational deletion logs may be kept for up to 30 days
Backup data is overwritten on a rolling schedule and accessed only for security, continuity, or legal compliance

These timelines follow global standards and are valid for users in Israel, the EU/EEA, the UK, the United States, and other regions.

Provider-side data (Superwall, RevenueCat, FAL, Vidu, Singular, Airbridge)

Deletion of your account or app profile in our systems does not automatically remove historical records or hosted files held by external providers such as Superwall, RevenueCat, FAL, Vidu, Singular, or Airbridge. Attribution data held by Singular or Airbridge may persist under their own policies and must be requested separately.

If you also want deletion of data still stored by these providers, you may request this separately. Where possible, and using the identifiers available to us, we may submit deletion requests to relevant providers or remove links/files we control.

Processing times, scope of deletion, and final results depend on each provider’s own policies, systems, and capabilities, and we cannot guarantee their timelines or outcomes.

Service providers (processing on our behalf)

We use these processors strictly to provide the Service, under our instructions:

Firebase (Google) — anonymous/legacy authentication, database, push notifications, diagnostics, analytics
Privacy: https://firebase.google.com/support/privacy
Cloud privacy: https://cloud.google.com/terms/cloud-privacy-notice
RevenueCat — subscription/entitlement management, purchase events, restore/recovery signals, device identifiers used for configured attribution integrations, and refund-request handling on iOS (sharing purchase delivery/consumption information with Apple when you request a refund — see "Refund requests (Apple App Store)" above) (no card processing by us)
Privacy: https://www.revenuecat.com/privacy/
Superwall — paywall rendering and experiments (non-advertising analytics)
Privacy: https://superwall.com/legal/privacy-policy
Google Cloud Vision (SafeSearch) — image moderation before generation
Privacy: https://cloud.google.com/terms/cloud-privacy-notice
FAL — Motion Control and other video-generation features (may receive uploaded images, source videos including embedded audio, prompts, and generation parameters required for the selected feature)
Privacy: https://fal.ai/privacy
Vidu — other video-generation features and task polling (may receive prompts, parameters, and required media for supported features)
Privacy: https://platform.vidu.com/docs/privacy-policy
Singular — mobile measurement / attribution and marketing analytics. May receive device identifiers (IDFA where you permit it, IDFV, AAID), IP address, ATT consent status, your app user ID, and in-app/purchase events including revenue and subscription events (some sent server-to-server from RevenueCat).
Privacy: https://www.singular.net/privacy-policy/
Airbridge — mobile measurement / attribution, tracking-link/deep-link routing, click/install reporting, and influencer campaign measurement. May receive device identifiers, IP address, IP-based country or region, locale, time zone, screen/network/device signals, your app user ID, and attribution/install/deep-link events.
Privacy: https://www.airbridge.io/privacy-policy

We do not use your media to train our own models. Our processors handle content only to provide the Service and related purchase/restore functionality under their policies above.

International data transfers

We operate globally and use providers (including our attribution partners Singular and Airbridge) that process data in multiple countries. Where required, we use contractual and organizational safeguards for cross-border transfers (e.g., EU Standard Contractual Clauses for EEA/UK transfers) and limit onward transfers.

Security

We apply organizational and technical measures appropriate to the risk, including access control, authentication, logging, and encryption in transit/at rest.

Automated decisions

We do not make automated decisions that produce legal or similarly significant effects about you.

Your privacy rights (region-specific)

We honor applicable laws and will verify your request.

EEA & UK (GDPR/UK GDPR): rights of access, rectification, erasure, restriction, portability, and objection; responses within one month (extendable where allowed).
California (CCPA/CPRA): rights to know, delete, correct, opt-out of sale/sharing, limit use of sensitive data, and non-discrimination. We do not sell personal information for money. Our use of advertising identifiers for attribution may be considered "sharing" for cross-context behavioral advertising; on iOS you can opt out by declining or revoking the App Tracking Transparency permission, and on Android by resetting or limiting your Advertising ID.
Israel (PPL): rights to access and correct personal data in a database; regulator: Israel Privacy Protection Authority.

Children’s privacy

The app is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal data, contact [email protected] so we can delete it.

Complaints

If you believe your privacy rights were not respected, you may contact your local data protection authority. You can also contact us at [email protected].

Changes

We may update this policy. We will post updates here and change the “Last updated” date. For material changes, we will notify you in-app or by email where required by law.