Paint Color Visualizer — Privacy Policy
Effective Date: November 7, 2026
This Privacy Policy covers Paint Color Visualizer, the Android app on Google Play (package com.mobilegames.paintvisualizer), and Paint Color Visualizer, the iOS app on the Apple App Store (together, “the App”). Both are developed and published by Mobile Card Games & Travel Apps, LLC. It explains what data the App collects, how it is used, and how your privacy is protected. Where the Android and iOS versions differ, the difference is called out explicitly.
The two versions behave identically from your point of view, but they reach our AI provider by different routes and store slightly different data. Where that matters, this policy says which platform it is describing.
1. Data We Collect
The app handles the following data:
- Room photos: Photos of your room that you take with the camera or select from your photo library. To generate the repainted image, your photo is uploaded to OpenAI's image-generation service (see below).
- Paint color selections: The colors and surfaces you choose to repaint.
- Purchase information: Records of your in-app credit purchases, managed by Apple (iOS) or Google Play (Android) together with RevenueCat.
- Credit balance (Android): An anonymous account identifier and the number of visualization credits it holds. This is created automatically on first launch and is not linked to your name, email, or Google account.
- Install attribution (Android): The Google Play install referrer — the campaign or source tag of the link that led to the install, if there was one (see section 3).
The app does not collect your name, email address, location, or device advertising identifiers (on Android, the advertising-ID permission is removed from the App), and contains no analytics or advertising SDKs.
2. How We Use Your Data
When you tap to visualize a paint color, your room photo (resized and compressed) and a text description of the surfaces to repaint and the target color are sent to OpenAI's image-generation API (openai.com), which returns an edited image showing your room with the new paint color.
The route differs by platform. On iOS, the request travels over an encrypted HTTPS connection through AIProxy (aiproxy.com), a secure API relay service. On Android, it travels over an encrypted HTTPS connection through our own backend, hosted on Google Cloud (Firebase Cloud Functions), which forwards it to OpenAI and returns the result. In both cases the photo is handled only for the duration of that request; neither AIProxy nor our backend keeps a copy.
For each visualization the Android app sends our backend the photo, re-encoded as a new JPEG (which drops embedded photo metadata such as location); whether it is an interior or exterior photo; a random request ID; the App's version; and, for each surface you repaint, the surface type, the paint color's name, RGB value, and brand, and any trim or brick options you chose. The backend turns those choices into the AI instruction and sends OpenAI only the photo and that instruction; the App version is not stored. If you cancel a visualization, the App sends the request ID so the backend can stop it.
Room photos may incidentally include people. Any such photo is treated exactly the same way: sent to OpenAI only to generate the repainted image, never analyzed for identity, and never stored on any server we operate. Per OpenAI's API data-usage policy, data sent through the API is not used to train their models.
3. Third-Party Data Sharing
- OpenAI (openai.com): Receives your room photo and paint selections solely to generate the repainted image, relayed over encrypted HTTPS via AIProxy (iOS) or our own backend (Android).
- RevenueCat (revenuecat.com): Manages in-app credit purchases. RevenueCat receives purchase transaction tokens from Apple or Google Play and a random anonymous app-user ID — never your name, email, or photos. Payments themselves are processed by Apple or Google; we never see your payment card details. On Android, that app-user ID is the anonymous account identifier described in section 1, and RevenueCat also stores the install referrer described below.
- Google (policies.google.com/privacy), Android only: Google Play processes payments and confirms to our backend that a purchase is genuine: after a purchase, the App sends our backend the Google Play purchase token and the product ID, and the backend asks Google Play to verify them before adding the credits; every few minutes the backend also asks Google Play which purchases were refunded or charged back, so the matching credits can be removed. Google Cloud and Firebase host our backend and the anonymous credit balance described in section 4. Google Play Integrity confirms that requests come from a genuine, unmodified copy of the App. Once after installation, the App reads the Google Play Install Referrer — the referral tag (such as a campaign or source name) of the link that led to the install, if any — and stores it with your anonymous RevenueCat ID to measure which links and campaigns lead to purchases; it contains no personal information. Google Play also shows the in-app rating and update prompts, and when the App suggests one of our other apps, Google Play shows that app's install page; Google handles those under its own privacy policy.
- Our website (Android): The App downloads a small configuration file from mobilegames.cloud, our own website, to decide which of our other apps to suggest. The request contains no personal data; like any web request, it exposes your device's IP address to the hosting provider, and we do not use it to identify you.
We do not sell, rent, or share your data with any other third parties.
Abuse prevention: every AI request the App sends carries a device-attestation token — Apple DeviceCheck together with your device's Apple identifier-for-vendor on iOS, and Google Play Integrity on Android. In addition, each time the Android app starts it sends our backend two one-way hashes: one of an app-specific device identifier, and one of a random restore key that the App keeps in Google Block Store, which travels with your device backup. They let us restore your credit balance after a reinstall or on a new phone set up from your backup, and make sure the single free visualization cannot be claimed repeatedly; we store only a further keyed hash of each value, which cannot be reversed to identify your device. All of this is used solely to prevent abuse and rate-limit AI requests. None of it is linked to your name or identity, and none of it is used for advertising or tracking.
4. Data Storage and Retention
- On your device: Original photos and generated results are stored locally on your device until you delete them from the app's history or uninstall the app.
- In your iCloud (iOS): Your before/after history syncs across your devices via your private iCloud (CloudKit) database, tied to your Apple ID. This data is accessible only to you — we cannot access it. Your credit balance is synced via Apple iCloud key-value storage, which we also cannot access.
- In your Google account backup (Android): If Android Auto Backup is enabled on your device, your saved before/after images and app settings are included in your device's private Google backup, which is used to restore the app if you reinstall it. That backup belongs to your Google account; we cannot access it.
- On our servers: We never store your photos. On iOS we operate no server at all — photos exist in transit only. On Android, our backend (Google Cloud Firestore, in the United States) stores an anonymous account identifier, your credit balance, the keyed hashes described in section 3, an append-only record of credits added and spent (for purchases, the product and the Google Play order number), and technical details of each visualization request (image dimensions, timing, whether it succeeded, and the AI provider's token usage). It does not store the photo itself or any generated image. Request records and purchase confirmations are automatically deleted 30 days after they finish. The anonymous account and its balance are kept for as long as the account exists, so that a reinstall or a new phone does not lose your purchased credits. Our backend's operational logs (Google Cloud Logging) record request IDs, anonymous account IDs, product IDs, and error codes for troubleshooting; they never contain your photos or the generated images.
5. Data Security
All data transmitted to third-party services is sent over encrypted HTTPS connections. No AI provider key is ever embedded in the App: on iOS the key is protected by the AIProxy relay service, and on Android it is held in Google Secret Manager and used only by our backend. Requests to our backend are accepted only from a verified, unmodified copy of the App (Firebase App Check with Google Play Integrity), and the anonymous credit balance can be read only by the account it belongs to and written only by our backend.
6. Your Rights
You have the right to:
- Delete individual before/after results from the app's history at any time.
- Remove all app data by uninstalling the app (on iOS, iCloud-synced history can be removed by deleting items in the app before uninstalling).
- Deny camera or photo library permissions in iOS Settings, which prevents the app from accessing your photos. The Android app requests no camera or photo-library permission at all — it uses the Android photo picker and the system camera, so it only ever receives the single photo you choose or take. On Android 8 and 9 only, saving a result to your gallery uses the system storage permission, which you can deny in Android Settings.
- Turn off the App's progress notification on Android at any time in Android's notification settings; visualizations work without it.
- Request deletion of the anonymous Android account and its credit balance and request records by emailing us at the address below. Because the account is anonymous, we cannot look it up by name or email: if you bought credits, include the Google Play order number (it starts with GPA.) from your purchase receipt. Deleting the account forfeits any unused credits on it.
Depending on where you live, privacy laws such as the European Union's General Data Protection Regulation (GDPR) and the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA) give you rights over your personal data, including the rights to know, access, correct, and delete it. On iOS we hold nothing on our own servers, so there is typically nothing for us to access or delete — deleting the App deletes your data. On Android we hold the anonymous account described in section 4; you may contact us at the email below to have it and its records deleted. In either case, where the App processes data in transit or a third-party service described above collects data, you may contact us to exercise your rights and we will respond as required by applicable law.
7. Children's Privacy
The App is not directed at children under 13, and we do not knowingly collect data from children under 13. In some regions, including the European Union, a higher minimum age applies to consent for data processing; the same statement applies there — we do not knowingly collect data from anyone under the applicable age.
8. Data Breach Notification
In the unlikely event of a data breach affecting user data on any system we operate, we will notify affected users as required by applicable law.
9. Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be reflected by updating the "Effective Date" at the top of this page.
10. Contact Us
If you have questions about this Privacy Policy or your data, please contact us at:
v5cqpsj4e3u4@opayq.com