Your data, in plain words.

• Your mobile number, to sign you in with a one-time code and send booking and match updates.
• Your name and profile: the name, home city, skill level and bio you choose to add.
• Bookings and payments: which courts you booked, when, and the payment reference. Card, UPI and bank details are handled by Razorpay; we never see or store them.
• Matches and stats: matches you join or host, results confirmed by the other team, and the numbers worked out from them.
• A friend's number on a match: a match host can type a friend's name and mobile number, so that friend can claim their stats when they log in. We don't message that number or make an account from it. If you find a match added to your number by mistake, choose "Not me" and your number comes off it.
• Quick matches: the team names, player names and score a host types, kept only so others can watch.
• Reviews you write about turfs.
• Technical data such as your browser and IP address, kept in server logs to keep the service secure.

If you tap Near me, your browser asks before sharing your location. It is used on your device only, to sort turfs by distance, and is not sent to us.

• To create your account, take bookings and payments, and give you an entry pass.
• To run Play Together: squads, join requests, cost shares and scorecards.
• To send you sign-in codes and updates about your bookings and matches.
• To prevent fraud and abuse, and to meet tax and legal obligations.

• The venue you book sees your name, mobile number and booking, to let you in and contact you about it.
• Other players see your name or first name and initial, your public stats and your reviews. Your mobile number is never shown to them in full.
• Service providers who work for us: Razorpay for payments, Meta (WhatsApp) for sign-in codes and messages, our cloud hosting and database providers, and Google (Gemini) for the wording of your cricket reports, only if you turn AI-written reports on.
• Authorities, when the law requires it.

Your cricket reports are worked out by our own server from your confirmed matches. AI-written reports are off until you turn them on. When they are on, we send Google's Gemini service the findings only: what each one is about (such as "death overs" or "against spin"), its numbers and how sure it is, and the place and ball type. We never send your name, phone number, email, account or match ids, team, player or venue names, or photos.

Gemini only puts the findings into words. Our server checks every sentence against your numbers, and uses its own wording for any sentence that fails. We keep the last three versions of each report, and a record of each AI call (its size and cost) for 180 days. We don't keep Gemini's raw replies. You can turn AI-written reports off at any time, which removes the AI wording from your reports, and everything goes when your account is deleted.

We keep your account data while your account is open. Booking and payment records are kept for as long as tax law requires (usually 8 years). When your account is deleted at your request, your profile is removed and your name is taken off past match records. A friend's number typed on a match is removed when they claim it or say it isn't them, or after 90 days. A quick match leaves the app 30 minutes after it ends, or after 6 hours with no new score, and is gone from our server's files within a day.

• See the personal data we hold about you, and correct it.
• Ask us to delete your account and data (write to the grievance officer below), apart from records the law makes us keep.
• Withdraw consent for optional messages at any time.
• Nominate someone to act on your behalf, and complain to our grievance officer or the Data Protection Board of India.

Players under 18 need a parent or guardian to create the account and make bookings for them.

Grievance Officer, One Turf, One Turf Sports Technologies Pvt. Ltd., Anna Salai, Guindy, Chennai, Tamil Nadu 600032. Email grievance@oneturf.in. We reply within 30 days. If we change this policy in a way that matters, we will tell you in the app before it applies.