Privacy Policy

What we collect

From the sender: your name and your email address. Your email is required to send a card — it sets the Reply-To on the card email, so replies from the recipient reach you directly, and it is how we track your usage against your plan's limits when you are not signed in. If you are signed in, your usage is tracked against your account instead.

If you create a Zovwy account: your email address (sign-in link) or, if you choose "Continue with Google," the name, email address, and profile picture Google shares with us. We use this only to create and identify your account — we never see or store your Google password. Signing up also lets us attach cards you previously sent anonymously (by matching your verified email) to your new account.

When you first sign in to a new account: the country and city your connection appears to come from, and which method you used to sign in (sign-in link or Google). We record these two location fields only. We do not store the IP address they are derived from — it is not written to our database or kept in our logs.

From the card: the recipient's name, the message you write (or generate with AI), the occasion, and the language you choose. The recipient's email address is collected only if you ask us to email the card to them. If you choose "Get a link to share myself" instead, we never ask for it and no recipient address is stored against that card — you share the link yourself, and we email a copy of that link to your own address so you can find it again on another device.

From group signing: each signer's name, an optional email, their message, and — for abuse prevention — the IP address the signature was submitted from.

From delivery: whether and when a card was delivered and viewed — for a card you share yourself, only when it was created and when it was first opened, since there is no delivery for us to record, and — if the card could not be delivered — that it failed and the reason the receiving mail server gave (for example, that the mailbox does not exist). We keep this so we can show you the card did not arrive, and let you correct the address and send it again. When a card cannot be delivered we also email the address it was sent from, once, to say so — worded so that it tells you nothing about the card beyond the occasion and the recipient's name, because we cannot verify who owns that address. It never includes your message.

From how a card was sent: whether it was sent while signed in to an account or without one. This is a single label on the card, recorded once when it is sent, and is used to understand how people use Zovwy and to investigate problems. It never affects your plan or your limits.

From your use of the service: counts of how many cards you have sent and how many AI message writes you have used in the current period, the date your monthly period started (so limits reset on your own signup anniversary rather than the calendar month), and whether you have used the free plan's one-time group card. These are counts and dates only — never the content of what you wrote.

Why we collect it

To create your card and, when you ask us to, deliver it by email; to send you a copy of your own share link when you choose to hand the card over yourself; to route replies back to you, to track your usage against your plan's limits (cards, AI message writes, and group signing), to let group signers add their message to the right card, to let you sign in to and manage your account, and to prevent abuse of the signing link (the IP address on a signature exists solely for this purpose).

The country and city recorded when an account is first created are used to keep the service secure — to notice unusual sign-in patterns — and to understand where Zovwy is being used so we can operate it sensibly. They are never used to target you.

Sending a card without an account collects nothing beyond what is listed above: no location, no sign-in method, and no account is created for you.

Before sending, we check that the email addresses you enter are correctly formed and that their domain is set up to receive mail at all. That check is a public DNS lookup of the domain only — the address itself is never sent anywhere for it — and it exists so a card is not lost to a typo.

Who we share it with

We use a small number of service providers to run Zovwy, each with a specific, limited role:

• Supabase — hosts our database (PostgreSQL, in the western United States) where card, signature, and account data lives, and handles account sign-in (sign-in link and Google OAuth) on our behalf.

• Google — if you choose "Continue with Google" to sign in, Google authenticates you and shares your name, email, and profile picture with us; we never see your Google password.

• Resend — delivers the card, notification, and sign-in emails on our behalf.

• Anthropic (Claude API) — when you use AI message writing or translation, your message text is sent to Anthropic to generate or translate it. It is not used by Zovwy or Anthropic to train AI models.

We do not sell your data, and we do not share it with anyone beyond these processors.

How long we keep it

A card and its data are kept until the sender deletes it. If you would like a card, or all data associated with you, deleted sooner, contact us and we will take care of it.

Your rights

Wherever you are, you can ask us what data we hold about you and ask us to delete it — email cards@zovwy.com and we will respond promptly. If you are in the EU/UK or California, this covers the access and deletion rights GDPR and CCPA give you; we intend to honor the same standard for everyone, not just where required to.

Children

Zovwy is not directed at, and is not knowingly used to collect data from, children under 13.

Changes to this policy

If this policy changes, we will update the "Last updated" date below and, for material changes, make a reasonable effort to let existing users know.

Related: Terms of Service · Cancellation & Refund Policy

This page is a plain-language template and not legal advice. It will be reviewed by a qualified professional before commercial launch.

Last updated: September 29, 2026