Last updated November 20, 2026

Shuv privacy policy

Shuv is a two-way notification service. Software agents you authorize send you short messages (“Shuvs”) through the Shuv API, and you read and reply to them in the Shuv Android app (package app.shuv.android) or the Shuv web portal. Shuv is developed and operated by 13bfc3s, the developer named on Shuv’s Google Play listing. This policy covers the Android app, the web portal and the Shuv API. Shuv is currently an invite-only beta.

Want to delete your account? See Delete your Shuv account for the steps, what is deleted and what is kept.

Information we collect

Account and sign-in

You sign in with Google through Firebase Authentication, a Google service. Shuv receives your email address, whether Google has verified it, and a Firebase user ID, and uses them to identify your account and check it is invited. Firebase Authentication also keeps a sign-in record for you that includes the name, profile-photo link and Google account identifier that Google provides. Shuv does not read, display or store your name or photo, and does not download your profile picture. We never receive your Google password or access to other Google data. App-store reviewers use an email-and-password sign-in that we create for them.

If you sign in without an invite, we keep your email on a waitlist so we can invite you later. Our support staff may add short internal notes or labels to your account (for example, “beta tester”). These are used only to run the service.

Messages

The title and body of each Shuv your agents send, its priority and delivery status, and any reply you send. Standard Shuvs are not end-to-end encrypted: our server, and Google’s push service while delivering them, can technically read them. Do not put passwords, payment details, health information or other sensitive data in a standard Shuv.

Optional end-to-end encryption (preview). You can turn on encryption for a phone in the app. The phone then publishes a public key, and agents that support it encrypt each Shuv to that key before sending, so Shuv stores and forwards only ciphertext it cannot read. Replies to encrypted Shuvs can be encrypted back to the agent. Shuv still sees metadata: which account and phone a Shuv is for, when it was sent, its size, priority and delivery status. Encryption is a preview that has not been independently reviewed.

Phones and API keys

When you connect a phone, we store its push-notification token (encrypted on our server), a random device ID, a one-way hash of the phone’s credential and, if you turned on encryption, its public key. The app also sends Android’s app-specific device ID (ANDROID_ID); we keep only a one-way keyed hash of it, used only to stop a phone banned for abuse from reconnecting. For each API key you create we store its name, permissions, expiry and last-used time, and only a one-way hash of the key itself.

Purchases

Paid plans are being tested and are not yet available to the public; no real payments are taken until they launch. Payments are handled by Stripe, which acts as the merchant of record: Stripe collects your card or other payment details, billing address and email, and calculates and collects sales tax. Shuv never sees your full card number. Shuv receives and stores your Stripe customer ID, subscription status and renewal date, and for each credit-pack purchase the amount, date, status and credits granted, so we can apply your plan and show your purchase history.

Usage, diagnostics and security records

Shuv contains no advertising or behavioral analytics SDKs, uses no advertising identifiers, and does not sell or rent personal information or share it for advertising. It does not access your location, contacts, photos, microphone or camera.

Permissions on your phone

How we use information

Only to provide Shuv: to sign you in, deliver Shuvs and return your replies to the agent that sent them, apply your plan and limits, process purchases, give support, keep the service secure and prevent abuse. We may suspend accounts, or block email addresses, networks or devices, that abuse the service. We do not use message content for advertising or to train machine-learning models.

Service providers

We share information only with the providers that run Shuv, and only for that purpose:

We may also disclose information if the law requires it or to protect the safety or security of users or the service. All connections use HTTPS.

Data stored on your phone

The app keeps your Shuv history (titles, bodies and replies), its device credential and, if you use encryption, its private key on your phone, encrypted with a key held in the Android Keystore. Android cloud backup is disabled for Shuv. Uninstalling the app or clearing its storage removes this data. “Clear history on this phone” in the app removes only the phone’s copy; it does not delete your account.

Retention

Your choices and rights

You can revoke API keys and disconnect phones at any time in the app or portal; signing out of the app revokes that phone on our server. The portal’s DATA tab lets you download a copy of your data and delete your account. You can also email us to access, correct or delete your data. We respond within 30 days.

Children

Shuv is not directed to children under 13, and we do not knowingly collect information from them.

Changes

We will publish material changes on this page and update the date above before they take effect.

Contact

Privacy, deletion and support requests: c4xbrx4lc@mozmail.com