Store privacy disclosures
Consolidated privacy questionnaire answers for Prompt Doom submissions to Amazon Appstore, Google Play, and Apple App Store.
Store submission summary
These answers map the current Prompt Doom source and enabled SDKs. Store definitions and third-party SDK behaviour can change, so re-check them whenever the app or SDK versions change.
URLs to enter
- Privacy policy: https://promptdoom.com/app/privacy/
- Account deletion: https://promptdoom.com/app/account-deletion/
- Data deletion: https://promptdoom.com/app/data-deletion/
General security questions
| Question | Answer | Notes |
|---|---|---|
| Does the app collect or transmit user data? | Yes | Account, activity, subscription, reporting, analytics, and advertising flows transmit data off device. |
| Is data encrypted in transit? | Yes for production | The published build and production API must use HTTPS. Do not submit a build configured with the local HTTP development URL. |
| Can users request deletion? | Yes | Use the public account and data deletion forms above. |
| Is every data type required? | No | Guest browsing is available. Account-linked collection begins when the user chooses Google sign-in or account features. |
| Is data used for tracking? | Yes, conservatively | Declare tracking/advertising for Google Mobile Ads unless the distributed build uses consent-controlled limited ads and the SDK disclosure supports a narrower answer. |
Consolidated data inventory
Use this inventory to answer Amazon “Collected / Third-party transfer / Purpose,” Google Play “Collected / Shared / Purpose / Required,” and Apple “Collected / Linked / Tracking / Purpose” questions.
| Store data type | Collected | Linked to user | Shared / transferred | Required | Purposes |
|---|---|---|---|---|---|
| Name | Yes | Yes | Payment/auth service when applicable | Optional app use; required for account | App functionality, account management |
| Email address | Yes | Yes | Google authentication and payment service when applicable | Optional app use; required for account | App functionality, account management, security |
| User IDs | Yes | Yes | Authentication/service providers as necessary | Optional app use; required for account | App functionality, account management, fraud prevention |
| Other user info: profile image | Yes | Yes | Received from Google sign-in | Optional | App functionality, personalization |
| Purchase history | Yes | Yes | Payment provider | Optional | App functionality, account management, fraud prevention |
| Device or other IDs | Yes | May be linked by SDK | Google Mobile Ads | Automatic for ad-eligible users | Third-party advertising, analytics, fraud prevention |
| Advertising ID | Yes | May be linked by SDK | Google Mobile Ads | Automatic or consent-controlled by region/platform | Third-party advertising, analytics |
| Approximate location | Yes, conservative | May be linked by SDK | Google Mobile Ads | Automatic for ad delivery; no location permission used | Third-party advertising, analytics, fraud prevention |
| App interactions / product interaction | Yes | Yes when signed in; guest session otherwise | Ad interactions to Google Mobile Ads | Automatic | App functionality, analytics, advertising |
| Advertising data | Yes | May be linked by SDK | Google Mobile Ads | Automatic for ad-eligible users | Third-party advertising, analytics |
| Other user-generated content | Yes | Yes | No routine third-party transfer | Optional | App functionality, safety, fraud prevention |
| Customer support / deletion request content | Yes | Yes | No routine third-party transfer | Optional | App functionality, account management, compliance |
Data types to answer “No” based on current app source
Precise location; physical address; phone number; race or ethnicity; sexual orientation; political or religious beliefs; credit score; salary, assets, or debts; health; fitness; contacts; call logs; emails or message contents; SMS/MMS; photos uploaded by the user; videos; audio; music; files and documents; calendar events; installed apps; web browsing history; in-app search history stored on the server; crash logs sent to a crash-reporting service; and biometric/environment/body data.
Amazon Appstore questionnaire
App-level answer: Yes, the app collects user data or transfers data to third parties.
| Amazon field | Collected | Third-party transfer | Purposes |
|---|---|---|---|
| Name, Email Address, User IDs, Other user info | Yes | No for routine first-party/service-provider processing | App functionality; personalization; fraud prevention, security and compliance |
| Purchase history | Yes | No when the payment provider qualifies as service provider/user-initiated transfer | App functionality; fraud prevention, security and compliance |
| Device or other IDs, Advertising ID, Approximate location | Yes | Yes | Third-party advertising or marketing; analytics; fraud prevention, security and compliance |
| App interactions, Other user-generated content, Other actions | Yes | Advertising interactions only | App functionality; analytics; third-party advertising; fraud prevention, security and compliance |
Google Play Data Safety
- Collects or shares required user data types: Yes.
- Data encrypted in transit: Yes only for the production HTTPS build.
- Deletion request mechanism: Yes.
- Account creation is optional because guests can browse; account data becomes required when users opt into account features.
Declare the data inventory above under Personal info, Financial info → Purchase history, App activity, Device or other IDs, and the relevant advertising/location SDK types. For “Shared,” apply Google Play’s service-provider and user-initiated transfer exceptions carefully, but conservatively declare Google Mobile Ads data as shared for advertising.
Apple App Privacy
| Apple category | Data | Linked | Tracking | Purposes |
|---|---|---|---|---|
| Contact Info | Name, Email Address | Yes | No first-party tracking | App Functionality |
| Identifiers | User ID, Device ID | Yes / SDK-dependent | Yes for advertising SDK, conservatively | App Functionality, Analytics, Third-Party Advertising |
| Purchases | Purchase History | Yes | No | App Functionality |
| Usage Data | Product Interaction, Advertising Data, Other Usage Data | Yes when signed in; SDK-dependent otherwise | Yes for advertising data, conservatively | Analytics, App Functionality, Third-Party Advertising |
| User Content | Other User Content, Customer Support | Yes | No | App Functionality |
| Location | Coarse Location inferred by advertising provider | SDK-dependent | Yes, conservatively | Third-Party Advertising, Analytics |
If the iOS release does not ship Google Mobile Ads, remove SDK-only Device ID, Advertising Data, Coarse Location, and tracking declarations for that platform after verifying the final binary.