How Altivo keeps your school's data isolated from every other school, how login and roles work, how deleting a record actually behaves, and what Altivo does and does not do with your data.
Data Security and Privacy
Many schools share the same Altivo infrastructure, but each one's data is completely separate - like an apartment building where everyone shares walls but each unit has its own lock.
Every record - sponsors, assets, sponsorships, allocations, enquiries - is tagged to a specific school
Your school is identified from your verified login token on every request. It cannot be changed or spoofed from the browser
If a request's token does not match the school being asked for, it is rejected immediately with nothing returned
This is enforced twice, independently: once by the application, and again by the database itself. If one layer had a flaw, the other still blocks the request
Altivo uses Supabase Auth. Logging in issues a secure signed token identifying you and your school, sent with every request after that.
Passwords are never stored in plain text
Tokens are cryptographically signed and cannot be forged or edited
Tokens expire, requiring you to log in again periodically
Everything runs over HTTPS - all traffic is encrypted
Login attempts are rate-limited as a defence against automated guessing
| Role | View | Add / edit / delete | Manage users & settings |
|---|---|---|---|
| School Admin | Yes | Yes | Yes |
| School Manager | Yes | Yes | No |
| School Viewer | Yes | No | No |
Roles are enforced by the backend, not just hidden in the interface - even if someone found a way to trigger a restricted action, the request would still be rejected server-side.
Nothing is ever truly erased from the database. Deleting a record hides it from your views immediately, but the underlying data is kept - which protects your financial history and guards against an accidental click.
If you delete something by mistake, contact d6 support with the details. Restoring it is a manual step on our side, not something you or a support agent can undo instantly from the interface - so it may take a little time, and the sooner you flag it the easier it is to find.
Never sold, shared, or transferred to a third party
Never used to train any AI model
Never viewed by d6 staff without a specific, authorised support reason
No. Isolation is enforced at both the application and database level. There is no shared view, and no way for one school's admin to reach another's records, even by accident.
Yes - deletes are soft, so the data still exists. Contact d6 support with what was deleted and roughly when, and it can be restored.
Treat this as urgent. Contact d6 support immediately with exactly what you saw and when. Do not wait to see if it happens again.
No. It reads your live data to answer a question, and nothing from that exchange is stored afterwards or used to train any model. Each conversation is independent.
Last updated: September 2026 | Version 3.0