What we keep, and what we don’t.

Who this covers

This applies to the public site, the web console, and the iOS and Android apps. If you create an account, the same record is used on every surface.

What we collect

• Account: email, sign-in provider, and a display name you can edit.
• Devices: a push token, platform, and a name so we can reach the phone you picked.
• Agent keys: a hash of the key and which phone it is pinned to. The raw key is shown once.
• Handoffs: label, optional message and agent metadata, fire time, delivery mode, and delivery status.
• Usage: how many agent-created messages and alarms have used your monthly handoff allowance.
• Public-site analytics, when enabled: aggregate page views, referring site, approximate country, device and browser type, and performance timings.
• Billing, if you pay: payment-provider customer and subscription ids. We do not store card numbers.

We do not sell personal data or use your handoff content to train AI models. Send only the information needed for the notification; avoid passwords, API keys, or other sensitive content.

Why we use it

We use this information to sign you in, deliver handoffs to the phone you choose, display history, enforce usage limits, support you, and protect the service from abuse. Technical logs may include request timing, IP addresses, and errors used for security and reliability.

The public site may use Cloudflare Web Analytics to understand traffic and page performance. It does not use analytics cookies, local storage, fingerprinting, or advertising profiles. Product adoption is reviewed from aggregate counts already held for accounts, linked phones, connected agents, and handoffs; those reports do not expose account identities.

Storage on your device

We store sign-in credentials and preferences to keep you signed in and remember your theme. Native apps also keep device registration and scheduled alarms. Notification text may appear on your lock screen according to your phone settings.

Where it lives

The public site and API use Cloudflare, while the application service and database use AWS and Supabase. Push goes through Apple or Google so the phone can wake. Payment, if you use it, goes through the provider shown at checkout.

How long we keep it

Account data stays until you delete the account. Handoff history stays with the account. A revoked agent key stops working immediately; the hash may remain until the account is removed.

Deleting an account removes its active application records. Infrastructure backups and security or payment records may persist according to provider retention and legal obligations. Deletion does not remove messages already delivered to a phone or information you shared elsewhere.

Your choices

You can edit your account name, revoke agent keys, unlink phones, change notification permissions, and delete your account. Depending on where you live, you may have rights to access, correct, export, or erase personal data. Use Email us to make a request; we may verify account ownership before acting.

Our infrastructure providers may process data outside your country. We share information with them to operate the service, or when legally required, rather than for advertising.

Deleting your account

Open Settings and choose Delete account on the web console or in the phone apps. That removes the auth user and, with it, phones, keys, alarms, and usage. Sign-out only clears the session on that device.

Contact

Questions about this page: Email us.