Created
April 28, 2026 05:04
-
-
Save dropoutninja/af34618ed85d14a431d6f6d6244ae464 to your computer and use it in GitHub Desktop.
arcade-pocket-privacy-policy.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Privacy Policy — Arcade Pocket | |
| Effective date: [28-04-2026] | |
| Developer: [Jovik] | |
| Introduction | |
| This policy describes how Arcade Pocket (“the app”) handles information when you use it. The app is an offline arcade-style game collection. | |
| Information we collect | |
| We do not deliberately collect, store, or transmit personal information such as your name, email address, phone number, or precise location through the app. | |
| The app runs locally on your device. We do not operate our own servers for this app’s gameplay. | |
| Internet and third parties | |
| The version of Arcade Pocket described here does not request network permission for gameplay and does not integrate third-party analytics, advertising, or social-login SDKs. | |
| Google Play: When you install or update through Google Play, Google processes certain information according to Google’s own policies, not ours. See: | |
| https://policies.google.com/privacy | |
| Device storage | |
| Game state or settings may be stored only on your device. Android backup behavior depends on your device settings and allowBackup in the app manifest. | |
| Children’s privacy | |
| The app is intended for general audiences. We do not knowingly collect personal information from children. If you believe we have, contact us and we will help remove it if applicable. | |
| Changes | |
| We may update this policy if the app changes (for example, if new features collect data). The new version will be posted here with an updated effective date. | |
| Contact | |
| Questions about this policy: [incrementalexperience@gmail.com] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment