SplitThat Privacy Policy
Effective date: August 8, 2026
This policy describes how Inyeon LLC, a New York limited liability company ("Inyeon," "we," "us"), handles personal information in the SplitThat mobile app and its supporting service (together, the "App").
SplitThat is a consumer app, operated in the United States. This policy is separate from, and does not incorporate, the Inyeon business platform's privacy policy — that document covers a different, business-only service.
Contact for anything in this policy: team@inyeon.dev
1. The short version
- We collect what the App needs to split a bill: your account details, the expenses you create, and the receipts you upload.
- Receipt images and PDFs are sent to a third-party AI provider to read the line items off them. This is the core of the scan feature and is described in Section 4.
- Receipts are encrypted at rest and are readable only by people on that expense.
- We do not sell personal information, run advertising, use third-party analytics SDKs, or track you across other apps and websites.
- We do not read your device's contact list, your location, or your microphone.
- You can delete your account from inside the App, and we describe exactly what survives and why in Section 9.
2. Information you give us
Account. Depending on how you sign in, some combination of: phone number, email address, a password (stored only as a bcrypt hash — we never hold the password itself), display name, username, and avatar image.
Sign in with Google or Apple. If you use these, we receive the provider's stable identifier for you (the "subject"), and the email address and display name the provider releases. We verify the sign-in token against Google's or Apple's public keys; we do not send those providers any information about your expenses.
Phone verification. When you sign in by phone, we generate a one-time code, store only an HMAC hash of it, and hand your number and the code to our SMS provider (Telnyx) for delivery. Codes expire and are limited in both send rate and attempts.
Payment handles. If you choose to add them, your Zelle, Cash App, or Venmo handle. These are handles only. SplitThat never asks for and never stores card numbers, bank credentials, or account numbers.
Purchases. If you subscribe to Pro, we receive the App Store receipt or the Google Play purchase token and the product identifier, and we send them to Apple or Google to verify the purchase and unlock the plan. Payment card details go to Apple or Google, never to us — we never see or store them.
Preferences. Locale and default currency.
3. Information the App creates as you use it
- Expenses: titles, dates, line items, quantities, amounts, tax lines, tip, who paid, and how each item was split.
- Groups and trips: names, settings, membership, and roles.
- Invites: the phone number or username you type when inviting someone. We use it to connect that invite to their account, and to show them the pending invite.
- Balances and settlements: who owes whom, and each person's confirmation that a settlement happened.
- Notifications generated for you, and the Expo push token for your device if you enable push.
- Audit records of changes made to an expense after it was confirmed, so the people affected can see what changed.
- Product events: an internal, first-party record of things like "a scan happened," with an event name, an optional user id, a number, and a small set of properties. These are aggregated to understand whether features work. They are not shared, not sold, and not joined to advertising of any kind.
Server logs. Our API logs a request id, method, path, status code, duration, and the requesting IP address. IP is used for rate limiting and abuse prevention.
4. Receipts, and the AI that reads them
When you scan a receipt, the image (or the pages of the PDF, rasterized) is transmitted to OpenRouter, which routes it to a third-party vision model that extracts the merchant, line items, quantities, prices, tax, and tip. The extracted text comes back to us and becomes the editable expense you see.
Things worth knowing:
- Whatever is visible in the photo is sent. If a receipt shows the last four digits of your card, a name, or a phone number, that is in the image we transmit. Crop or retake the photo if you would rather it were not.
- We send the image for extraction only. We do not send your account details, your contacts, or your other expenses.
- Model providers reachable through OpenRouter have their own retention and training practices, which we do not control. We select providers and routing settings, and we do not authorize use of your receipts to train models; we cannot make an absolute guarantee about a third party's internal handling.
- If the AI service is unavailable, the App falls back to a manual entry flow. You can always create an expense without scanning anything.
Storage. Receipt files are stored encrypted at rest using AES-GCM with a per-file nonce. A request for a receipt from someone who is not a participant on that expense returns "not found" — we do not confirm that someone else's receipt exists.
5. Device permissions
| Permission | Why |
|---|---|
| Camera | To photograph a receipt. |
| Photo library | To choose an existing receipt photo. |
| Notifications | To tell you about invites, confirmations, and settlements. |
The App does not request access to your contact list, location, calendar, health data, or microphone.
6. What other people can see
Splitting a bill is inherently shared. People in a group or trip with you can see:
- Your display name, username, and avatar.
- The expenses, line items, and amounts you share with them, and what each person owes.
- Any payment handle you have chosen to add, so they can pay you.
They cannot see your email address or phone number. The API deliberately omits contact details from other people's profiles.
If you leave a group, you keep read access to your own history within it, but you stop receiving new activity.
7. Who we share information with
We do not sell personal information and we do not share it for advertising. We use a small number of service providers, each for one job:
- OpenRouter and the model providers it routes to — reading receipts (Section 4).
- Expo — delivering push notifications to your device.
- Google and Apple — verifying sign-in, if you use those buttons, and verifying a Pro purchase.
- Telnyx — delivering phone verification codes.
- Our hosting provider — running the servers and database.
We also disclose information when the law requires it, to protect our rights or someone's safety, or in connection with a merger or sale of the business, in which case this policy continues to apply until you are given notice of a new one.
8. How long we keep things
We keep your account and its data while your account is open. Verification codes expire in minutes. Server logs are kept for a short operational window. Expense records persist because they are also other people's records of a shared debt.
9. Deleting your account
Delete your account from Settings → Account → Delete account in the App, or email team@inyeon.dev from the address on the account.
What is erased: your phone number, email address, password, display name, username, avatar, and saved payment handles. Your push tokens, notifications, and any linked Google or Apple identity are deleted outright, and the account can no longer be signed into.
What survives, and why: expenses, line items, balances, and settlements you shared with other people remain, with your name replaced by "Deleted user." These are the other participants' financial records too, and cascading a delete through them would rewrite what they are owed. Nothing left behind identifies you.
Receipts. Receipt images attached to an expense that you shared with other people remain available to the other participants of that expense, for the same reason. If you want a specific receipt removed, email us and we will remove it.
10. Your choices and rights
- Access. Export your expenses as CSV from inside the App.
- Correction. Edit your profile and your expenses in the App.
- Deletion. Section 9.
- Push. Turn notifications off in your device settings at any time.
Depending on where you live, you may have additional rights — to know what we hold, to request deletion, to correct information, or to appeal a refusal. Email team@inyeon.dev and we will respond as the applicable law requires. We will not discriminate against you for exercising a right.
We do not sell or share personal information as those terms are defined under California law, and we do not process it for targeted advertising.
11. Security
Traffic to our API is encrypted with TLS. Passwords are hashed with bcrypt. One-time codes are stored as HMAC hashes. Receipt files are encrypted at rest. Every read of an expense, receipt, or balance is checked against your membership on the container it belongs to. No system is perfectly secure, but we design for the case where something leaks.
12. Children
SplitThat is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has created an account, email team@inyeon.dev and we will delete it.
13. Changes
If we change this policy we will update the effective date above, and for material changes we will notify you in the App before the change takes effect.
14. Contact
Inyeon LLC — team@inyeon.dev