Last updated 4 October 2026
SplitCheck helps groups of people split shared expenses. This policy explains what we collect, why, and who else sees it. We've tried to write it in plain language rather than legalese.
SplitCheck is operated by Part2AI, Inc. ("we", "us"). If you use the app or the website at splitcheck.me, this policy applies to you.
The short version: we store the expenses and groups you create, plus a name and (if you signed up with one) an email. We don't sell your data or show ads inside the app. We advertise SplitCheck elsewhere and use Meta's SDK in the iOS app to measure those ads. Receipt images go to Anthropic; voice recordings go through our server to OpenAI for transcription, then the text goes to Anthropic to parse the expense. We do not store the receipt images, and our transcription function does not store the audio.
When you create an account we store your email address, a display name, and your preferred default currency. If you join a group through an invite link without signing up, we create an anonymous account for you — that account has an ID and a display name, but no email address.
If you connect SplitCheck to ChatGPT, you authorize the connection to create groups and expenses and to read your accessible groups, member display names and balances. Requested group names, currencies, member display names and references, accessible invite links, and balances are returned to ChatGPT. Expense dates, amounts, allocations and notes you confirm are saved to SplitCheck and visible to your group members. The connection does not send receipt images to SplitCheck. Currency lookups send only currency codes to public exchange-rate services. The MCP service does not persist access tokens or conversation history. ChatGPT processes your conversation under OpenAI's policies. You can disconnect SplitCheck in ChatGPT's connection settings; doing so does not delete previously saved groups or expenses.
We store what you put into the app in order to make it work:
When you scan a receipt, the image is compressed on your device and sent to our server, which passes it to Anthropic's AI service to read the text and extract the amounts. The same happens with expenses you type or dictate.
Along with the image or text, we send the names and IDs of the people in that group, the group's currency, and the date, so the AI can work out who was involved.
We do not store the receipt image. Once the amounts have been extracted, only the resulting expense data is saved. The image itself is not written to our database or file storage. Your device may keep a temporary copy in its cache until the operating system clears it, and if you picked the photo from your camera roll it of course stays in your camera roll.
Anthropic processes this data under its own terms. See Anthropic's privacy policy for how they handle it.
If you dictate an expense, the app records audio with your microphone permission and uploads it to our server. Our transcription function sends the audio to OpenAI to turn it into text and does not store the audio. The resulting text then goes through the same Anthropic expense-parsing step as expenses you type. Only the resulting expense data is saved in SplitCheck. These providers process the audio and text under their own terms; their privacy policies are linked below.
If you choose to invite someone from your contacts, the app asks your permission and then reads your contacts on your device so you can pick a person. We do not upload your contact list. If you invite someone by email, we store that email address so we can match the invitation when they join. If you invite someone by text message, the phone number is handed to your phone's Messages app and never reaches us.
If you turn on notifications, we store a push token so we can send them. Your notification preferences are kept on your device only.
We record that an AI scan or entry happened, along with the date and whether it was an image or text, so we can apply the free tier limits. We do not store what was scanned or entered as part of this record.
If you subscribe, the purchase is handled by Apple for App Store purchases or Google Play for Android purchases, and by RevenueCat, our subscription provider. We store your subscription status and expiry so the app knows you're a subscriber. RevenueCat receives your SplitCheck account ID. We never see or store your payment card details — those go directly to the store you purchase from.
The iOS app includes the Meta (Facebook) SDK. It sends app install and activation events, purchase, trial and subscription events, account registration, and a one-time "first expense added" event for accounts created on or after 1 October 2026. These events include app and device information for ad measurement. The web app does not include this SDK.
Meta measurement is iOS-only. It is disabled in the Android app, and Android and web do not send Meta app events.
The advertising identifier is collected only if you allow tracking in the iPhone permission prompt. If you decline, app events are still sent to Meta without that identifier.
When enabled, we use PostHog to understand how people start using SplitCheck and which features help them. This covers the iPhone and Android apps and the web app, including browser guests. PostHog is configured to use its US Cloud, hosted in the United States.
We record specific actions: signing up or in, finishing or skipping onboarding, creating a group, sharing or sending an invite, joining as a guest, adding an expense, recording a settlement, opening the paywall, starting or completing a purchase, purchase failures, restoring purchases and reaching a scan limit. We also record fixed screen labels, such as “welcome” or “join,” without page addresses or link parameters. Events include their time and platform. Depending on the action, they can include the entry or invite method, monthly or annual plan, currency code, counts or a simple outcome such as a canceled purchase. They do not include amounts, expense notes, receipt content, group names, contact details, full page URLs or invite tokens.
For signed-in accounts, the only account identifier we send is the Supabase user ID. Guests and visitors use a random visit identifier. On iPhone and Android, this identifier is saved on your device so it survives app restarts until you sign in. On the web, it stays in memory for that visit. Signing in can connect the current visit's events to your account ID. We reset the analytics identity and clear the saved visit identifier when you sign out or delete your account. We do not send PostHog your name, email address or phone number.
There is no automatic click or form capture and no session replay. PostHog analytics does not use cookies or browser storage; refreshing the page starts a new anonymous visit. Like any service receiving network requests, PostHog receives ordinary connection information such as an IP address and browser headers. We disable location enrichment and send no location information in our events.
These PostHog events are used to improve SplitCheck. They are not sold or used for advertising. The separate iOS Meta ad measurement described above is unchanged.
We use a small number of service providers to run SplitCheck:
The app also makes a periodic request to a Google endpoint to check whether your device is online. It carries no app data, though Google receives ordinary network information such as your IP address.
SplitCheck is shared by design. Anyone in a group with you can see your display name, the expenses you add, amounts you paid, what you owe or are owed, and any notes you write on an expense. Think of an expense note the way you'd think of a message to the group — don't put anything in it you wouldn't want the others to read.
Data is transmitted over encrypted connections and stored with access rules that restrict each account to its own groups and expenses. No system is perfectly secure, but we take this seriously and design for it.
We keep your account and expense data for as long as your account exists. Expenses stay visible to a group as long as the group exists, since removing one person's expenses would break everyone else's balances.
If you want your account deleted, follow the account-deletion instructions or email us at the address below. You can request deletion without the app. Shared expenses and settlements remain visible to other group members under “Deleted user” so their history and balances stay consistent. An active subscription must be canceled separately through Apple or Google Play; deleting your account does not stop billing.
Email deletion requests are completed within 30 days of the request. Deleted data may remain in database backups for up to 30 days, until those backups roll off automatically. Shared expenses are kept for as long as the group exists, with your name anonymized so they no longer identify you, because other members' balances depend on them. Apple, Google Play and RevenueCat keep their own subscription and purchase records under their policies; cancel your subscription in the store before deleting your account.
Depending on where you live, you may have additional rights under laws such as the GDPR or the CCPA — including the right to access, correct, delete, or port your data, and to object to certain processing. Write to us and we'll honour them.
SplitCheck is not directed at children under 13, and we don't knowingly collect their information. If you believe a child has given us personal data, contact us and we'll remove it.
Our providers operate in the United States and elsewhere. If you use SplitCheck from another country, your information will be processed in countries whose data protection laws may differ from your own.
If we change this policy we'll update the date at the top. For anything significant, we'll tell you in the app.
Questions, requests, or complaints: support@splitcheck.me
Part2AI, Inc.