Shoo!: Privacy policy

Last updated 2026-10-16.

Shoo! collects the following, and nothing else.

What	Specifically	Why	Shared
App activity	Feature-used events the app logs, and which version of a setting it showed (A/B tests), sent to our own analytics server; Screen views and feature-used events the host app chooses to log; Where this installation came from: only Google Play's campaign details (for example, found on Google Play itself, or which of our apps showed the ad) and whether one of our invite links brought it; read once and sent with its events to our own analytics server	Analytics	No
App info and performance	App sessions, as Firebase Sessions reports them to Crashlytics: when the app came to the foreground and started a session, with the package name, OS and SDK versions, network type, and device manufacturer and model; Crash stack traces, native crash reports (minidumps), ANRs, breadcrumbs, and the reason Android recorded for the app's last exit: the exit reason, the app's importance at that moment, its memory use and the system's description	Analytics, Fraud prevention, security, and compliance	No
Device or other IDs	A random ID created for this app installation and sent with its events; 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; Firebase installation ID (app instance ID); Firebase installation ID, from the Firebase Installations SDK that Crashlytics brings in; it is sent with each app session and used to renew the Crashlytics installation UUID	Advertising or marketing, Analytics, Fraud prevention, security, and compliance	No

How long your data is kept

Who holds each kind of data listed above, and when it is deleted:

Device or other IDs: Our ad server keeps each ad view and tap for 35 days, linked only to a one-way code made from the device identifier with a secret key (a keyed hash), never to the identifier itself. Then that whole day's records are deleted, and the totals that remain identify no phone. A record of which ads a phone has already been shown is kept for 30 days, so the same ad is not shown to it again.
App activity, Device or other IDs: Google holds it for as long as the retention setting of our Firebase project says. When you ask for deletion, our servers ask Google Analytics to delete the data linked to your app installation's ID (the app instance ID), and the app resets its Firebase data on your phone. Our servers keep nothing else beyond the events they received, and the same request erases those.
App info and performance, Device or other IDs: Google (Firebase Crashlytics) keeps crash reports, minidumps (snapshots of memory at the moment of a crash), the installation IDs and the session data sent with them for 90 days, then removes them from its live and backup systems. We keep none of it on our own servers.

Deleting your data

You can ask for your data to be deleted at any time, without signing in: on the request page at https://zaparo.us/delete-account, or by email.

Email privacy@zaparo.us with the subject “Delete my data” and the app's name, Shoo!.
Your data in Shoo! listed above is deleted within 30 days of your request, except what the list above says is kept, for as long as it says.

Contact

Questions about this policy, or a deletion request: privacy@zaparo.us