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; the terms of service cover how you may use them. Shuv is currently an invite-only beta.
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
- Usage. Counts of Shuvs per day and per API key, your monthly allowance and credit balance. You see these in the portal; we also look at totals to plan capacity and enforce limits.
- Operational diagnostics. Our server writes one log line per request: a request ID, the type of request (with IDs removed), the result code and how long it took. These logs contain no message content, IP addresses, emails, keys or tokens, and our hosting provider keeps them for up to 7 days. We also run automated uptime checks against the service.
- Security log. A record of account actions (for example, “API key created” or “phone disconnected”) with their time, and the IP address of each sign-in.
- Network data. Our hosting provider processes your IP address to deliver the service. We record the IP address your account, each phone and each API key last connected from, and use it only for security and abuse prevention, such as blocking a network that is attacking the service.
- Connection report. If sign-in fails, the app can build a diagnostics report on your phone. It is copied only when you tap the copy button and is never uploaded automatically. It contains app and device version details and error codes, and no account details, tokens or message content.
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
- Notifications (Android 13 and later) to show incoming Shuvs.
- Do Not Disturb access (optional). Only if you turn on “bypass Do Not Disturb” in Shuv’s notification settings and grant access in Android settings. Shuv uses it only so its own notifications can sound during Do Not Disturb, and checks whether access is granted and the current Do Not Disturb mode to show notification status. It does not change your Do Not Disturb settings or read other apps’ notifications. You can withdraw access in Android settings at any time.
- Internet and network state to talk to the Shuv API and to report whether you are online in the connection report.
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:
- Google: Firebase Authentication for sign-in, Firebase Cloud Messaging for push delivery (a standard Shuv’s title, body and IDs pass through it; an encrypted Shuv passes through only as ciphertext), and Google Fonts for the web portal’s typeface. Google privacy policy.
- Cloudflare: hosts the Shuv API, its database (Workers and D1) and the request logs described above. Cloudflare privacy policy.
- Stripe: payments, as merchant of record. Stripe privacy policy.
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
- Account data, Shuvs and replies are kept while your account exists so they can appear in your history and reach your agents.
- Recorded IP addresses are deleted automatically 90 days after they were last used. Request logs are kept for up to 7 days.
- Backups. We back up the database daily and keep the 14 most recent copies in access-restricted storage; our hosting provider also keeps point-in-time recovery data for up to 30 days. Backups are used only to restore the service after a failure. Data you delete, or the data of a deleted account, disappears from all backups within 30 days, as older backups are replaced. If we ever restore a backup, we re-apply deletions made since it was taken.
- Blocks placed for abuse (an email, network or device) are kept while the block lasts and removed within 90 days after it ends.
- When an account is deleted, we keep a line in our operator log recording that a deletion happened, with the account’s random ID and the date, but no email or content. A record of a deletion request we handled (the email address and dates) is kept for one year to show it was fulfilled.
- Stripe keeps its own records of completed purchases for as long as tax and financial laws require.
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