Play Console
Play Data Safety mapping
Last updated 22 August 2026
Play Console, App content, Data safety asks how Digital Darzi collects, shares, and handles user data. This page is the mapping for the default ShipKaro Android Kit SDKs used by the app. Adjust it if a module was disabled in KitConfig, or if our own code starts collecting extra fields.
This is guidance, not legal advice. We are responsible for the accuracy of the Play declaration. Re-check it whenever an SDK is added.
Data the app itself stores
Besides the kit SDKs, Digital Darzi stores shop records that the tailor enters: customer names and mobile numbers, measurements (naap), garment and fabric notes, prices, advances, delivery dates, and shop profile details. That data stays in the signed-in account so the shop can search it later. It is not sold.
Per-SDK data collection
| SDK | Data type (Play category) | Collected | Shared | Purpose |
|---|---|---|---|---|
| Supabase Auth | Email address | Yes | No | Account management |
| Google Sign-In | Name, email, photo | Yes | No | Account management |
| RevenueCat | Purchase history | Yes | No | App functionality |
| PostHog | App interactions, device IDs | Yes | No* | Analytics |
| Firebase Analytics | App interactions, device IDs | Yes | No* | Analytics |
| Firebase Crashlytics | Crash logs, diagnostics | Yes | No* | Crash diagnostics |
* "Shared" in Play's sense means transfer to a separate company. Sending data to our own analytics processor is collection, not sharing, but we still confirm this against each provider's current data-processing terms.
Form answers (typical kit defaults)
- Does your app collect or share data? Yes
- Is data encrypted in transit? Yes. All SDKs use HTTPS/TLS.
- Can users request data deletion? Yes. Settings, Account, Delete account calls delete_my_account(), which removes the row from auth.users. Related tables cascade from there. The app then clears the Room cache, DataStore, and the encrypted store that holds the screen-lock PIN. People who already uninstalled the app can use https://thedigitaldarzi.com/account-deletion.
- Is any collected data required? Email is required only if auth is enabled (KitConfig.AUTH_ENABLED). Analytics is optional. Users can opt out in Settings, Privacy.
Account deletion URL
Play requires a URL that anyone can reach without installing the app, because the people most likely to want deletion are the ones who already uninstalled it. An in-app button on its own does not satisfy the policy.
Declare this URL in Play Console, your app, Data safety, Data deletion:
https://thedigitaldarzi.com/account-deletion
support@thedigitaldarzi.com appears on that page and must be a mailbox somebody actually reads. A deletion request that bounces is worse than no page at all, and Play does check the link resolves.
What the deletion page covers
It lists what is deleted immediately: the account, customers, measurements, orders, shop profile, referral code, and everything on the phone including the PIN. The one thing that is not deleted: records of subscription payments, kept with the name and account removed. Deleting the record of money that changed hands would make refunds, chargebacks and tax records unanswerable. Play accepts retention for a stated legal reason. It does not accept silence about it.
It also tells people to cancel their Play subscription separately. Google holds a subscription against the Google account, not against ours, so deleting an account here does not stop the billing. The in-app confirmation dialog says the same thing, for the same reason.
When modules change
- Disabled auth: remove the Supabase / Google rows.
- Disabled analytics: remove PostHog / Firebase Analytics rows. Crashlytics may stay if crash reporting is still on.
- Added an SDK: add a row and re-review the form.