Exterior Paint Visualizer — Privacy Policy
Effective Date: November 7, 2026
This Privacy Policy covers Exterior Paint Visualizer, the Android app on Google Play (package com.mobilegames.exteriorpaint), and Exterior Paint 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 the same way from your point of view, but they reach the image-generation service by different routes and store slightly different data, so a few sections below distinguish between them. Where a section does not say otherwise, it applies to both.
1. Data We Collect
The App handles the following data:
- Home exterior photos: Photos of your home's exterior 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 exterior surfaces (siding, brick, trim, doors, shutters) you choose to repaint.
- Purchase information: Records of your in-app credit purchases, managed by Apple (iOS) or Google Play (Android) together with RevenueCat.
- Anonymous account identifier (Android only): A randomly generated account ID, created without any sign-in, that holds your visualization credit balance. It is not linked to your name, email, or Google account.
- Device integrity and abuse-prevention signals: See section 3.
- Install attribution (Android only): 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 home exterior 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 home with the new paint color. In both versions the request travels over an encrypted HTTPS connection, and in neither version is the API key stored in the app itself.
On iOS
The request is relayed through AIProxy (aiproxy.com), a secure API relay service that holds the API key.
On Android
The request is relayed through our own backend, running on Google Cloud Functions in the United States, which holds the API key in Google Secret Manager and forwards the request to OpenAI. The backend also checks and updates your visualization credit balance. Your photo passes through this backend in memory only, for the duration of the request; it is never written to disk or to any storage bucket we operate.
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); the output size; a random request ID; and, for each surface you repaint, the surface type, the paint color's name and RGB value, and the trim, brick, stone, and wall-material options you chose. The backend turns those choices into the AI instruction and sends OpenAI only the photo and that instruction. If you cancel a visualization, the App sends the request ID so the backend can stop it.
Exterior 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 home exterior photo and paint selections solely to generate the repainted image, over encrypted HTTPS.
- 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, RevenueCat also stores the install referrer described below.
- Google (firebase.google.com, Android only; Google privacy policy): Firebase provides the anonymous account, the credit ledger, and the abuse-prevention checks described below, and Google Play processes purchases and confirms them to our backend. 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. 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 you tap one of our other apps in the App, Google Play shows that app's install page; Google handles those under its own privacy policy.
We do not sell, rent, or share your data with any other third parties.
Abuse prevention
Generating an image costs us money on every request, so both versions verify that requests come from a genuine installation of the App rather than a script.
- On iOS: each AI request includes your device's Apple identifier-for-vendor and an Apple DeviceCheck token.
- On Android: each request includes a Google Play Integrity attestation, obtained through Firebase App Check, which confirms the request comes from an unmodified copy of the App. Separately, each time the App starts it sends our backend two values: a one-way cryptographic hash of the Android device identifier, and a random restore key that the App generates and 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 grant the one free visualization only once per device. We receive only the hash, never the device identifier itself; the restore key is a random value that does not identify you or your device.
These signals are used solely to prevent abuse, restore purchases, and rate-limit AI requests. They are not linked to your name or identity and are not 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 only): 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 only): If Android backup is enabled on your device, your before/after history and the App's settings (including a copy of the restore key) are included in your device's backup to your own Google account, in the same way as other app data. That backup belongs to you and we cannot access it. Your credit balance is not part of the backup; it is restored from our server instead.
- On our servers (Android only): Because Android has no equivalent of the private iCloud database, the Android version keeps your credit balance on a server we operate (Google Cloud Firestore, in the United States), so that a reinstall or a new phone does not cost you credits you paid for. We store an anonymous account record containing your credit balance; counts of the credits you have received, bought, and used; the restore key and hashed device identifier described in section 3; and a balance history with one dated entry for each credit added, used, or removed after a refund (for purchases, the product and the Google Play order number). We also keep a record of each visualization request — its anonymous account ID, timestamps, output size, processing time, the AI service's usage count, and whether it succeeded — and of each purchase confirmation for 30 days, so that a failed generation can be refunded and abuse can be detected. These records never include your photos, your paint color choices, or the generated images. 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. Your before/after history on Android stays on your device, and in your own Google backup if enabled.
- Photos: On neither platform do we operate any server that stores your photos. Photos exist in transit only, for the duration of the API request.
5. Data Security
All data transmitted to third-party services is sent over encrypted HTTPS connections. API keys are never embedded in the App: on iOS they are held by the AIProxy relay service, and on Android they are held in Google Secret Manager and used only by our backend. On Android, the credit balance can only be changed by our backend — the App itself has no write access to it — and every request to that backend must pass a Google Play Integrity check.
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 stored on your device 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 (iOS). The Android version asks for neither permission: photos come from your own camera app or the Android photo picker, so the App receives only the single photo you take or choose. 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 your anonymous account (Android): Because the Android account is anonymous, we cannot look it up by name or email. Email us at the address below with the Account ID shown on the App's Help screen, or, if you bought credits, the Google Play order number (it starts with GPA.) from your purchase receipt, and we will delete the account record and its associated data. Deleting the account also forfeits any unused visualization 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 no data on servers we operate, so there is typically nothing for us to access or delete on request — deleting the App deletes your data. On Android, the anonymous account record described in section 4 is data we hold, and you may contact us at the email below to access or delete it. 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