Privacy Policy
Last updated 8 August 2026
What we collect, what we deliberately don't, who can see it, and how to get it back or have it deleted.
1.What we collect
- Identity: your name, email address, and — if you sign in that way — your phone number, from Google or Firebase phone sign-in.
- Profile: username, college, institute email, gender, date of birth, photo, and bio, as you provide them.
- Location: live position while you have a group ride open and sharing switched on; a coarse home location if you set one; pickup and destination points for trips you create.
- Usage: rides and group rides you create or join, messages you send, and notifications generated for you.
- Referrals: if you arrived through an invite link, the id of the person who invited you and the date you joined. It is recorded once and never rewritten.
- Payments: none today — the service is free during the beta, so no payment records are created. If a fee is introduced we will hold the Razorpay order and payment identifiers and their status. Card numbers, UPI IDs and bank details are entered on Razorpay and never reach our servers.
- Technical: IP address and user agent, in server logs and rate-limiting counters.
2.What we do not collect
- We do not use advertising cookies or cross-site trackers.
- We do not sell personal data to anyone, for any purpose.
- We do not store your password when you sign in with Google or phone — there is no password on those accounts. Where a password exists, it is stored only as a bcrypt hash and cannot be read back.
- We do not read your device contacts, camera roll, or messages.
- Analytics is not switched on. The Firebase analytics SDK is deliberately not initialised.
3.How your phone number is stored
Your phone number is stored twice and for different reasons: once in readable form so it can be shown to you and to people you are actively travelling with, and once as a salted one-way hash used to detect duplicate accounts. The hash cannot be reversed into a number.
4.Who can see what
- Your name, username, photo, college and rating are visible to other Spllit users.
- Your email address, phone number and institute email are not shown on your public profile.
- Live location is visible only to members of the group ride you are sharing with, and only while you are sharing.
- Messages are visible to the people in that conversation. We do not read them except where we must to investigate a report or comply with the law.
5.Cookies and local storage
Strictly necessary storage keeps you signed in. It is not optional — without it the app cannot tell who you are — and it is exempt from consent under ePrivacy rules.
Everything else is asked for: remembering dismissed banners and your invite link (preferences), and usage measurement (analytics, currently unused). You can accept, reject, or choose per category, and change your mind by clearing site data.
6.Third parties we share with
- Google Firebase — authentication (Google sign-in, phone OTP) and push tokens.
- MongoDB Atlas — the database where your account and activity are stored.
- Mapbox — geocoding, map tiles and directions. Coordinates are sent to compute a route or resolve a place name.
- Razorpay — payment processing. Integrated but not active during the free beta, so nothing is sent to them today. If a fee is introduced you would enter payment details on Razorpay, not on Spllit, and we would receive only an order id, a payment id and a success or failure.
- Cloudflare, Vercel and Google Cloud — hosting and delivery.
- We share what those services need to do their job, and nothing more. None of them is permitted to use your data for their own purposes.
- Some of these providers process data outside India. Where that happens, it is done under the provider’s contractual data-protection terms.
7.Why we are allowed to hold it
- Most of what we hold is processed because you asked us to provide the service — an account, a group ride, a message you chose to send.
- Location sharing, optional cookies and notifications run on your consent, which you give explicitly and can withdraw at any time.
- Payment records and security logs are kept because we have a legal obligation to, and a legitimate interest in preventing fraud and abuse.
8.How long we keep it
- Account and profile data: while your account exists, then deleted on request.
- Live positions: short-lived, cleared when you stop sharing or leave a group ride.
- Messages: for as long as the conversation exists. A message you sent stays in the recipient’s copy — it is their record too, and we cannot remove it from their history without deleting theirs.
- Payment records: retained for eight years, as required of financial records under Indian tax and company law. These survive account deletion.
- Server and security logs: a limited period for debugging and abuse investigation.
9.Children
Spllit is for students aged 18 and over. We do not knowingly collect data from anyone under 18. If you believe a child has an account, write to us and we will remove it.
10.Your rights
Under India’s Digital Personal Data Protection Act 2023 — and under GDPR if you are in the EU/UK — you can ask for a copy of your data, ask us to correct it, ask us to delete it, withdraw a consent you previously gave, or nominate someone to exercise these rights if you cannot. Write to the address below and we will respond within 30 days.
If you are not satisfied with our response you may complain to the Data Protection Board of India.
11.Grievance Officer
For complaints about how your data is handled, under the Information Technology Act 2000 and the DPDP Act 2023:
Saurav Kumar — [email protected]. Acknowledged within 24 hours, resolved within 15 days.
12.Security
- Passwords, where they exist, are hashed with bcrypt. They are never stored or logged in readable form.
- Sign-in endpoints are rate limited, and repeated failed attempts against one account trigger a temporary lockout.
- Sign-in failures return the same message whether the account exists or not, so the response cannot be used to discover who has an account.
- Traffic is served over HTTPS. No system is perfectly secure, and we will tell affected users promptly if a breach puts their data at risk.
13.Contact
Questions, or a request about your data: [email protected]
This document describes how Spllit actually works today rather than reserving rights over features that do not exist. It has not been reviewed by a lawyer, and should be before Spllit takes payment or opens beyond a pilot.