Privacy Policy
Last updated: 16 November 2026
LightVow holds things people wrote for someone they love. This page says exactly what we store, where it physically lives, who else can touch it, and how to get it back or have it erased. The controller is Ravid Zer, a sole trader registered in Israel; write to hello@lightvow.com about anything here.
What we collect
| What | Why |
|---|---|
| Your email address | To sign you in, to send the link that confirms the address is yours, and to tell you when a vow you sent has been delivered, opened or written back to. |
| Your display name | It is the name your recipient reads above the message. Without it, a vow arrives signed by nobody. |
| Your recipient's name, relationship, email and optionally phone | To address and deliver the vow. You give us this about someone else — see below. |
| The vow itself: your text and any photo, video, voice note or document | It is the thing we are keeping. We do not read it, sell it, or use it to train anything. Each uploaded file is checked automatically, by its digital fingerprint only, against lists of known child sexual abuse images; nobody looks at it. |
| If you use the app: a notification token, and the one contact you pick | The token lets us tell you a vow was delivered or opened; it is deleted when you sign out. When you pick someone from your phone's contacts, the phone hands us only the name and number you tapped — we never read your address book. |
| Where your first visit came from — the campaign tags in the link you followed (such as utm_source=pinterest), the site that sent you, the page you landed on, and a random id your browser keeps. If you arrived by clicking one of our Google ads, also the click id Google adds to that link (gclid, gbraid or wbraid), kept for 90 days, as Google does | So we know which of our posts bring people who actually use LightVow, and can stop making the ones that do not. It is kept in our own database, linked to your account once you sign up, and never shared or sold. |
| If you are the person a message is for and you answer the page that asks where it should reach you: the email and/or phone number you type, and — for a phone number — a record of your consent to texts | To deliver the message there. The consent record holds when you agreed, the exact wording you were shown, the page, your browser type, and scrambled (hashed) forms of the number and your network address — never the address itself. It exists so we can show that you, and not someone else, asked for the texts. |
| Delivery records — when we tried, whether it was accepted, why it failed | So a failure is visible and can be retried, and so we can prove what happened. |
| Your email address, if you ask us to remind you on December 1 (no account needed), with the date you asked and the wording you agreed to | To send a link to confirm it was you, then the one reminder you asked for, and then delete the address. Lawful basis: your consent, which you can withdraw with the link in the email or by writing to us. |
We use PostHog to count visits: which pages are opened, where a visit came from (the campaign tag, the card a link pointed to, and the kind of site that sent it, such as a search engine, a social network or an AI assistant, never its address, and for a visit from one of our Google ads, the click id Google added to the link), which part of a page a button was in, and whether the visit went on to write and seal a vow, make a purchase, or tap through to the App Store or Google Play (which store; a button on our site passes the random id PostHog already keeps for your browser along to that step, so the tap counts with your other visits, and it never goes on to Apple or Google). It also counts which step of writing a visit reached (what goes in it, who it is for, how it reaches them, when it opens, the review), when sealing was stopped and the short reason (an account needed, not enough tokens, a plan, a missing detail or an error), and, on a reply, that one was started and that it was sent. It never receives what you type, never records your screen, and is not loaded at all on the page where a recipient opens a vow. PostHog keeps a small cookie and local-storage entry to tell one visit from the next.
When you sign in or create an account, your earlier visits in the same browser are counted as the same person as your account. If you start in one browser and confirm your email in another, the random id PostHog gave the first browser is stored with your account so those visits are counted as you too. It is an id PostHog made up, not anything about you. Visits by our own team's tests are marked so they are left out of the counts.
Our own server also tells PostHog about the steps that happen there, under your account's random id (never your email address or name): that an account was created and how you signed in (email, Google or Apple); that a vow was sealed, with the card it went out on, the kind of occasion, how many days ahead it opens, how many kinds of address it has and whether it is a group vow; that a purchase was started, completed (the pack or plan, its tokens, amount, currency, whether it was a free trial and whether through Paddle, Apple or Google) or did not go through (a short reason such as "card declined", never card details); and, as part of the sender's own record, that their vow was delivered (by email, text, WhatsApp or the app), opened (and through which of those, the kind of occasion, and whether that browser had been to LightVow before), that the button to write one back was shown or pressed (and which of the offered days was picked), or that a reply to it was started or sent. To join those steps without the vow's id, they carry a one-way scrambled code made from it. Whether an account's first vow was a reply is noted on its sign-up, seals and purchases, and where its first visit came from (as above, including a Google ad click id from the last 90 days) on its sign-up, seals and purchases. Nothing about the person a vow is for is ever sent — no name, email address, phone number or account — and never a word of any vow, card or link.
Advertising (the website only)
On lightvow.com, outside the European Economic Area, the UK and Switzerland, we use the Meta Pixel so we can show our ads to people who visited, and stop showing them to people who already bought. Like any Meta Pixel, it sends Meta the address of the page you are on, the website that sent you there as your browser reports it, your IP address and browser type, and Meta's own cookies (_fbp, and _fbc if you came from a Meta ad). On top of that, it tells Meta: that a page was viewed (with the kind of site that sent you, such as a search engine, a social network, an ad or an AI assistant); that the writing screen was opened (with which of our cards, unless the card is for sympathy, illness, a new baby or a religious holiday such as Hanukkah, Rosh Hashanah, Passover, a bar or bat mitzvah or Easter, in which case Meta is told nothing about that visit; Christmas cards, which most people send whatever they believe, are treated like any other card); that a link to the App Store or Google Play was tapped; that a letter was sealed (the kind of date it opens on, such as a birthday or an anniversary, roughly how far ahead, whether it carries any photo, video or voice, and whether you chose to write one more for later); that you asked to write one more for later; that an account was created; or that a purchase started or completed (with its amount). Meta's cookie links this to your Meta account if you have one, and Meta uses it for its own purposes too, under its own privacy policy. It never receives your letter, who it is for, your name, email address or phone number.
It is never loaded in the LightVow app, in the EEA, the UK, Switzerland or Israel, on the pages where a message is opened or an account is signed into, or when your browser sends a Global Privacy Control signal, which is how to opt out of this "sharing" under US state privacy laws. You can also ask us to stop at hello@lightvow.com, manage ad preferences in your Meta account, or use Your privacy choices at the foot of any page. Apart from this we sell nothing.
The only other cookies and local-storage entries are: the ones that keep you signed in; the PostHog visit counter described above, with a note that the id above was linked; the draft your browser keeps while you write; until you close the tab, the campaign tag of the visit (such as where the link came from), so the page where you write or sign up knows it, and the email address you typed for "Send it to me", so the sign-up form can fill it in; and, on the page that asks where a message should reach someone, a random device id (lv_did). That id, and a scrambled (hashed) form of the network address, are used for one thing only — telling the person who wrote a message apart from the person it is for, so that nobody can sign somebody else up for text messages. We keep them for at most 90 days. Also Meta's _fbp / _fbc cookies, where the pixel runs (see Advertising); a note that you turned ads off under Your privacy choices (lv_ads_off), kept until you turn them on again; and, for 30 days after a letter or an album key was opened in this browser, a note (lv_maybe_minor) so that an account created from it is never reported to Meta, because the person signing up may be a child.
We never see your card details. Payments are handled entirely by Paddle, Apple or Google.
Where it lives
- Text, names, dates and delivery records — a PostgreSQL database hosted by Supabase in Frankfurt, Germany (EU).
- Photos, video, audio and documents — Cloudflare R2, a private bucket. Nothing in it is public; the app hands out short-lived links that expire within the hour.
- Outgoing email — Resend, sending from the EU (Ireland) region.
- Outgoing text messages — the SMS provider for the recipient's country (listed below). It receives the number and the text of that one message.
Who else touches it
Only the services that make the product work: Supabase (database), Cloudflare (media storage), Resend (email), the SMS providers Twilio, TextMe and BulkGate (text messages), Vercel (hosting), PostHog (counting visits and product events), Meta (the advertising pixel on the website, described above), RevenueCat (reconciling purchases), AI providers only when you ask for writing help, a made card or a moving photo, and Paddle, Apple or Google for payments. Each is listed with its job under "Who processes it for us" below, and each gets the minimum it needs. Nobody buys or rents your data. The one case that US state laws call "sharing" is the Meta Pixel, and you can turn it off — see Advertising above.
About the person you are writing to
When you name a recipient you give us their details. You are responsible for having a reason to contact them; we are responsible for using it only to deliver your vow.
A recipient can write to us and ask what we hold about them, ask us to correct it, ask us to stop a delivery, or ask us to erase their details. We will honour that even though it was you who gave us the data — and we will tell you that a delivery was stopped.
Text messages
When a recipient has a phone number on a vow, they get one text message on the day the vow opens, with the link to open it, and — only if the sender asks — a reminder with the same link, at most once a day, while it stays unopened. If they have the LightVow app, the app may tell them first and the text follows a day later only if the vow is still unopened. Nothing else: no marketing, ever, and the number is never shared with anyone for their own use. Message and data rates from their carrier may apply.
In the United States we text only a number the person typed in themselves, on the page that asks where a message should reach them — never a number the sender gave us. We keep a record of that consent (see "What we collect"). Elsewhere, the sender may give us the number, and the texts are the same ones described here.
If you add your own number to your account, we text it a one-time code to confirm it is yours, only when you ask for one.
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Phone numbers and text-message consent are used only to deliver the message someone left you and its reminders (or a one-time code to confirm your own number), by Ravid Zer, trading as LightVow.
Every text carries a way out: reply STOP where replies are possible, or tap the link in the message. Either stops all texts from LightVow to that number, immediately. For anything else, write to hello@lightvow.com.
What deleting actually deletes
- A sealed vow is kept until it is delivered and opened — that may be years, by design.
- The magic link in a delivery email expires after 90 days or ten opens. A recipient with an account can always mint a fresh one; the link's expiry never decides whether a memory still exists.
- Delete a vow and its media are removed from storage and its delivery is cancelled.
- Delete your account and vows you have sealed but that have not yet arrived are still delivered, because each is a promise to someone else. If you would rather they were cancelled, delete them from your vault first, or write to us and we will cancel them together with the account. Vows already delivered stay with the person who received them — once somebody has been told a letter is waiting, it is not only yours to take back.
- Records we are required to keep — payment and tax records, and the minimum needed to prevent fraud — remain for as long as the law says, detached from you where they can be.
Why we are allowed to hold it
Under the UK and EU GDPR every use of personal data needs a lawful basis. Ours, in plain terms:
- To run the service you asked for (performance of a contract) — your account, your vows, storing them, and delivering them on the date you chose.
- To reach your recipient (legitimate interests) — holding their name and contact details for the single purpose of delivering what you addressed to them. We balanced that against their interests and concluded it is what a person would expect of a letter addressed to them; they can object at any time and we stop.
- To take payment and keep records (contract, and legal obligation) — tax and accounting law requires us to keep transaction records for several years even after you leave.
- To keep the service safe (legitimate interests) — rate limits, abuse prevention, and the logs that make a failure visible.
Two things rest on your consent, and you can withdraw either at any time: the December 1 reminder email (the link in the email, or write to us), and texts to a US number you entered yourself (reply STOP). We do not sell personal data, and apart from the Meta Pixel described under Advertising, we do not build profiles of anyone. The one exception to "we share nothing" is the Meta Pixel described under Advertising: under California's CCPA/CPRA and similar state laws that counts as "sharing" for cross-context behavioural advertising. It runs on the website only, never in the app, and never in the EEA, the UK, Switzerland or Israel. You can opt out by turning on Global Privacy Control in your browser — we honour it automatically — or by writing to hello@lightvow.com, and we will stop.
Who processes it for us
We use a small number of providers, each for one job, each under a data processing agreement:
- Supabase — the database and accounts. Hosted in the EU (Frankfurt).
- Cloudflare R2 — the files you upload. Hosted in the EU.
- Vercel — running the website and the delivery worker.
- Resend — sending the emails that carry your vows.
- Paddle — the merchant of record for purchases on this website. Paddle is the controller of your payment details; we never see a card number.
- PostHog (United States) — counting visits and how many go on to seal a vow, and the product events our server reports, as described above. It never receives the contents of a vow or anything about the person a vow is for.
- RevenueCat — reconciling purchases across the web, Apple and Google.
- Twilio (United States), TextMe (Israel) and BulkGate (Europe and Australia) — sending text messages. Each gets the recipient's number and that one message.
- Expo, Apple and Google — carrying notifications to the app on your phone.
- OpenRouter and Google (Gemini, and Veo on Google Cloud Vertex AI), only when you ask for writing help, for a card to be made, or for a photo to be turned into a short moving clip: the words or photo you gave for that request, and nothing else.
Meta Platforms is not our processor: for the Meta Pixel it is a separate business that uses what it receives for its own advertising too. See Advertising.
We will update this list when it changes. If you would like the current version at any time, ask.
How long we keep it
Vague answers here are how retention promises get broken, so these are the actual periods, and they are the ones the software enforces.
- A vow that has been delivered — for good. Not for a stated number of years: for good. It is the recipient’s, whatever plan you were on, whether you later cancelled, and whether or not you are still here. If you delete it yourself before it is delivered, it goes; once somebody has received it, it is not yours alone to withdraw.
- A sealed vow that has not been delivered yet — until its day, however far away that is. That is what you paid for when you chose the date.
- A vow that lapsed — one that was never delivered and now never can be, because nobody ever gave us an address for it. Kept twelve months after it lapses, so it can still be rewritten and sent, then removed. We write to you before that happens and you can download everything in it at any point.
- A draft — until you seal or delete it. We may remove drafts left untouched for a long time, and will warn you first.
- A draft you write before creating an account — only in your own browser, never on our servers, until you sign up or for 30 days.
- Backups — a daily backup kept 90 days and a monthly one kept long-term, so a sealed vow survives a disaster. Deleted data stays in them until they expire and is used for nothing but recovery.
- The device id and hashed network addresses used to tell a sender from a recipient — 90 days from when we last saw them.
- A record of consent to texts — for as long as we may need to show that consent was given. It holds only hashes, never the number or address itself.
- Your account — until you delete it.
- Payment records — as long as tax law requires, typically seven years, even after your account is gone.
- Delivery logs — twelve months, so a failure can be explained.
- A reminder request — until the reminder is sent or you unsubscribe, whichever comes first. If you unsubscribe we keep only a one-way hash of the address, so we never write it down again.
Your rights
You can ask us for a copy of everything we hold about you, ask us to correct it, ask us to erase it, or object to how we use it. One email to hello@lightvow.com is enough, and we answer within 30 days.
If you are in the EU or UK and you think we have handled your data badly, you can complain to your national data protection authority. We would rather you told us first.
Keeping it safe
- Everything travels over TLS and is encrypted at rest.
- Delivery links are stored only as a hash — the link itself exists in your recipient's email and nowhere else, so even we cannot reconstruct it from the database.
- Row-level security means one account cannot read another's vows, and a sealed vow cannot be altered by anyone through the app.
- The claim page is rate-limited and returns identical errors for wrong, expired and used links, so it cannot be probed to discover live ones.
Children
A vow addressed to a child is exactly what this product is for. But you must be 18 or older to create an account yourself. The same goes for asking us for a reminder email.
International transfers
Data is stored in the EU. Where a provider processes it elsewhere, that transfer is covered by Standard Contractual Clauses or an equivalent safeguard.
Complaining about us
If you think we have handled your data badly, please tell us first — hello@lightvow.com — because most of it we can simply fix.
You also have the right to complain to a supervisory authority without going through us. In the EU that is the data protection authority of the country you live in; in the UK it is the Information Commissioner's Office; in Israel it is the Privacy Protection Authority. You do not need our permission and we will not hold it against you.
Changes
If we change this policy in a way that matters, we will tell you before it takes effect rather than quietly updating the date.
