Security

Effective date: 22/09/2026. This page describes the measures Splitwiser takes to protect your account and your data. No online service can promise perfect security, and this page is a description of our practices rather than a warranty.

Splitwiser holds what people spend and who they spend it with, so we take reasonable security measures, including technical and organizational safeguards, to keep that information safe. This page explains the main security measures we use and what you can do to help protect your information.

1. Signing in

There is no account password to steal. You sign in with a one-time link and a six-digit code sent to your email, or with Google or Apple.

  • Links and codes work once and expire after 15 minutes.
  • A limited number of login emails and code attempts are allowed before a short cooldown, which slows down anyone trying to guess.
  • Where an administrator account uses a password, it is stored only as a salted PBKDF2 hash — never in readable form — and is compared without revealing where it differs.

2. Data in transit

All traffic between your device and Splitwiser travels over HTTPS (TLS). Plain-text HTTP is redirected to the secure address, and browsers are asked to remember to use HTTPS for the future (HSTS), so information is encrypted while it moves across the network.

3. Data at rest

The data files on our servers are encrypted using authenticated encryption (AES-256-GCM). Because the encryption is authenticated, tampering with a stored file is detected rather than silently accepted. A stolen backup or disk snapshot is unreadable without the key.

4. Who can see your data

Splitwiser is built so you only ever receive your own part of the shared data — your account, the people you share a group or friendship with, those groups, and the expenses in them. Nothing outside that circle leaves the server.

  • Every request that touches shared data has to prove which account is making it.
  • You cannot read, change, or delete data belonging to people you do not share with.
  • The figures in an expense are checked on the server, so a participant cannot quietly alter amounts in a way that would skew someone else’s balance.

5. Sessions

When you sign in, your device is given a signed session token that identifies you. Signing out ends it, and an account that an administrator disables or that is deleted loses its sessions right away. Sessions expire on their own after a period of inactivity.

A group can be shared as a read-only view protected by a password. That password is checked on the server, not in the browser, and repeated wrong attempts lock the link for a short time. A read-only link can view only that one group and cannot change anything.

7. Uploads

Receipts and images you upload are served with no privileges of their own — no scripts, no network access, isolated from the rest of the site — so an uploaded file cannot run code or interfere with your account or anyone else’s.

8. The admin panel

People who help run Splitwiser are given only the sections their role needs. The server enforces those limits directly — anything outside a person’s role is refused, not merely hidden — and only an owner can add administrators or change what they can access.

9. Payments and integrations

Card details are handled by the payment provider and do not reach our servers. Messages we receive from payment and marketplace providers are verified by signature and checked for freshness before they are acted on, so a forged or replayed message is rejected.

10. Backups and availability

Data is backed up on a regular schedule so it can be restored if something goes wrong. We aim to keep the Service available and to apply security updates promptly, though we cannot guarantee uninterrupted availability.

11. Your part

Security is shared. You can help keep your account safe by:

  • Keeping access to your email account secure, since that is how you sign in.
  • Signing out on shared or public devices.
  • Keeping your device, browser, and operating system up to date.
  • Being careful about what you add to shared groups, and who you invite.
  • Telling us promptly if you think someone else has accessed your account.

12. Reporting a security problem

If you believe you have found a security vulnerability, please tell us before disclosing it anywhere else, and give us a reasonable chance to fix it. Describe what you found and how to reproduce it.

  • Please do not access, alter, or delete data that is not yours.
  • Please do not run tests against other people’s accounts, or attempt denial-of-service, spam, or social-engineering attacks.
  • Act in good faith and within the law, and we will respond in good faith.
Report a security issue by email to support@splitwiser.com, or through the contact page. We read these promptly.

13. Limits

No internet-based service or storage system can be guaranteed to be completely secure, and nothing on this page is a warranty. We describe our measures honestly and improve them over time, but you use the Service understanding that some risk always remains.

14. Changes to this page

We may update this page as our systems and safeguards change. Significant changes will be reflected by updating the effective date above.

15. Contact

For security matters, email support@splitwiser.co. For anything else, use the contact page.