Draft document — not yet published. This page was generated from an inspection of the ZynPey app's source code (permissions, database models, dependencies, and its in-app privacy disclosures) and is written to be factually accurate about what the app does today. It is not a substitute for legal review. Every section marked like this needs a real value filled in, and the checklist below lists the judgment calls a qualified professional should confirm before this page goes live.

Confirm before publishing

These are the open questions this draft could not answer on its own — resolve them (ideally with a lawyer familiar with your target markets) before this policy is linked from a live app store listing.

  1. Publisher identity: name, support email, and registered address are set (ZynZ Studio, zynzstudio@gmail.com, Bangalore). Still needed: business type (individual/sole proprietor vs. registered company) — this affects which of your target markets' disclosure requirements apply.
  2. Target markets: which countries/regions ZynPey will actually be published in. This determines which laws genuinely apply — e.g. GDPR/UK GDPR (EU/UK users), CCPA/CPRA (California), India's DPDP Act 2023 (India) — and Sections 8, 12, and 15 should be revised to match.
  3. Governing law: which jurisdiction's law governs this policy and the companion Terms & Conditions.
  4. Minimum age: confirm the minimum age policy for your target markets and whether any children's-privacy law (e.g. COPPA) requires additional language beyond Section 14.
  5. Store consistency: the Google Play Data Safety form and Apple App Privacy "nutrition label" must be filled out to match this document exactly — in particular the READ_SMS declaration, which Google separately requires a Permissions Declaration Form for.
  6. Review cadence: confirm who owns keeping this page in sync with the app as features change, and revisit it before every store submission that adds a permission, SDK, or data flow.