This privacy policy covers the Creovia FX app ("the app", "FX") for Android, iPhone and iPad, 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.
The short version: FX edits your photos and short videos on your device and never uploads them. You do not need an account; signing in is optional. The free version shows ads, and the app sends crash reports and usage analytics so we can fix problems and improve it, and tells Google and Meta when our own ads lead to an install or a purchase. You can turn crash reports and analytics off in About. This policy lists everything the app collects, who processes it and why.
1. Your photos and videos stay on your device
- All editing, filters, effects and person detection run on your device. Your photos, videos, camera frames and microphone recordings are never uploaded to us or to anyone else, and they are never added to crash reports, analytics or ad requests.
- You choose individual items through your device's system media picker. On Android, FX keeps the access grant for the item you chose so you can keep editing after reopening the app. On iPhone and iPad, FX keeps a private copy of the item in the app's Imports folder, which is excluded from backup; replacing an import removes the previous copy. Export uses temporary local files.
- We do not use your photos or videos to train AI models — ours or anyone else's.
2. Camera and microphone
Camera access is optional and is requested when you open the camera. FX processes live camera frames on your device to preview your filter and effect. Microphone access is requested for video recording; if you deny it, you can record silently. New captures stay in private temporary storage until you save or share them. Retake, or closing the review, removes the temporary capture.
3. Person detection
Some effects find the person in a photo, video or camera frame so they can draw around them or stay off them. This runs entirely on your device. FX uses the result only to draw the image you are working on. It does not store it, send it anywhere, or use it to identify anyone.
4. Accounts are optional
- Without signing in, FX uses a guest account: a random account ID from Google Firebase Authentication, with no name or email. Our server keeps the account and device record described in section 5 under that ID.
- If you sign in — with Google, Apple, or an email and password, through Google Firebase Authentication — we receive your email address. With Apple, that can be a private relay address Apple creates for you. We use it to keep your account and purchases attached to you and to answer support requests.
- Your name: Google sign-in passes on the name and profile photo of your Google account, and Apple passes on the name you choose to share the first time you sign in. You can also type a name in Settings → Account → Edit profile, or clear it there. The name and photo are kept only by Google Firebase Authentication, with your sign-in. FX shows the name on your account page. Our server does not store either, and neither is sent to analytics or to advertisers.
- Email and password accounts: to confirm the address, we email a 6-digit code through Resend. We store only a one-way hash of the code, which expires after 10 minutes, and when the address was confirmed.
- Purchases still belong to your Google Play or Apple account. We keep a record of them for your FX account (section 5).
- You can delete your account at any time in Settings → Account → Delete account. See FX data deletion for what is deleted and what stays.
5. What the app collects, and why
- Crash reports, through Google Firebase Crashlytics: app version, device model, operating system, a random identifier for this installation, a stack trace, short failure codes, and technical text from the failure. Used to find and fix problems. On by default; turn it off in About.
- Usage analytics, through Google Analytics for Firebase: which screens and features are used, which looks are chosen, when an export or capture finishes, paywall and purchase events, and ad events, together with the device model, operating system, app version, country derived from your IP address, and a random app-instance identifier. Events contain look identifiers and short codes only, never file names, media details or anything you type. Used to understand how FX is used and improve it. Turn it off in About. Where the law requires consent, analytics waits for it.
- FX's own copy of usage events: the same usage events, also sent to our own server (hosted on Cloudflare) with the account ID, a session ID, the platform, country and app version. Behind the same Analytics switch and consent. Kept 90 days. Used to see how FX is used without depending on Google's reports.
- Account and device record, on our server (hosted on Cloudflare and Neon): the account ID, how you signed in (guest, Google, Apple or email), your email address if you signed in, the platform, system and app version, language, country, time zone, how the app was installed, how many times it was opened and when it was first and last used; and for each device, a random device ID, the device model and system and app version. Used to run your account, keep purchases attached to it, and support you.
- Purchase state: whether you have FX Pro or Remove ads, and which product. Read from Google Play or Apple on your device and cached there so Pro works offline. Payments are handled entirely by Google Play or Apple; we never receive your card or bank details.
- Purchase records, on our server: Google Play and Apple tell our server about purchases, renewals, refunds and cancellations. We keep, for your account: the product, the store, the store's order ID, the price, currency and country, whether it is a trial, whether it is active, and when it ends. Used to deliver what you bought, handle refunds and support, and measure our ads (section 7).
- Advertising and ad-measurement data (see section 7).
- App configuration: FX fetches settings such as the free-look list and ad frequency from Google Firebase Remote Config, which uses a random installation identifier.
6. What is never collected
- No photos, videos, camera frames or audio, and nothing derived from them, such as the person outline.
- No file names, paths or media details, and nothing you type, such as the names of your saved looks.
- No name, profile photo or email address unless you sign in (section 4).
- No precise location, contacts, messages, browsing history, or health or financial information. We do not sell personal data, and we do not use it for third-party marketing.
7. Advertising and consent
- The free version shows ads served by Google AdMob, which may fill an ad from Meta Audience Network. To choose, cap and measure ads, Google and Meta may receive your device's advertising identifier, your IP address (from which they derive an approximate location), and basic device and app information. Google's use of this data is described at policies.google.com/technologies/partner-sites, and Meta's at facebook.com/privacy/policy.
- Measuring our own ads. We advertise FX on Google and Meta. To learn which ads bring people to FX, the app tells Google (through Google Analytics for Firebase, linked to Google Ads) and Meta (through the Meta SDK) when FX is installed or opened, an account is created, the first photo or video is made, a trial starts, or a purchase is made, with the price and currency. Meta also receives an ID its SDK creates for FX on this device and basic device information. For renewals and for trials that turn into a paid subscription, which happen while the app is closed, our server sends Meta the same kind of event through Meta's Conversions API, with Meta's ID for your device and a one-way hash of your account ID and, if you signed in, of your email address.
- This happens only while the Analytics switch in About is on and, where the law requires consent, only if you agree to ad measurement in Google's consent dialog. If you decline or withdraw, the Meta SDK is not started (or is muted until the app next opens), Google is told that ad consent is denied, and our server forgets Meta's ID for your device, so no further events are sent for you. On iPhone and iPad, the advertising identifier, and the hashed account ID and email sent by our server, are used only if you allow App Tracking Transparency.
- On iPhone and iPad, if you are signed in, Google Analytics for Firebase may use your account's email address for Google's on-device conversion measurement, only while ad consent is granted. The address is processed on your device and is not sent to Google or to us for this purpose.
- Ads never appear in the editor preview or the camera. FX Pro and Remove ads turn off banner, native and full-screen ads; a rewarded ad remains available as an option for unlocking a Pro look.
- Where required (for example in the EEA, the UK and Switzerland), FX shows Google's consent dialog before personalised ads, and you can choose non-personalised ads or decline. You can change your choice in About.
- On Android, you can reset or delete your advertising ID in your device settings. On iPhone and iPad, ads use your device's advertising identifier only if you allow the App Tracking Transparency prompt; declining is fully supported.
8. Who processes data on our behalf
- Google LLC / Google Ireland Ltd. — Firebase Authentication (accounts and sign-in with Google), Firebase Crashlytics, Google Analytics for Firebase, Firebase Remote Config, Firebase Installations and AdMob; Google Ads, for measuring our own ads; Google Play for purchases on Android. Privacy policy.
- Meta Platforms, Inc. / Meta Platforms Ireland Ltd. — Audience Network, for ads served through AdMob; the Meta SDK and Conversions API, for measuring our own ads (section 7). Privacy policy.
- Apple Inc. — App Store distribution, In-App Purchase and Sign in with Apple on iPhone and iPad.
- Cloudflare, Inc. — hosting for our server and its usage-event store. Privacy policy.
- Neon, Inc. — database hosting for our server. Privacy policy.
- Resend — delivery of the email confirmation code. Privacy policy.
These providers act as our processors, or as independent controllers for their own platform services. Beyond them, we share data only where the law requires it, or — should CREOVIA PRO LLP ever be part of a merger or acquisition — with the successor entity under this same policy.
9. Legal bases (EEA/UK users)
- Consent — personalised advertising, measuring our own ads, and analytics where consent is required. You can withdraw any of them at any time without losing any part of the app: declining personalised ads means you see non-personalised ads instead.
- Contract — running your account if you create one, and processing purchase state and purchase records to deliver the Pro looks or the ad removal you bought.
- Legitimate interests — crash diagnostics, security, and usage measurement, balanced against your rights.
10. How long data is kept
- Crashlytics keeps crash reports for 90 days. Analytics event data is kept for 2 months. Ad data is kept under Google's and Meta's policies. Purchase state stays on your device until you remove FX.
- Your sign-in, with the email, name and profile photo Google Firebase Authentication holds for it, is kept until you delete your account.
- On our server: FX's own usage events expire after 90 days. The account and device record, the purchase records and the email confirmation record are kept until you delete your account; an email code expires after 10 minutes. Meta's ID for a device is kept only while you allow ad measurement. When you delete your account, we keep only a record that the deletion was carried out (the account ID and when each step finished).
- Removing FX deletes its working files, settings and identifiers from your device. Exported copies in Photos, your gallery or other apps stay until you delete them.
11. Saved looks, settings and sharing
- FX stores your named looks, the current edit and your settings on your device. They are not sent to us. On iPhone and iPad, normal device backup may include these settings. Android app backup is disabled.
- On Android, finished exports are written to your media library. On iPhone and iPad, FX asks for permission to add finished media to Photos when you choose to save; if you deny it, the finished file stays available to share or retry.
- Sharing is started by you and handled by the app you choose; its privacy practices apply.
12. Security
All data in transit between the app and our service providers is encrypted (TLS). Because editing happens on the device and we run no content servers, your photos and videos never cross the network.
13. 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.
14. Your rights
- You can turn off crash reports and analytics in About, change your ad consent in About, and reset your advertising ID in your device settings.
- 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" under the CPRA, you can opt out through the in-app ad-consent controls or your device's ad settings. 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]. If you signed in, you can delete your account yourself in Settings → Account → Delete account; see FX data deletion. If you never signed in, we hold no email to match a request against, so we may ask for details (such as your device model and roughly when you installed the app) to find the records — or, in some cases, be unable to identify them at all.
15. Children
FX 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. If you believe a child has used the app in a way that gave us personal data, contact us and we will delete it.
16. Support emails
If you email us, we receive what you choose to send, such as your email address and message, and use it only to reply. The app does not attach logs or media to support emails.
17. Changes to this policy
If a future release changes these practices, we will update this policy and the in-app disclosures before the change takes effect. New versions are published at this URL with an updated date.
18. 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].