EncryptionIn place
- In transit
- TLS 1.2 or higher
- At rest
- AES-256
- Bank tokens
- Separate encrypted vault
- Keys
- Managed service, rotated yearly

Tarn can see your balances and transactions. It can never move money, and it never sees your bank login. Here is how the rest of your data is looked after.
Workspace securityAll good
Four stops, each with one job. Money only ever moves inside your bank, never through Tarn.
You sign in on your bank’s own page. Your password stays there.
11,000+ banksIssues Tarn a read-only token. No payment permissions exist on it.
Read-only tokenBuilds your forecast. Data is encrypted at rest, tokens kept in a separate vault.
AES-256 at restRoles decide who sees balances, who edits, and who can connect accounts.
No path back to your money. Tarn holds no payment permissions, so it cannot move, send or withdraw funds.
What we do today, written plainly. Your IT team can ask for the detail behind any of it.
EncryptionIn place
Access controlsIn place
Four roles, set per person. Owners can require 2-step sign-in for everyone.
| Role | See balances | Edit forecast | Connect accounts | Manage people |
|---|---|---|---|---|
| Owner | Yes | Yes | Yes | Yes |
| Admin | Yes | Yes | Yes | No |
| Adviser | Yes | Yes | No | No |
| Viewer | Yes | No | No | No |
Retention and deletionIn place
Export everything as CSV whenever you like. When you leave, your data leaves with you.
HostingIn place
Incident responseTested twice a year
Staff accessIn place
Support only sees your workspace when you let them, for as long as you choose.
Owners get a full activity log: who signed in, from where, what they changed and what left the workspace.
Signed in now
Doing a vendor review? Tell us what you need and we will send the documents, usually within two working days.
Or write to hello@example.com
(Preview site: nothing was sent.)