This privacy policy covers the Creator app ("the app") for Android — and for iOS, when released — made and operated by CREOVIA PRO LLP, a limited liability partnership incorporated under the (Indian) Limited Liability Partnership Act, 2008 (LLPIN: ADA-3738) ("we", "us", "our"), registered office: No. 33, 4th Floor, 1st Main, HMT Layout, CBI Road, Ganganagar, R T Nagar, Bengaluru – 560032, Karnataka, India. Privacy contact: [email protected]. We are the data controller — and, for India, the data fiduciary under the Digital Personal Data Protection Act, 2023 — for the personal data described here. The Creovia Pro website has its own policy at creoviapro.com/privacy.
This policy also covers account.creoviapro.com, where you can sign in to buy, manage or cancel Creator Pro and redeem codes. That site keeps your sign-in in your browser's storage (set by Firebase Authentication), uses Google reCAPTCHA Enterprise through Firebase App Check to tell real visitors from automated abuse, and sets no advertising or analytics cookies.
The short version: your footage is processed on your phone, not on our servers. Accounts are optional, we cannot see your content, and backups go to your own cloud storage — not ours. The data the app does collect is the standard operational kind — account basics if you sign in, analytics, crash reports, advertising, and purchase state — and every category is listed below, along with who processes it and how to exercise your rights.
1. Your videos, photos, and audio stay on your device
- Editing — including every AI feature (background replacement, face redaction, captions, auto-reframe, stabilization, and the rest) — runs entirely on your device. Your media is never uploaded to us or to any server for processing.
- Speech-to-text for captions, silence detection, and all detection and tracking models run on-device.
- The app accesses only the photos and videos you explicitly pick, via the system photo picker or scoped storage access. Voice-over recordings are stored locally with your project.
- Projects, drafts, and exports are stored locally on your device. We cannot access, view, scan, or moderate your content — signed in or not.
- Backups are yours too. If you connect a cloud drive, project backups are written to your own Google Drive (Android) or iCloud Drive (iOS), under scoped access that only reaches files the app itself created. We run no content servers and hold no copy.
- We do not use your content to train AI models — ours or anyone else's.
2. Data we collect, and why
At a glance — each category maps to the disclosures in Google Play's Data safety section and Apple's App Privacy label, and is explained in full below the table.
| Category | Examples | Purpose | Legal basis | Shared with | Retention |
|---|---|---|---|---|---|
| Account info (optional) | Email, name, profile photo | Account, purchases, backup; we store your account’s email address on our servers to identify your account for support and purchases | Contract | Google (Firebase Auth), Cloudflare, Neon | Until account deletion |
| Emails we send (only if your account has an email address) | Your email address, and the content of the message | Verification codes, a welcome email, and notices about purchases on our website | Contract; legitimate interests (welcome email, which you can unsubscribe from) | Resend (email delivery), Cloudflare, Neon | Your address: until account deletion |
| Email verification (email & password accounts) | A one-way hash of the code, when it was sent and verified, and how many codes were sent; the code itself is never stored | Confirming you own the address; limiting abuse | Contract; legitimate interests (security) | Cloudflare, Neon | Code: 10 minutes. Verification record: until account deletion. Send counters: 24 hours after the last code |
| Notification preferences | Your Settings → Notifications choices, the app’s language, your time zone and region setting, push token | Sending only the notifications you chose, in your language, outside night-time hours | Consent (each category you leave on); contract (account and billing notices) | Google (Firebase Cloud Messaging), Apple (on iOS), Cloudflare, Neon | Until you change them, or account deletion |
| App interactions | Features used, screen flows | Product improvement | Consent / legitimate interests | Google (Firebase), Mixpanel | 14 months (Firebase) / 12 months (Mixpanel) |
| First-party analytics events | Features used, screen flows, app version, country, pseudonymous IDs | Product improvement | Consent / legitimate interests | Our first-party backend (Cloudflare) | Up to 400 days |
| Crash & diagnostics | Stack traces, device model | Stability | Legitimate interests | Google (Crashlytics) | 90 days |
| Anonymous error reports | Error type, code location, app version, device model | Stability | Legitimate interests | Our first-party backend (Cloudflare) | 400 days |
| Diagnostic reports you send | Error description, project file and file names, device summary | Fixing the problem you reported | Consent (each time you send) | Our first-party backend (Cloudflare) | 90 days |
| Device & ad identifiers | Advertising ID, app-instance IDs, push token | Ads, analytics, notifications | Consent | Ad partners (below) | Until reset / deletion |
| Purchase state | Active subscription / purchase, the platforms it covers | Delivering what you bought | Contract | Google Play Billing, Apple, Razorpay, Paddle | While entitlement active |
| Web purchase records (only if you buy on our website) | Account email, plan, platforms, price, currency, billing country, payment-provider order / subscription / payment and invoice IDs, refund and dispute status, campaign tags of the link you came from; in India, the mobile number you give Razorpay at checkout | Selling and delivering Pro, renewals, invoices, refunds, tax and accounting, fraud prevention; the mobile number as your account’s billing contact, so we can match a payment to your account when you contact support | Contract; legal obligation (tax and accounting records) | Razorpay (India), Paddle (outside India), Cloudflare, Neon | 8 years after the transaction (anonymised if you delete your account) |
| Pro usage record (only while you have Pro) | That an export was made with Pro: its type (video or photo), time, platform, app version and where your Pro came from. Never the content of your projects or exports | Handling refund requests and payment disputes, and preventing refund abuse | Legitimate interests; contract | Cloudflare, Neon | 18 months, or until you delete your account |
| Checkout funnel statistics (account.creoviapro.com) | Which checkout steps were reached, the plan, platforms and country chosen, and the outcome (paid, failed, abandoned); a random ID created for each browser tab. No cookies, no account ID, and your IP address is not stored | Improving checkout and detecting broken payment steps | Legitimate interests | Cloudflare, Grafana Labs | 14 days |
| Sticker searches | Search terms | Returning results | Legitimate interests | Klipy | Not stored by us |
| Support mail | Your email + message | Responding to you | Legitimate interests | — | Up to 24 months after resolution |
- Account information (only if you sign in). Creator works fully without an account — you can continue as a guest. If you choose to sign in (Google or email & password, via Firebase Authentication — and, on account.creoviapro.com, also Sign in with Apple), we receive your email address and, with Google sign-in, your basic profile (name, profile photo). With Apple, we receive the name and email you choose to share, which can be an Apple private relay address. Purpose: keeping your purchases and settings attached to you, and enabling cloud-drive backup. Passwords are handled by Firebase Authentication; we never see them.
- Emails we send. If your account has an email address, our backend may send you: a verification code when you create an email & password account; a welcome email, once, when your account has a verified address; and, only if you buy on account.creoviapro.com, billing notices (subscription started, renewal reminder, payment problem, plan ending or ended). The welcome email has a one-click unsubscribe link, and once you unsubscribe we stop sending it to you. Verification codes and billing notices are service messages about your account and purchases, so they are sent even after you unsubscribe. Emails are delivered for us by Resend, which receives your address and the message only to deliver it.
- Notifications. Push notifications come in five categories. Account & billing notices are always on. Exports & AI, Tips, Offers and Product news can each be switched off in Settings → Notifications. Where the law requires your prior consent to marketing (the EEA, the UK, Brazil and California), Offers is off until you turn it on. The app sends your choices to our backend, with the app's language, your time zone and region setting, and the device's push token. Our backend uses them to decide which notifications to send, in which language, and to hold non-urgent ones back during night-time hours where you are. You can also turn notifications off entirely in your device's settings.
- App interactions (usage analytics). Which features are used and how often, screen flows, and feature performance, under pseudonymous identifiers (app-instance and device-scoped IDs). Processed by Google Firebase Analytics, Mixpanel, and our own first-party backend (hosted on Cloudflare and Neon; see section 4). Purpose: understanding what to improve.
- Crash logs and diagnostics. Stack traces, device model, OS version, and performance timings when something breaks. Processed by Firebase Crashlytics and Firebase Performance. Purpose: app functionality and stability.
- Anonymous error reports. When the app hits an error, it sends our first-party backend the kind of error, where in the app's code it happened (class, method and line), and the app version, operating-system version and device model — also when you have declined analytics. These reports carry no user ID, session or screen, are not linked to you, and never include an error's own text, file paths or any of your content. Purpose: app stability.
- Diagnostic reports you choose to send. If an export fails, you can tap Send details. Only then, after the app shows you exactly what will be included, we receive: the technical description of the error, the names of the files in your project, your project file (your edit settings — never the videos, photos or audio themselves) and a summary of your device. The report is linked to your account so we can follow up. Purpose: fixing the problem you reported.
- Device and other identifiers. The advertising identifier (Android Advertising ID; on iOS only with your App Tracking Transparency permission), Firebase app-instance IDs, and a push-notification token if notifications are enabled.
- Purchase state. Which subscription or one-time purchase is active, via Google Play Billing (or Apple In-App Purchase on iOS). Payments are processed entirely by the app store; we never receive your card or bank details.
- Purchases on our website. If you buy Creator Pro at account.creoviapro.com, we record the plan, platforms, price, currency and billing country, and the order, subscription, payment, invoice and refund identifiers the payment provider gives us, linked to your Creovia account so the app can unlock Pro. Your card, bank or UPI details are collected by the payment provider — Razorpay in India, Paddle elsewhere — never by us; we only see what they report back (for example the payment method type and whether a payment succeeded). In India, Razorpay asks for your mobile number (required for recurring payments); we keep that number as your account's billing contact, and delete it with your account. Paddle sells to you as our reseller and merchant of record, so for its checkout it is an independent controller of the data it collects, under its own privacy notice.
- Search queries (sticker & GIF library). When you search the sticker library, the search term is sent to our sticker-library provider to return results. We don't attach your identity to these queries.
- Support correspondence. If you email us, we receive your email address and whatever you include, used solely to respond.
We do not collect: your precise location (only your approximate location, the country, used for analytics and ads as described above), contacts, messages, browsing history, health or financial information (beyond the purchase records above — never card numbers, bank details or UPI PINs), or the content of your media — a diagnostic report you choose to send can include your project's file names and edit settings, never the videos, photos or audio — and unless you sign in, we don't hold your name or email either. We do not sell personal data, and we do not use your data for third-party marketing.
3. Advertising and consent
- The free tier shows ads served through Google AdMob, our ad-mediation platform. Through mediation, an ad may be filled by one of our advertising partners: Google, Meta Audience Network, Unity Ads (Unity Technologies), or Liftoff Monetize (formerly Vungle). These partners may receive your device's advertising identifier and coarse, non-identifying device information to serve, frequency-cap, and measure ads. Paid tiers remove ads.
- Beyond the partners named above, Google may share that same limited ad-request data with its certified ad partners, for bidding and measurement. The full, current list of those partners is shown inside the consent dialog itself, under Manage options, so it stays accurate as the list changes.
- Where required (for example the EEA, UK, and Switzerland), you'll see a consent dialog (Google's UMP framework) before any personalised advertising, and you can choose non-personalised ads or decline. You can change your choice any time from the app's settings.
- On Android you can reset or delete your Advertising ID in system settings (Settings → Google → Ads). On iOS, ads would only ever track across apps if you allow the App Tracking Transparency prompt; declining it is fully supported.
- Ad partners process data under their own policies: Google advertising, Meta privacy policy, Unity privacy policy, Liftoff privacy policy.
4. Who processes data on our behalf
- Google LLC — Firebase Authentication (accounts), Firebase Analytics, Crashlytics, Performance, Cloud Messaging, Remote Config; AdMob; Google Play Billing; Google Drive (as your chosen backup destination). Privacy policy.
- Mixpanel, Inc. — product analytics. Privacy policy.
- Meta Platforms, Inc. — Audience Network ads via mediation. Privacy policy.
- Unity Technologies — Unity Ads, ads via AdMob mediation. Privacy policy.
- Liftoff Mobile, Inc. — Liftoff Monetize (formerly Vungle), ads via AdMob mediation. Privacy policy.
- Razorpay Software Private Limited — payment processing for purchases on our website in India (cards, UPI AutoPay mandates, invoices, refunds). Privacy policy.
- Paddle.com Market Limited — reseller and merchant of record for purchases on our website outside India, where offered: it processes the payment, calculates and remits sales tax and VAT, and issues your invoice. Privacy policy.
- Klipy (klipy.com) — sticker & GIF search results.
- Apple Inc. (on iOS) — App Store distribution, In-App Purchase, and iCloud Drive as your chosen backup destination.
- Resend (Plus Five Five, Inc.) — delivery of the emails we send you (verification codes, the welcome email and billing notices). It receives your email address and the message. Privacy policy.
- Cloudflare, Inc. — hosting for account.creoviapro.com and for our backend. Privacy policy.
- Neon, Inc. — database hosting for our backend. Privacy policy.
- Grafana Labs — performance and error diagnostics (telemetry). Privacy policy.
These providers act as our processors or as independent controllers for their platform services, under contracts and terms that require protection at least equivalent to this policy. Beyond them, we share data only if the law requires it (a valid legal request), to protect rights and safety, or — should CREOVIA PRO LLP ever be part of a merger or acquisition — with the successor entity under this same policy.
5. Legal bases (EEA/UK users)
- Consent — personalised advertising, push notifications, and analytics where consent is required. You can withdraw consent at any time without affecting the app's core function.
- Contract — operating your account if you create one (including verification codes and account and billing notices), and processing purchase state to deliver what you bought.
- Legal obligation — keeping billing and tax records for purchases on our website for as long as tax and accounting law requires.
- Legitimate interests — crash diagnostics, security, fraud prevention, non-identifying usage measurement, and a single welcome email you can unsubscribe from, balanced against your rights.
6. Retention and deletion
- Analytics and diagnostics are retained for defined windows and then deleted or irreversibly aggregated: Firebase Analytics user-level data for 14 months; Crashlytics crash records for 90 days; Mixpanel events for our configured project window of 12 months; first-party analytics on our own backend for up to 400 days; anonymous error reports for 400 days; diagnostic reports you send for 90 days, or until you delete your account if that is sooner. Push tokens persist until refresh or account deletion.
- Email verification codes expire after 10 minutes and are cleared once used. Counts of codes sent to an address hold no address and are deleted 24 hours after the last code, even if you delete your account. Notification preferences are kept until you change them or delete your account.
- Records of purchases on our website are kept for 8 years after the transaction, because tax and accounting law requires it. If you delete your account, we first cancel any active web subscription, then delete your access records, checkout sessions and the link to your identity; the remaining financial records (amounts, dates, provider IDs, refund status) are kept for the rest of that period under a one-way pseudonymous identifier that cannot be turned back into your account, and are then deleted.
- Your projects and media live only on your device: deleting a draft (and its trash entry), clearing the app's storage, or uninstalling the app deletes them. We hold no copy.
- Delete your account in the app: Settings → Account → Delete account. This deletes your Firebase Authentication account, unlinks your identity from analytics, revokes the app's cloud-drive access, and clears your account's settings on this device. Your drafts stay on the device; delete them in the app if you no longer want them. On our backend it deletes your account record and stored email address, your email verification record, your devices' notification preferences and push tokens, your Pro usage records, and the first-party analytics events and counts tied to your account. Backups already in your own Google Drive or iCloud remain yours to keep or delete there.
- When an account is deleted we keep a short deletion record as evidence that the deletion was carried out: a one-way identifier and the time each step finished. Once the deletion completes it holds no name, email address or account ID. It is kept for 3 years and then deleted.
- No longer have the app installed? Use the data-deletion request page or email [email protected] — we'll delete your account and the analytics or diagnostics data tied to your identifiers with our providers, and confirm within 30 days.
- Support emails are kept only as long as needed to resolve your request.
7. Security
All data in transit between the app and our service providers is encrypted (TLS). Because content processing is on-device and we run no content servers, the most sensitive data — your media — never crosses the network at all. Access to provider dashboards is restricted and protected with strong authentication.
8. International transfers
Our providers may process the limited data above on servers outside your country, including the United States. Where data leaves the EEA/UK, transfers rely on adequacy decisions or Standard Contractual Clauses; equivalent safeguards apply for other regions with transfer rules.
9. Your rights
- EEA/UK (GDPR): access, rectification, erasure, restriction, portability, objection, and withdrawal of consent — plus the right to complain to your supervisory authority.
- California (CCPA/CPRA): the rights to know, delete, and correct; we do not "sell" personal information. If serving personalised ads constitutes "sharing", you can opt out via the in-app ad-consent controls or your device's ad settings, and we honour opt-out preference signals where technically applicable. We don't discriminate for exercising rights.
- India (DPDP Act 2023): as data principals you have the rights to access, correction and erasure, grievance redressal, and to nominate. Our grievance contact is below. If you are not satisfied with our resolution, you have the right to complain to the Data Protection Board of India.
- Exercise any of these by emailing [email protected]. Before acting on a request we check it comes from you: if you have an account, we match it against the email address stored for that account (and, for purchases on our website, the billing records above), and may ask you to confirm from that address or from inside the app while signed in. If you never signed in, we hold no name or email for you, so we may ask for details such as your device model and when you used the app to find the pseudonymous data tied to it — and we act on what we can match reliably to you.
10. Children
Creator is not directed at children under 13 (or the higher minimum age your jurisdiction sets for consent), and we do not knowingly collect personal data from them. The app is not enrolled in child-directed programs, and ads are not targeted at children. If you believe a child has used the app in a way that gave us personal data, contact us and we'll delete it.
11. Changes to this policy
We'll update this policy as the app evolves. New versions are published at this URL with an updated effective date; material changes are additionally noted in the app's release notes and, where consent is the legal basis, re-consented in the app.
12. Google API Services User Data Policy
The Creator app's access to and use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically:
- Narrow Drive scope. We request only the
drive.filescope. This grants access solely to the files you create or open with Creator (for the optional cloud backup) — we cannot see, read, or access any of your other Google Drive files. - Sign-in only. Your Google account email and basic profile are used only to sign you in and associate your account.
- Limited use. We use data received from Google APIs only to provide and improve these user-facing features (account sign-in and your own backups). We do not use it for advertising, do not sell it, and do not transfer it to others except as needed to provide the backup you requested or as required by law.
- No human access. We do not let humans read your Google user data unless you give explicit consent for a specific issue, it is necessary for security or to comply with the law, or the data has been aggregated and anonymised.
13. Contact & grievance
Data controller / data fiduciary: CREOVIA PRO LLP, registered office: No. 33, 4th Floor, 1st Main, HMT Layout, CBI Road, Ganganagar, R T Nagar, Bengaluru – 560032, Karnataka, India. Grievance redressal (India — DPDP Act, 2023): Namrata Boro, Grievance Officer, CREOVIA PRO LLP, [email protected]. We acknowledge grievances within 48 hours and resolve them within the timelines applicable law prescribes. General support: [email protected].