Google Play Data Safety
Apple App Privacy
India & Global Stores
App Store & Google Play Data Safety Disclosures
1. Google Play Console Data Safety Questionnaire (Exact Answers)
Developers submitting Jaap Karma to the Google Play Store Console must select the following exact answers in the Data Safety section:
| Google Play Console Question | Exact Required Selection | Statutory & Technical Justification |
|---|---|---|
| Does your app collect or share any of the required user data types? | 👉 Select: "No" | Jaap Karma does not collect, record, or share any user data. All records are processed and stored strictly on the user's local physical device. |
| Is all of the user data collected by your app encrypted in transit? | 👉 Select: "Not applicable" (or "Yes") | No user data is ever transmitted over network connections; the application does not have internet permissions. |
| Do you provide a way for users to request that their data be deleted? | 👉 Select: "Yes" | Users can delete 100% of their data immediately at any time by clearing application data in their device settings or uninstalling the app. Hosted URL: User Rights & Deletion Portal. |
2. Detailed Data Categories Breakdown (All 14 Categories: "NO")
The following declarations are officially submitted to Google Play Console reviewers for every data type:
| Data Category | Sub-Types Covered | Collected? | Shared? | Statutory Declaration for Store Reviewers |
|---|---|---|---|---|
| Location | Approximate, Precise GPS | ❌ NO | ❌ NO | No location APIs or permissions are declared or accessed. |
| Personal Info | Name, Email, Phone, Address, Religious / Spiritual beliefs | ❌ NO | ❌ NO | No account registration exists. Selected sacred mantras and devotion remain strictly on-device in the local SQLite database. |
| Financial Info | Credit card, Bank account, Billing history | ❌ NO | ❌ NO | App is 100% free with zero in-app purchases and zero payment gateways. |
| Health & Fitness | Health info, Fitness records | ❌ NO | ❌ NO | No Google Health Connect or Apple HealthKit integration. |
| Messages | Emails, SMS, In-app chats | ❌ NO | ❌ NO | No messaging features or SMS permissions. |
| Photos & Videos | Device photos, recorded videos | ❌ NO | ❌ NO | No camera access or photo gallery permissions requested. |
| Audio Files | Microphone recordings, voice notes | ❌ NO | ❌ NO | Zero microphone access. App only plays bundled offline click sound assets. |
| Files & Docs | Shared device storage documents | ❌ NO | ❌ NO | App writes exclusively to its own sandboxed application directory. |
| Calendar | System calendar events | ❌ NO | ❌ NO | No calendar access requested. |
| Contacts | Address book, contacts list | ❌ NO | ❌ NO | Zero contact permissions requested. |
| App Activity | Screen interactions, in-app search, clickstream | ❌ NO | ❌ NO | Zero analytics SDKs (no Firebase, no Mixpanel, no Facebook SDK). |
| Web Browsing | Web browsing history | ❌ NO | ❌ NO | Zero in-app browser trackers. |
| App Diagnostics | Crash logs, performance metrics | ❌ NO | ❌ NO | Zero Crashlytics or Sentry telemetry. Errors handled locally on device. |
| Device IDs | IMEI, MAC address, Advertising ID (AAID) | ❌ NO | ❌ NO | Zero hardware or advertising identifiers harvested. |
3. Line-by-Line Android Permissions Justification
Google Play review teams require technical declarations for sensitive and special permissions. The table below provides the exact text for submission to Google Play Policy Reviewers:
| Android Permission | Permission Group | Declaration Text for Google Play Reviewers |
|---|---|---|
android.permission.VIBRATE |
Normal | Used strictly for haptic feedback during bead counting and completing a 108-bead round. This tactile vibration is the core accessibility feature of the digital mala, enabling blind, visually impaired, and meditating devotees to count mantras with closed eyes without looking at the screen. |
android.permission.POST_NOTIFICATIONS |
Runtime (Android 13+) | Used strictly to post optional local prayer reminders scheduled by the user (e.g., morning Brahma Muhurta or evening Sandhya). All notifications are generated and scheduled strictly on-device using the operating system's local notification daemon. Zero push notification servers (no FCM) are used. |
SCHEDULE_EXACT_ALARM / USE_EXACT_ALARM |
Special App Access | Required by the Flutter local notifications plugin to trigger user-configured prayer reminders at exact times selected by the devotee (e.g., 4:00 AM) without being suppressed or delayed by Android battery optimization / Doze mode. |
4. Apple App Store Privacy Nutrition Labels
When completing the App Privacy section in App Store Connect for iOS submissions:
🍏 App Store Connect Questionnaire Steps
- Log in to App Store Connect → Navigate to App Privacy.
- Click "Get Started".
- When prompted: "Do you or your third-party partners collect data from this app?"
👉 Select: "No, we do not collect data from this app". - Publish the App Privacy response.
Resulting App Store Badge:
"Data Not Collected: The developer does not collect any data from this app."
5. Architectural Proof: Zero Internet Egress
For independent cyber security auditors, store reviewers, and security researchers:
- The Android Manifest file (
android/app/src/main/AndroidManifest.xml) intentionally does NOT declare<uses-permission android:name="android.permission.INTERNET"/>. - Under the Android operating system security model, any application that does not declare this permission is physically prevented by the Linux kernel sandbox from creating network sockets, transmitting TCP/UDP packets, or contacting external servers.
- Zero egress can be verified via Wireshark, mitmproxy, or Android Studio Network Profiler.
6. Developer Review & Audit Inquiries
🛡️ Store Compliance Support
Compliance Team
Jaap Karma App Store Operations
Developer Email
[email protected]
Public Privacy URL
Privacy Policy URL
Public Deletion URL
Data Deletion URL