Privacy
Privacy information is not final until the production data practices are confirmed.
This route exists so the final privacy notice has a stable home, but it intentionally does not invent operator identity, retention promises, analytics behavior, cookie usage, subprocessors, or international-transfer claims that have not yet been confirmed.
Pre-launch draft
This is not the final privacy notice and should not be relied on as one. It is intentionally noindex. The owner must confirm the actual launch configuration and obtain appropriate review before this page is converted into the public policy.
Facts the final notice must cover
The final policy should describe only practices that are actually enabled in production.
- Which public app-store data is stored, why it is stored, and the approved retention/archive approach.
- Whether accounts are enabled and, if so, what account/profile data is retained and how deletion or export requests are handled.
- Which analytics, cookies, local storage, monitoring, and email services are actually enabled.
- The selected hosting, database, Redis, analytics/monitoring, and other subprocessors plus relevant data-location or transfer facts.
What AppTrendKit already distinguishes publicly
Public research pages identify observed store information separately from modeled estimates and expose methodology/limitations where estimates exist. That product transparency does not replace a reviewed privacy notice for user or account data.