Splitlist · shared to-do lists
Last updated 29 September 2026.
Splitlist is a shared to-do list. Friends join a list, add tasks and check them off. This policy explains exactly what the app stores, why it needs it, who else can see it, how long it is kept and how to get rid of it.
The short version. Splitlist stores your account, your profile, your friendships, your lists and tasks, and the record of who checked what off. It contains no advertising, no analytics and no crash-reporting service, and it does not track you across other apps or websites. It never reads your phone's contacts. You can delete your account from inside the app.
Splitlist is operated by the independent developer publishing under the name Splitlist, based in Egypt. Splitlist is the party that decides what the app stores and why — in data protection terms, the data controller.
How to contact us: through the public support tracker at github.com/6dzzx4zb7h-afk/splitlist-support/issues. This is the contact route for privacy questions and for the rights described below. Please do not post passwords or other private details there, since the tracker is public.
| What | Why it exists | Who can see it |
|---|---|---|
| Your account — email address and the authentication data held by Supabase Auth | So you can sign in, recover a password and be reachable about your account | You. Your email address is not shown to other users. |
| Your user ID — a random identifier generated when you sign up | It is how every list, task and check is attributed to you | Other members of lists you share, via the app |
| Your profile — display name, username, and either a built-in avatar you picked or a photo you uploaded | So people in a shared list can tell each other apart | Effectively public. Anyone can find you by searching your username. |
| Your friendships — friend requests you send or receive, and who accepted | You can only add a friend to a list, so the app has to know who your friends are | You and the other person |
| Your lists — names, icons, colours, who owns each one and who is a member | The core function of the app | Current members of that list |
| Your tasks — titles, notes, due dates, repeat settings and assignments | The core function of the app | Current members of that list |
| Completion history — every check and undo, with who did it and when | Splitlist exists to show who did what; a counter task shows who contributed which check | Current members of that list |
| Push tokens — a device notification token, the platform (iOS or Android) and the app version, only if you turn notifications on | So a notification can be routed to your device and stale tokens retired | You. Not shown to other users. |
| Notification settings — which categories you want | So you only get what you asked for | You |
| Notification diagnostics — for each notification, the delivery attempt, the receipt reported back by the push service, and any error | To retry a failed send, and to disable a token the push service reports as dead. This is operational plumbing, not analytics about you. | Nobody but the operator, for troubleshooting |
Notifications are off until you turn them on. If you never enable them, no push token and no delivery record is ever created for you.
Splitlist does not request access to, and does not read, your phone's address book. The app contains no contacts functionality and never asks for the permission that would be required to use one.
Friendships work entirely inside the app. You search for a username that the other person chose and gave you, send a request, and they accept it. Your contacts are never uploaded, scanned or matched against other users.
If you choose to set a profile picture, the app asks for permission to open your photo library and uploads only the single image you select. It does not browse, scan or upload anything else, and it never uses your camera or microphone.
Uploaded avatars are stored in a publicly readable location. Anyone who has the file's web address can view that image, even without a Splitlist account. Please do not upload a picture you would not be willing to make public. The built-in avatars avoid this entirely.
Splitlist does not sell your data and does not share it with advertisers or data brokers. It is handled by two service providers, who process it only to run the app on our behalf:
Supabase provides the database, authentication, file storage
and realtime updates. Everything listed in the table above is stored there.
The Splitlist database is hosted in Tokyo, Japan (Amazon Web
Services region ap-northeast-1). Because the operator is in Egypt
and you may be anywhere, your data is transferred internationally to that
region and stored there.
See the Supabase privacy policy.
If you enable notifications, they are delivered through Expo's push service and from there through Apple's or Google's push network to your device. These providers receive your device's push token and the message.
Push messages say what happened, so you can tell at a glance whether it needs you: the list's name and icon, the title of the task, and the display name of the member who added, assigned, completed or nudged it — for example "🛒 Groceries: Ana added “Buy oat milk”". That text therefore passes through Expo and Apple or Google on its way to your device, and can appear on your lock screen. Notes, due dates, check history and everything else stay in the database and are fetched by the app once you open it.
To keep list and task names off your lock screen, use your phone's own setting to hide notification content while locked, or turn off the notification types you do not want in Splitlist's Settings. Turning notifications off entirely stops anything being sent through these providers.
See the Expo privacy policy.
We may disclose data if legally compelled to, or where it is necessary to protect the rights or safety of users.
Your data is kept for as long as your account exists. There is no automatic expiry, because a to-do list you come back to next year should still be there.
Open the Settings tab in the app and choose Delete account. This removes your sign-in record, your profile, your friendships, your list memberships, your uploaded avatar file, your notification settings and device tokens, and your personal check history.
Two things are worth stating plainly before you do it:
Deletion takes effect immediately, and we cannot undo it for you — as above, we hold no backup to restore from. If you cannot reach the in-app option, you can request deletion through the support tracker.
Different countries grant different rights, and Splitlist has users in many of them. Rather than limit these to one jurisdiction, we extend the following to every user, wherever you live:
Depending on where you live these may be legal entitlements — under the EU or UK GDPR, the California CCPA/CPRA, Egypt's Personal Data Protection Law, or a law local to you. Where they are not, we honour them anyway. Make any request through the support tracker.
We do not sell or share personal information as those terms are defined under California law, and we have no financial incentive programme, so there is nothing for you to opt out of.
Where a legal basis is required: we process your account, profile, lists, tasks and completion history because it is necessary to provide the service you asked for, and we process push tokens and notification settings on the basis of your consent, which you give by turning notifications on and withdraw by turning them off.
Splitlist is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe a child under 13 has created an account, tell us through the support tracker and we will delete it.
All traffic between the app and the server is encrypted in transit over HTTPS. Access to lists and tasks is enforced by row-level security rules in the database itself, so a list you are not a member of is not merely hidden from the app — the server refuses to return it. Passwords are handled by Supabase Auth and are never visible to the operator.
No service can promise perfect security, and Splitlist is no exception. Please do not store anything in a task that would be harmful if it were exposed.
If this policy changes, the date at the top changes with it, and the previous wording remains visible in the public revision history of this page, so you can see exactly what changed and when. Significant changes will also be noted on the support tracker.