Lumi: Privacy policy

Last updated 2026-10-16.

Lumi collects the following, and nothing else.

What	Specifically	Why	Shared
App activity	A score this user submitted to an app-defined board, when they achieved it, and an optional opaque proof string the app supplies - keyed on their Zaparo ID user id; Challenges you send: the score to beat, the climb it was set on, and who beat it; Climb results: the score, distance, level, dewdrops and close calls, and the moments you switched walls that the score is checked from; Feature-used events the app logs, and which version of a setting it showed (A/B tests), sent to our own analytics server; Link token opened, and the Play install referrer used to match a deferred link after install; Recorded runs a player uploads through GhostPoolClient: the game, the language and the replay the app recorded (in a word game the word played, each guess and when it was made), keyed on their Zaparo ID user id; Reports about your nickname or picture, whether your nickname or picture is hidden while it is reviewed, and the record of a nickname removed from you: which one, why, when, and the 30-day lock on the new one; Reports you send about someone's nickname or picture: what you reported, the reason you write, the app, and a weight from how new your Zaparo ID is and how often your earlier reports were found fine; 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; 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.; Which leagues this user is in, when they joined, and the scores they pushed into them; and, where the app uses weekly divisions, the tier this user stands in and each week's total with the group it was played in - keyed on their Zaparo ID user id	Account management, Analytics, App functionality, Fraud prevention, security, and compliance	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; FCM registration token; 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; The account identifier, the public half of a key generated in the device key store, and what registered it: the kind of client (phone app, browser, desktop app), its operating system and the app version	Account management, Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance	No
Personal info	Earlier nicknames, with the app and the date each was chosen, and whether you kept one after being told it might offend; Email address, name (with the given and family name), profile picture address and language a provider reported, and the identifier that provider gives the account, from the sign-in the person chose, and nothing else of the account. An app never receives that identifier itself, only a one-way code made from it for that app alone. On Android an app may sign the person in with Google on its first launch without opening a screen: the phone's Google account is offered through the system's Credential Manager, the person can decline it, and K reads these values out of the ID token Google issues for that sign-in. An email address belongs to one Zaparo ID only.; Nickname: one for each app, starting from a main nickname set on the Zaparo ID page, never made up for you; signed in with Google, it starts from your Google first name only; The display name and profile picture reference the app writes into a recorded run's label, shown to other players of that app beside the run; The nickname shown beside your score on the leaderboard and on a challenge you send	Account management, App functionality, Fraud prevention, security, and compliance, Personalization	No
Photos and videos	Profile photo the user chose to upload	App functionality, Personalization	No

How long your data is kept

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

App activity, Personal info: Your climb results (the score, distance, level, dewdrops, close calls, and the moments you switched walls that the score is checked from), the challenges you sent and who beat them, and your weekly league best stay on our servers until you delete your data in this app, a deletion request is carried out, or your guest identity is closed after a year unused. The same deletion erases all of them, takes your climbs out of the pool of recorded opponents, and stops the challenge links you shared from working. Your best score, achievements, and settings stay on your phone and are never sent.
App activity, Device or other IDs, Personal info: Our sign-in service keeps it for as long as your Zaparo ID exists. Your Zaparo ID is shared by every Zaparo app you use, so deleting your data in one app removes only that app's link to it. Once no app has your data, you can delete your Zaparo ID on your Zaparo ID page: it's deleted 30 days later, with everything still linked to it, unless you cancel before then. When a guest identity is closed after a year unused, its device keys are deleted with it.
App activity: On our servers, until you delete your data in this app, a deletion request is carried out, your guest identity is closed after a year unused, or the app removes the leaderboard. When your data is deleted, your places on the leaderboards stay so other players' places don't shift, shown as an anonymous “Deleted player” with nothing that leads back to you.
App activity, Personal info, Photos and videos: On our servers, profile pictures included. A picture you replace is moved to separate storage that is not backed up. Your nickname in an app, its earlier versions, the reports about it and any removal record are deleted with that app's data; your main nickname, its history and everything else go when you delete your profile, and a moderator's removal deletes the item itself. A report you send is deleted with the data of the app you sent it from. Taking part in a live session is kept as one hashed key per person, valid only in that app, which expires after at most 30 days and is deleted when you leave, when it expires, or with your profile.
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: On our servers, until you delete your data in this app, a deletion request is carried out, or your guest identity is closed after a year unused. A club only you are in is then deleted. In a club other people are in, your membership, your scores, and the club itself if you started it stay for them, under an anonymous “Deleted player” that can't be traced back to you, so their leaderboards still add up; your place in a weekly league stays the same way. Your own tier and whether you moved up or down are deleted. Leaving a club you own deletes it, and a club with no one left in it is deleted too.
App activity: On our servers. A link's record stays until the link expires, is revoked, or the account that made it deletes its data; nothing else is kept.
Device or other IDs: The notification token stays on our servers until your phone unregisters it, you delete your data in this app, a deletion request is carried out, or your guest identity is closed after a year unused.
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.
App activity, Personal info: On our servers, which keep your newest 500 recorded runs in each app, until you delete them, you delete your data in this app, a deletion request is carried out, or your guest identity is closed after a year unused.

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, Lumi.
If you signed in, send it from the email address you signed in with, or write that address in the message, so we can find your data by it.
Your data in Lumi listed above is deleted within 30 days of your request, except what the list above says is kept, for as long as it says.
Deleting your data in Lumi doesn't delete your Zaparo ID, which is shared by every Zaparo app you use. Once no app has your data, you can delete your Zaparo ID too: start at https://zaparo.us/delete-account, which takes you to your Zaparo ID page.

Using the apps without signing in

If you use the app without signing in, you use it with a guest identity. If you don't open the app on any device for a year, your data in that app is deleted and your guest identity is closed.
If the app is still on your phone, it sends you a notification 7 days before that happens. If the app can't notify you, nothing is deleted.
None of this happens while you still have credits you bought and haven't used, Unlimited, or an active subscription in the app.
A record of what you bought (the product, the price, and the date) is kept for tax purposes, but it's no longer linked to you.

Deletion requests

At https://zaparo.us/delete-account, anyone can ask for their data in one app to be deleted, without signing in. If you choose to delete your Zaparo ID there, we confirm your email address and send you to your Zaparo ID page, where you sign in and make the request.
We email you a link, and the request counts only once you open it.
A confirmed request is carried out within 30 days. Until then you can cancel it with the cancel link in that email, or by signing in on your Zaparo ID page at https://id.zaparo.us.
A request for one app's data does what “Delete my data from this app” in the app's settings does, and that setting is still the way to do it right away. Credits you bought and haven't used, Unlimited, an active subscription, and free credits you got for signing in with Google and haven't used are kept, and come back the next time you sign in to the app with the same Zaparo ID. A guest's are kept too, but can't come back, because a guest can't sign in again.
Your Zaparo ID page lists every app you use with your Zaparo ID. Once you've deleted your data in each of them there, you can ask for your Zaparo ID itself to be deleted. It's deleted 30 days later with everything still linked to it, including any credits, Unlimited, or subscription you still have. A record of what you bought is kept for tax purposes, no longer linked to you. Until then you can cancel on that page, in any Zaparo app, or with the link in our email. We email you on the day you ask, 7 days before, and when it's done. Signing in or opening an app doesn't cancel it, and a Google Play subscription keeps charging you until you cancel it in Google Play.

Contact

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