How we handle your data.

Yuvo is operated by the team behind Yuvo. References in this policy to “we”, “us”, or “our” mean Yuvo. References to “you” mean the venue owner or administrator using Yuvo to run their venue.

Yuvo does not directly serve consumers (captains booking a slot). Captains interact with the venue’s own booking page, and the venue is the data controller for any captain personal data Yuvo stores on the venue’s behalf.

From venue owners (you): name, email, phone, GSTIN, business address, the venue details you enter (name, address, pitches, pricing), and the staff or co-owners you invite. We store this in Supabase (project godnsvqthnncjgeqwlti) on managed Postgres. Yuvo runs a single Supabase project in one fixed region — there is no per-customer choice of region, and we will say so here if that ever changes.

From your captains and customers: name, phone (we normalize to E.164 at the database boundary), booking history, payment records, and any messages you send through Yuvo’s WhatsApp tooling. Captains are stored under your ground_id and never read by Yuvo staff in normal operation.

From your website visitors: the enquiry form on this site captures name, phone or email, and a message. The public pages also load Vercel Web Analytics, which counts page views without cookies and without building a profile of you. We run no advertising or cross-site tracking pixels.

• We do not read or store payment card details. Payments run through your own Razorpay account (or UPI / QR); Yuvo sees only the payment id and status.
• We do not log captain WhatsApp message content. Yuvo composes the draft in your browser and hands it to your own WhatsApp client (a wa.me deep link); we never hold the message after that handoff, and Yuvo has no WhatsApp sending channel of its own.
• We do not sell or rent personal data to anyone, ever. The list of captains is yours, not ours.

• To provide the service — to surface bookings, follow-ups, invoices, and tournaments to you and your staff.
• To enforce tenancy — every row is scoped to your ground_id by row-level security, so you cannot see another venue’s data and they cannot see yours.
• To comply with Indian tax law — invoices, GST, and TDS records are kept for the statutory period (currently 8 years for GST).

• Supabase (database, auth, and the sign-in emails auth sends), Vercel (hosting, plus the page analytics described above), Cloudflare (DNS + edge). Each acts as a data processor under a written agreement.
• If you are on a paid plan, a Razorpay invoice for your subscription may reference your business name and GSTIN.
• Enquiries you send from this site are stored in our own database. If you email support, the message sits in our email inbox, readable by the Yuvo team.
• We do not share data with law enforcement unless we receive a valid, court-ordered request. We will tell you if we receive one for your data, unless the order itself prohibits it.

Active data stays in your tenant as long as your account is open. On cancellation, we retain your tenant data for 90 days in case you change your mind, then delete it. Tax records (invoices, TDS) are retained for the statutory period even after cancellation.

Enquiry form submissions stay in our database until you ask for them to be removed; we use them only to respond to your inquiry, not for marketing.

• Export. Email privacy@getyuvo.com and we send your bookings, customers, captains, and invoices as a ZIP of CSVs within 48 hours. There is no self-serve export screen yet; when there is, this line will change.
• Delete. Email privacy@getyuvo.com to close your account. We confirm with you first, then delete your tenant data within 90 days, except for tax records we are required to keep. Take your export before you ask.
• Correct. Edit anything from the relevant screen in the app. There is no field you can see that you cannot change.
• Ask us anything. Email privacy@getyuvo.com and we respond within 30 days.

• HTTPS everywhere. The session cookie is set Secure in production, so it never travels over plain HTTP. It is deliberately not HttpOnly, because the browser client has to read it to keep you signed in.
• Database access is gated by Postgres row-level security on every table — no code path reads across tenants.
• Service-role access is reserved for the admin console and is itself gated by an ADMIN_EMAILS allowlist.
• Responsible disclosure goes to security@getyuvo.com, listed on /contact. We acknowledge within 48 hours.

If we change anything material — a new data category, a new processor, a new retention period — we email every active venue owner at least 14 days before the change takes effect. The “updated” date at the top of this page moves when that happens.