Skip to content
Splitfold

Security

Private numbers, kept private.

Royalty statements decide what people get paid. Here is what Splitfold does to protect them, the settings worth turning on, and what runs underneath.

Three things to set up first

  1. 1

    Turn on two-factor sign-in

    Account, then Security. Keep the backup codes somewhere other than your phone.

  2. 2

    Give each person their own login

    Invite teammates with the smallest role that works. An accountant only needs Viewer.

  3. 3

    Collect bank details in the portal

    Ask collaborators to enter payout details there instead of sending them by email.

Controls in your workspace

Each one is on from the start or one setting away. The link under each opens the guide that walks through it.

  • Two-factor sign-in

    Codes from an authenticator app, with single-use backup codes. Once enabled, a second factor is required when signing in.

    Turn on two-factor
  • Signed-in devices

    See every device on your account and sign out one or all of them. Sessions end after 30 days.

    Manage sessions
  • Owner, editor and viewer roles

    Owners close months, record payouts and manage members. Editors change the ledger. Viewers only read.

    What each role can do
  • Audit log with before and after

    Changes to splits, mappings, costs, months and payouts are kept with who made them and both values.

    Read about the audit log
  • Closed months stay closed

    A closed month never changes. Corrections land in the next open month, so a statement you sent still adds up.

    Closing a month
  • Sealed payout details

    Bank details collaborators enter are encrypted. Only owners can open them, a few times an hour, and each view is logged.

    The collaborator portal
  • Verified email addresses

    Collaborators see only statements for the address they signed in with. Accepting an invitation needs a verified email.

    How collaborators sign in
  • Export or delete

    Download sales, statements and history as CSV at any time, even read-only. Delete your account after an email check.

    Exporting your numbers

What runs underneath

The parts you don’t configure, because they are always on.

Hosting
The app, its database (D1) and its file storage (R2) run on Cloudflare. There is no separate server of ours to patch or leave open.
Encryption
Every connection uses HTTPS, with HSTS. Cloudflare encrypts stored data at rest. Store tokens, webhook secrets and payout details are sealed with AES-256-GCM under keys kept apart from the database.
Uploaded files
Sales files are checked by their contents: CSV up to 20 MB or Excel up to 10 MB, read without running macros. They sit in a private bucket and are served back only after an access check.
Workspace isolation
Every request is scoped to the workspace on your session and checked on the server. A workspace sent by the browser is never trusted.
Abuse protection
Sign-in, password resets and two-factor attempts are rate limited and guarded by Cloudflare Turnstile.
Locked-down pages
A strict content security policy limits what the browser may load, and other sites cannot frame Splitfold.
Support access
When you ask for help, an authorized administrator can view your account for up to an hour. Each visit is recorded.
Backups
Cloudflare D1 keeps a point-in-time history, so the database can be restored to an earlier moment.
Billing
Polar bills your plan as merchant of record, and card details go only to them. Splitfold never holds or moves money.

Responsible disclosure

Found a weakness? Tell us first.

Email us and a person will read it and reply. Please give us a reasonable time to fix the problem before sharing details, and don’t access other people’s data while testing.

  1. 1What you found and where
  2. 2Steps to reproduce it
  3. 3What someone could do with it
support@splitfold.com

Policies and providers