Privacy policy

• Account details: your name, email address and, if you sign in with Google, the profile photo Google gives us. Passwords are handled by Clerk, our sign-in provider, and kept only as a one-way hash that can never be read back.
• Profile details you choose to add: phone number, UPI ID, preferred currency and language.
• Group data: groups you create or join, expenses, who paid, how each expense was split, settlements and notes.
• Receipts: images you upload, the structured data extracted from them, and any corrections you make.
• Operational records: an audit log of actions that move money or change access, containing your user id, the action, a timestamp, a hashed IP address and your browser user-agent.

We do not ask for and do not store your UPI PIN, card number, CVV, card expiry, OTP, net-banking password or any other payment credential. There is no screen in this product that asks for them. If anything claiming to be Splitly asks you for one, it is not us.

A UPI ID (like name@bank) is a public address, comparable to an email address. Storing one lets people in your groups pay you back. It cannot be used to take money from your account.

• Expenses, balances and receipts are visible only to members of that group. Access is checked on the server for every single request.
• Your email address and UPI ID are shown to people in your groups masked, like ary*****@***.com. Your full UPI ID goes only to someone settling a balance with you, because their UPI app needs it to pay you.
• Invite links reveal only the group name, the host's name and the dates before they are accepted. Never the expenses.
• We do not sell your data, and we do not share it with advertisers.

Sign-in, email verification codes and password resets are run by Clerk. Clerk processes your email address, your password hash and the device and network details it uses to spot suspicious sign-ins. An account is only connected to groups you were added to by email once Clerk has confirmed the address is yours.

When you scan a receipt, the image is sent to a third-party vision model provider to be read. That provider processes the image to return structured text. Receipt images may contain your name, a merchant address or a partial card number printed by the merchant, so consider what is on a bill before uploading it.

Stored receipts are private. They are never publicly readable and are served only through links that expire after a few minutes.

Clerk, our sign-in provider, sets the cookies that keep you signed in. Groups you start as a guest use a signed, HTTP-only cookie scoped to this site. We do not use advertising or cross-site tracking cookies.

Your browser also stores unsent expense drafts locally on your device so a dropped connection does not lose what you typed. That data never leaves your device until you save the expense.

We record which features are used, for example that an expense was created with a particular split method. Analytics events deliberately exclude amounts, merchant names, email addresses and phone numbers, and user identifiers are hashed before they leave the server.

• Group and expense data is kept while the group exists.
• Deleting a group removes its expenses, receipts and settlements.
• Deleting your account removes your profile, login and notifications. Expenses you paid for remain in other people's groups with your name replaced, because removing them would silently change what your friends owe each other.
• Audit log entries are retained for security and dispute handling.

You can export any group as CSV or JSON at any time, correct your profile from the profile page, and delete your account from settings. For anything else, write to privacy@splitly.example.

Rights under the Digital Personal Data Protection Act 2023, including grievance redressal and the appointment of a data protection officer where required, need to be confirmed with legal counsel before launch.