Zorzal does one narrow thing: it lets one person you trust reach you with a loud alarm, even through Do Not Disturb or a silent ringer. We collect only what that requires.
Your name and email address. You sign in with Google or an email link, and we keep the name and email that sign-in provides. They're shown only to the people you invite — and, in the other direction, to the person who invited you — so everyone knows who they're reaching and who can reach them.
Your trills. When you send a trill, we store the short reason you typed so it can be delivered, and for a little while after. We can't read it — see below.
A device identifier. Each install gets a technical ID we use to wake the right device. It holds no content, and no sender ever sees it.
Reasons are end-to-end encrypted. The message you type is locked on your device to a key only the person you're reaching holds. Zorzal relays the encrypted bytes and checks their length — we can't read them, and neither can anyone in between.
Trills are deleted automatically 7 days after they're sent — reason and all. There's no standing conversation history, just a short delivery trail that erases itself.
If you send a diagnostics report, we keep it for 30 days and then delete it.
Zorzal runs on Google's Firebase platform, so data is stored on Google Cloud. Sign-in uses Google authentication (or a passwordless email link), and Google's reCAPTCHA (as part of Firebase App Check) verifies that requests come from a real browser, to block automated abuse.
To access, export, or delete your data, visit our account page.
We're setting up a contact email and will post it here. For now, the fastest way to reach us is the Send diagnostics button in the app's setup screen — it sends us the technical details we need (plus an optional note you type), without you having to explain anything by hand.