APPSINITYPrivacy requirements
Two privacy obligations exist on Appsinity and they are easy to confuse: what you tell players about your own software, and what Appsinity already does with the data flowing through its platform.
Open Appsinity StudioWhat you must provide
| Requirement | Where it lives | Blocking? |
|---|---|---|
| Privacy policy URL | Privacy section of the listing | Yes, until set the section is incomplete |
| Privacy disclosure text | Privacy section | No, but shown as not provided |
| Collection declaration | Eleven data categories | Yes, part of submission |
| Account creation fact | Account group | Yes, part of submission |
| Encryption in transit fact | Account group | Yes, part of submission |
| Support email | Contact section | Yes, required for publishing |
| Country | Contact and verification | Yes, part of the identity record |
| Content rating contact | Content rating form | Recommended |
The two attestations
Submission requires two explicit confirmations, and both must be ticked for the section to count as done. They are the platform's only written record that a declaration was made deliberately.
finalDeclarationAccurate: the declaration as submitted is accurate.finalDeclarationFalseInfo: you are not knowingly submitting false information.
What Appsinity collects anyway
Running the store means collecting platform data. The privacy policy names these categories: account information, developer content, build information, ratings and reviews, usage data such as timestamps and request types, and device and browser signals such as browser type and operating system version used for compatibility and security analysis.
- Listing events on your titles are counted per source and per country for your analytics; that is the mechanism behind Listing traffic and analytics.
- Security logs are retained for a reasonable period to support abuse prevention and incident investigation.
- Data attached to inactive accounts or unpublished content may be removed, anonymised or archived.
- Players can request deletion of their account and data, correction of inaccurate information, and removal of infringing or impersonating content through official support channels.
Third-party code inside your build
Anything shipped inside your APK or AAB is your declaration to make, including analytics SDKs, ad networks, crash reporters and social sign-in. The platform's own advertising measurement is documented under Ads policy.
Children and teen safety
The store maintains a teen-safe standard, and the rating form asks directly whether the app is designed for children under 13 and whether parental consent is required for any feature. If you answer yes to either, the data-safety declaration becomes the operative promise: the categories you collect from those users are exactly what a parent will be shown.
Frequently asked questions
Do I need to host my own privacy policy?
Yes. The completion rule requires a URL, and the listing displays it. A link to a page that 404s leaves the section technically satisfied and practically broken.
Is there a GDPR or DPDP specific field?
No. There is no region selector, consent banner configuration or legal-basis field in Studio. Your policy page carries that work.
Does Appsinity sign a data processing agreement?
There is no DPA process on the platform. The relationship is governed by the Terms of Use and the privacy policy as published.
Where do players send a deletion request about my game?
To Appsinity through official support channels for platform data, and to your support email for data your own software holds. Both routes are expected to work.
Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]