Legal
Last updated 19 November 2026
VowBox builds digital wedding invitations for Indian couples, and VowBox Hisaab, a shared place to track what a wedding costs and who owes whom. This page explains, in plain language, what information we collect, why, and how long we keep it. It reflects what VowBox actually does today — not a generic template. Unless a section says “VowBox Hisaab”, it is about wedding invitations.
From the couple building an invite: names, an optional opening message, event details (event names, dates, times, and venue addresses), the email address you give when you pay (where we send your payment confirmation and your dashboard link), and — if you turn RSVP on — up to two email addresses where we send your RSVP notifications.
From a wedding guest submitting an RSVP: their name, mobile number, number of guests, and which events they’re attending.
We never ask anyone to upload a personal photo. Every invite uses pre-selected template imagery — no guest or couple photo ever passes through our systems.
Wedding invitations have no accounts and no login — access to your invite is a private link, not a profile — and they use no cookies. VowBox Hisaab does have sign-in and uses the cookies described below, which exist only to keep you signed in and to remember your unsaved wedding. Across all of VowBox, we don’t run third-party advertising or analytics trackers, and we don’t sell or share your data with anyone for marketing.
To understand how many people visit VowBox and whether our ads are working, we keep simple aggregate counts: how many times our home page is viewed, which steps of the invite builder people reach, and which website or marketing campaign referred a visit (for example, an Instagram ad). On the VowBox home page and the VowBox Hisaab home page we also count which links and which questions people use, each recorded as a label from a fixed list (for example “the Explore Hisaab button”) together with the campaign that referred the visit. These counts are kept without cookies, without any third-party analytics service, and without your IP address, your device details, or anything else that identifies you. They’re counts, not profiles. All of this stays in our own database (Supabase, listed below) — no analytics company is involved.
If you start building an invite after clicking one of our ads, we store the name of that campaign alongside your invite so we know which ads lead to real bookings. It is never linked to anything that identifies you as a person.
One small technical note, not a cookie: while you’re building your invite, your browser briefly remembers which steps it has already told us you’ve reached — so refreshing the page doesn’t get counted twice. This lives only in that browser tab, disappears the moment you close it, and is never sent to us or saved anywhere on our end.
Couple details are used to build and display your invite. The email address you give at payment is used to send your payment confirmation and dashboard link, and to contact you about your invite if we ever need to. Guest RSVP details are used for exactly one purpose: letting you know who’s coming, by emailing your RSVP notification address(es) each time a guest responds.
If you don’t finish building your invite, we don’t keep the draft indefinitely — an inactive draft is automatically and permanently deleted, typically within about an hour of you stepping away.
Once your invite is live, it — and every guest RSVP submitted to it — stays until 30 days after your last event, then it’s permanently deleted. There is no archival or “keepsake” copy kept anywhere after that.
The aggregate visit and invite-builder counts described above are kept indefinitely — since they hold no cookies, IP address, or anything else that identifies you, there’s nothing tied to you to expire. We may introduce an automatic deletion schedule for this data in the future.
We use a small number of service providers to run VowBox, each only able to access what they need to do their job: Supabase (database and file storage), Vercel (hosting; every request to VowBox passes through it), Resend (delivering RSVP notification, payment confirmation and VowBox Hisaab emails), Razorpay (processing your payment; VowBox never sees or stores your card details), and Cloudflare (a bot check, Turnstile, on VowBox Hisaab’s start and sign-in forms; Cloudflare sees your browser and network details to tell people from bots), and OpenAI (answers the questions asked in Ask AI on VowBox Hisaab, as described under “VowBox Hisaab: Ask AI” below). We use them only to run VowBox: we do not sell your data, and we do not give it to any of them for advertising. Each handles it under its own terms, and some keep limited security logs for a short time. Some of these providers, including OpenAI, may process data outside India.
To stop abuse, our servers keep short-lived counters that include your IP address, for example how many drafts or sign-in codes one address asked for in an hour. They are deleted automatically within two days, and are not used for anything else.
Anyone with your invite’s link can view it and RSVP — the same way a physical invitation works. Don’t share your configurator draft link with anyone you wouldn’t hand a house key to; it’s meant only for you and your co-planner while building.
VowBox Hisaab keeps a private record of one wedding’s spending. A “wedding” there holds what you and the people you add enter: the wedding’s name, date, currency and budgets; vendor and expense names, prices, due dates, payments, notes and the links you paste (we store the link, never the file); how each cost is split; settle-ups; the names and, if you give them, email addresses of the people on it; and a history of who changed what. Everyone on a wedding can see all of it, including prices and everyone’s payments.
When you save a wedding we also keep your email address, which is how you sign in. When you pay the one-time fee, we keep the payment reference and amount Razorpay gives us, never your card details. The questions you ask in Ask AI, and its answers, are kept for 30 days as described below; they are not shown to the other people on the wedding.
There are no passwords. You enter your email, we email you a 6-digit code that works for 10 minutes and only once, and you type it in. We keep only a scrambled form of the code, never the code itself, and remove used and expired codes within a day. After that, one cookie keeps you signed in for up to 30 days; it is strictly necessary, can’t be read by scripts on the page, and is deleted when you sign out. While you sign in, your browser tab also remembers the email you typed so the next screen can show it; that lives only in the tab and goes when you close it.
Before you save, a wedding you started lives as an unsaved draft tied to a second necessary cookie on your device (up to 30 days). It is how we find your draft again; it holds no personal details. There are no advertising or analytics cookies.
Like the invite builder, VowBox Hisaab counts which screens and buttons people use, so we can find where people get stuck. Each count records only what happened (for example “the Start screen was opened” or “a payment was recorded”), whether the device was a phone or a computer, and the campaign or website that referred the visit. It never includes your name, email address, amounts, anything you type, or your IP address, and it uses no cookies and no outside analytics company. A wedding’s counts are joined by a coded label that can’t be read back into the wedding without a secret key only we hold. These counts are kept indefinitely, because they hold no names, emails, amounts or anything you type.
Anyone on a wedding can use Ask AI, an assistant that answers questions about that wedding’s figures and can prepare a draft expense from a sentence you type. It never changes anything by itself: a draft is saved only when you press “Add it”, and the figures in an answer come from the wedding’s own records, not from the assistant’s own arithmetic.
To answer, we send OpenAI, our AI provider, the question you type, up to six earlier messages from that chat, and the figures it needs to look up on that wedding: vendor and expense names, amounts, dates, categories and who paid or owes. Every person on the wedding appears to OpenAI as “You”, “Person A”, “Person B” and so on, never by name, and email addresses and long numbers you type are masked before they are sent. Amounts and vendor and expense names are sent as they are, because the answer needs them. Under OpenAI’s published terms for its API, it does not use what we send to train its models, and it may keep requests for up to 30 days to watch for misuse.
We keep a log of each question and answer for 30 days, then delete it. In that stored copy, names, email addresses, phone numbers and amounts are masked. We use the log to check that Ask AI answers correctly and to fix problems, and we do not use it to train a model.
The owner of a wedding can add people by name and, optionally, by email address. If the owner adds your email address, we send you an email telling you who added you and to which wedding, and what you could do on it. The owner can send it again. Nothing happens until you sign in with that address and accept; you can decline instead. We use your address only to deliver that invitation and your sign-in codes. It is deleted if you decline, if you ignore the invitation for 30 days, or if you are later removed from the wedding. If you don’t know the person who added you, ignore the email or write to us at the address below. We send any one address at most a few invitation emails a day, whoever asks. The wedding’s history shows that you declined. If you also choose “Decline and block”, we remember the block against the sender’s account, not your email address, so their later invitations never reach you. They are not told about the block. You can remove it yourself, any time, from “Blocked senders” on your weddings page.
If you accept, your name is shown to everyone on that wedding, and so is the optional full name if you add one to your profile. If you are removed or you leave, your email address is deleted straight away, but your name stays on past entries so the wedding’s figures still add up. Ask us and, within 30 days, we will replace your name on past entries with “Former member” in the list of people and in the history; the amounts stay. If someone typed your name into a note, we can’t change that automatically. Tell us where it is and we’ll look at it. If you are still on the wedding, leave it first, then ask.
The owner decides what to enter about other people and is responsible for having the right to share it. When an owner schedules a wedding for deletion, or cancels that, we email everyone else on it whose email address we hold.
A draft you never save is deleted after 7 days without activity. A saved wedding is kept until its owner deletes it: deletion takes effect 7 days after the owner asks (everyone else is emailed, and the owner can cancel), then the wedding and everything in it is permanently deleted for everyone, including the history. If nobody opens a saved wedding for 12 months (anyone on it signing in and opening it counts), we email its owner a warning, and if nobody opens it in the 30 days after that, we delete it. About two days before a wedding’s free week ends, we email its owner one reminder. If the free week ends unpaid, the wedding stays available to view, download and delete, and is not deleted for that reason. We keep payment references for as long as the law and our own accounts require. Ask AI questions and answers are deleted 30 days after they were asked.
You can ask us for a copy of the personal data we hold about you, ask us to correct it, ask us to erase it, and name someone to exercise these rights for you if you die or cannot. You can also withdraw your consent to anything you agreed to, for example by leaving a wedding or asking us to delete it. If you are unhappy with how we handled a request, tell us first at the address below; if we have not resolved it, you can complain to the Data Protection Board of India. VowBox is not meant for anyone under 18.
To ask what we hold about you, or to have it deleted early, write to hello@thevowbox.com. We respond to every request within 30 days.
VowBox is operated as a sole proprietorship, and is responsible for the personal data described on this page.