AppsinityAPPSINITY
Policies and safety

Data safety

Data safety is a declaration, not an audit. Appsinity shows fourteen rows on every listing built from the fields you ticked in Studio, and states plainly that the developer made them up.

Open Appsinity Studio
On this pageThe fourteen rows players seeWhat Studio actually savesThe completion ruleHow the panel is labelledCompleting the sectionFrequently asked questions

The fourteen rows players see

Eleven of them are collection claims with a collected / not collected pair. Three are account-level facts with their own vocabulary.

Field writtenLabel on the listingKindCollected valueAbsent value
collectsAnalyticsAnalyticscollectCollectedNot collected
collectsContactsContactscollectCollectedNot collected
collectsCrashLogsCrash logscollectCollectedNot collected
collectsDeviceInfoDevice infocollectCollectedNot collected
collectsEmailEmailcollectCollectedNot collected
collectsHealthDataHealth datacollectCollectedNot collected
collectsLocationLocationcollectCollectedNot collected
collectsMediaFilesMedia filescollectCollectedNot collected
collectsPaymentInfoPayment infocollectCollectedNot collected
collectsPersonalInfoPersonal infocollectCollectedNot collected
collectsPhonePhonecollectCollectedNot collected
allowsAccountCreationAccount creationaccountSupportedNot offered
privacyDisclosurePrivacy disclosureaccountProvidedNot provided
encryptedInTransitEncryption in transitaccountEncryptedNot encrypted
Note: The panel prints a tally of how many data types are declared as collected, so a listing that ticks everything is visibly ticking everything.

What Studio actually saves

The privacy section writes one object onto the listing document. It carries the collection switches above plus the fuller declaration you fill in:

  • collectsUserData and collectedDataTypes: whether you collect anything at all, and which categories.
  • dataUses: what you use it for.
  • sharesData and sharedWith: whether it leaves your control and to whom.
  • securityPractices: the safeguards you rely on.
  • privacyPolicyUrl: the public policy players can read.
  • privacyDisclosure: the disclosure text itself.
  • finalDeclarationAccurate and finalDeclarationFalseInfo: the two attestations.
  • submitted and updatedAt: the commit flag and its timestamp.

The completion rule

The privacy section counts as done only when four things are all true. A partially filled form shows as incomplete rather than as done.

privacy.done =
  privacy.submitted
  && privacy.privacyPolicyUrl
  && privacy.finalDeclarationAccurate
  && privacy.finalDeclarationFalseInfo

badge: done | inc (a URL is present but the rest is not) | none
Watch out: Both attestations must be ticked, including the one phrased as a negative. Its label asks you to confirm you are not knowingly submitting false information; leaving it unticked keeps the section incomplete forever, which surprises most first-time publishers.

How the panel is labelled

The store does not verify declarations. The panel states that what players are reading was declared by the developer and is not independently verified, and links the Appsinity privacy policy for the platform's own collection. Do not treat the row list as a legal opinion.

Not available: There is no per-field verification, no automatic scan of your traffic, and no crawler checking your privacy policy URL. A false declaration is a policy violation that will only be discovered by a complaint.

Completing the section

  1. Inventory the SDKs. Every analytics, crash, ads and payment library in the build reads something. If you cannot name the SDK, open the build and find it before declaring.
  2. Answer collection per category. Use the eleven collection switches. When a category is genuinely never touched, mark it not collected rather than leaving it blank.
  3. Write the policy. Host an actual privacy policy page and paste its URL. The completion rule needs it.
  4. State sharing explicitly. Named recipients beat 'partners'. If you share with ad networks, list them.
  5. Tick both attestations. Accuracy and no-knowing-false-information.
  6. Submit, then re-read the listing. The tally and the fourteen rows are what players will judge you on.

Frequently asked questions

My game collects nothing. What do I tick?

Turn every collection switch to not collected, set account creation to not offered if it really is absent, still provide a privacy policy URL and both attestations, and submit. Encryption in transit should reflect reality: a plain HTTP fetch is not encrypted.

Do crash logs count as collected data?

Yes, if a crash reporter ships them anywhere. Declaring Crash logs as collected with the SDK named is the accurate answer.

Does Appsinity check my declarations?

No. The panel says the declaration is developer-supplied and not independently verified. See Privacy requirements for the surrounding obligations.

The privacy section will not turn green.

Almost always a missing policy URL or one unticked attestation; both are hard requirements in the completion rule above.

Related documentation

Privacy requirementsContent ratingsPermissionsSecure developmentPrivacy policy URL
Need help?

Developer publishing support: [email protected]
General support: [email protected]
Partnerships: [email protected]