Modern sign-in
Accounts use current sign-in practices, so access doesn't depend on a shared password in a group chat.
Security
Money records deserve real care
A group's savings are built on trust, and the record of them should be treated that way. This page explains, plainly, how Savipy protects accounts, limits access and keeps your group's data its own.
Protecting accounts
Keeping the right person signed in, and everyone else out
A ledger is only as safe as the accounts that can write to it. Savipy puts several layers around each sign-in.
Two-factor with recovery codes
Add a second step at sign-in. Recovery codes mean losing a phone doesn't lock you out of your group's books.
Session management
See where you're signed in and end sessions you don't recognise or no longer need.
Device lock and biometric unlock
On the mobile apps, lock Savipy behind your device and unlock it with your fingerprint or face.
The right access for each person
People see and do what their role allows
Access is decided by the server, not by what the screen happens to show. Hiding a button is not the same as blocking an action.
Role-based access
Treasurers, chairpersons, members and admins each get permissions that fit what they actually do.
Enforced on the server
Every request is checked against the person's role before anything changes, whichever app they use.
Authority is group-specific
Being treasurer in one group doesn't make you treasurer in another group under the same organisation.
Least privilege
Give people the access their job needs and nothing beyond it. Nothing counts until it's approved.
Your group's data stays yours
Separate books, and a history behind every change
Savings groups hold each other's trust. The software should make it easy to check that trust, not ask you to take it on faith.
Each organisation kept separate
Your organisation's data is held apart from every other organisation's.
An audit trail behind every change
Savipy keeps a record of what changed, so questions about the books can be answered from the history.
Recorder is not always the owner
The person who enters a transaction isn't necessarily the member the money belongs to. Savipy tracks both, so a treasurer recording a deposit never becomes its owner by accident.
Good habits built in
Safe by default, and honest about what we'll never ask
Some of the best protection is in what the product refuses to do.
No PIN requests, ever
Savipy never asks for your bank or mobile-money PIN. If anyone claiming to be us does, don't share it.
Delete your account on request
You can ask for your account to be deleted. Get in touch and we'll take it from there.
Reporting a problem
Found something that doesn't look right?
If you think you've found a security problem, or something in your group's account looks off, tell us. Email hello@savipy.com with what you saw and how to reproduce it. Please don't include passwords or PINs. We'd rather hear about it early than late.
Savipy is operated by Astroteck Bridge Ltd.
Keep your group's books safe and in the open
Set up your group with roles, approvals and two-factor from day one.