Last updated 2026-09-26.
OurList collects the following, and nothing else.
| What | Specifically | Why | Shared |
|---|---|---|---|
| App activity | Link token opened, and the Play install referrer used to match a deferred link after install; List names, items, amounts, meal plans and remembered dishes the household created; Room name and join code the user created; 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, App functionality | No |
| App info and performance | Crash stack traces and performance diagnostics; Crash stack traces, ANRs and breadcrumbs; The app's version, and the "Firebase user agent" - device metadata, installer app info and the versions of the Firebase SDKs in the app | Analytics, App functionality, 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; Crashlytics installation UUID, attached to each crash report; FCM registration token; FCM registration token, so a push can reach this phone; Firebase installation ID, minted by the Firebase Installations SDK that Cloud Messaging depends on; The account identifier, and the public half of a key generated in the device key store; User id and room membership | Account management, Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance | No |
| Personal info | Display name - generated by default, editable by the user; Email address, and the name a provider reported, from the sign-in the person chose. Those two and nothing else: a browser provider is asked for `openid email profile` and only the address and the name are read out of what comes back. | Account management, App functionality, Personalization | No |
| Photos and videos | Profile photo the user chose to upload | App functionality, Personalization | 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
