Last updated 2026-09-26.
Zaparo Keep in Touch collects the following, and nothing else.
| What | Specifically | Why | Shared |
|---|---|---|---|
| App activity | Screen views and feature-used events the host app chooses to log; Which applications within this one tenant the account has been seen in. Recorded when an application registers a device or completes a sign-in under its own application id, so `me().apps` can answer it back to the person. | Account management, Analytics | No |
| App info and performance | Crash stack traces, ANRs and breadcrumbs | Analytics, Fraud prevention, security, and compliance | No |
| Device or other IDs | An identifier for the phone, sent with an ad request and with the report that an ad was shown or tapped. It is the advertising identifier only where the app has been declared for it in Play; everywhere else it is an identifier this SDK generates for that install alone, which no other app can read and which dies when the app is removed. Neither is stored as it arrives: the server keeps a keyed hash of it, so the ads cannot be traced back to the identifier.; Crashlytics installation UUID; FCM registration token; Firebase installation ID (app instance ID); The account identifier, and the public half of a key generated in the device key store | Account management, Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance | No |
You can ask for your data to be deleted at any time, at the address below.
Questions about this policy, or a deletion request: privacy@kbsoap.com
