Play Data Safety — Bachat

Generated 21 July 2026 by /kit-generate-legal, from the SDKs and endpoints actually wired in the build. Re-run after toggling anything in KitConfig or adding a table/endpoint — a form that no longer matches the app is the exact thing Play removes apps for.

Open this side-by-side with Play Console → App content → Data safety and copy the answers.

Data collection and security

Question	Answer
Does your app collect or share any of the required user data types?	Yes
Is all of the user data collected by your app encrypted in transit?	Yes
Do you provide a way for users to request that their data is deleted?	Yes

Deletion detail to enter: In-app via Profile → Delete account, which permanently erases the account, all tax records and all receipt images immediately. Users may also email team@morpheralabs.com. There is no retention window.

Data types collected

Only the categories below are active. Everything not listed here must be left unchecked.

Personal info → Name

Collected: Yes · Shared: No · Required: No (only when signing in with Google)
Purposes: App functionality, Account management
Source: Google Sign-In

Personal info → Email address

Collected: Yes · Shared: No · Required: Yes
Purposes: App functionality, Account management
Source: Supabase Auth, Google Sign-In

Personal info → User IDs

Collected: Yes · Shared: No · Required: Yes
Purposes: App functionality, Account management, Analytics
Source: Supabase user ID; RevenueCat anonymous purchase ID

Financial info → Purchase history

Collected: Yes · Shared: No · Required: No
Purposes: App functionality
Source: Google Play Billing via RevenueCat

Financial info → Other financial info

Collected: Yes · Shared: No · Required: Yes
Purposes: App functionality
Source: tax_entries — merchant name, amount paid, tax amount, date, category
Do not skip this one. These are the user's own spending records and are the reason the app exists. Declaring the app as collecting no financial data would be false.

Photos and videos → Photos

Collected: Yes · Shared: No · Required: No (entries can be saved without a receipt)
Purposes: App functionality
Source: Receipt images captured or picked by the user, stored in a private AWS S3 bucket
Note: text recognition runs on-device; only the image is uploaded.

App activity → App interactions

Collected: Yes · Shared: No · Required: No — user can opt out in Settings → Analytics
Purposes: Analytics
Source: PostHog, Firebase Analytics

App info and performance → Crash logs

Collected: Yes · Shared: No · Required: No
Purposes: Analytics, App functionality (diagnostics)
Source: Firebase Crashlytics

App info and performance → Diagnostics

Collected: Yes · Shared: No · Required: No
Purposes: Analytics, App functionality
Source: Firebase Crashlytics (device model, OS version, app build)

Device or other IDs → Device or other IDs

Collected: Yes · Shared: No · Required: Yes
Purposes: Analytics, App functionality
Source: Firebase/PostHog device identifiers; Firebase Messaging push token; a device identifier recorded in receipt_versions to evidence which device uploaded a receipt

Categories to leave UNCHECKED

Verified absent from the build — do not tick these:

Location (approximate or precise) — no location permission is requested. Note: IP-derived coarse location by analytics providers is standard telemetry and is disclosed in the privacy policy; Play does not require it under Location, which covers device location APIs.
Contacts, Calendar, SMS or call logs
Audio, Music files, Voice or sound recordings
Health and fitness
Web browsing history
Installed apps
Files and docs (receipts are declared under Photos)
Payment info — card details never reach the app; Google Play handles payment entirely.
Race/ethnicity, political or religious beliefs, sexual orientation
National identification number — the app never asks for a CNIC.

Security practices section

Question	Answer
Is data encrypted in transit?	Yes — all traffic is HTTPS/TLS
Can users request data deletion?	Yes — in-app, immediate
Has your app been independently validated against a security standard?	No

Before you submit

Privacy policy URL — host playstore/privacy_policy.html and paste the URL under App content → Privacy policy. Play rejects submissions without one.
Data deletion — under App content → Data deletion, point at the hosted policy (Section 4 describes the in-app flow) and provide team@morpheralabs.com as the request address.
KitConfig.PRIVACY_URL and TERMS_URL are still https://example.com/.... Update them to the hosted URLs, or Settings → Privacy opens a dead link on a shipped build.