Every family kept separate
The database itself refuses to show one family's records to anyone outside that family, including advisors who work with several families.
Checked by an automated test
Your family's records are some of the most sensitive data there is. This page lists every control we claim, and the ones we are still building. Controls shown as in place are checked by an automated test.
Last reviewed 1 October 2026
The database itself refuses to show one family's records to anyone outside that family, including advisors who work with several families.
Checked by an automated test
Everyone signs in with a password and a code from an authenticator app. Without the code, the database returns no family data.
Checked by an automated test
Each change is logged with who made it and when, including changes made by imports. The log cannot be edited.
Checked by an automated test
People see only what their role and the entities they are given allow, and access can be set to expire.
Checked by an automated test
Staff accounts are blocked from all financial records, and no permission can override that.
Checked by an automated test
An advisor working with several families sees one family at a time. Families are never combined or searched together.
Checked by an automated test
Files are private, and only people who can see the record a document belongs to can open it.
Checked by an automated test
Earlier versions can be restored, deleted records can be brought back, and the owner can require approval for sensitive changes.
Checked by an automated test
The owner can download a complete copy of everything in the family workspace at any time.
Built into the product
Oikos has not been deployed yet. We plan to host in the EU, and will say so here when it is true.
Tax numbers and similar fields are not separately encrypted yet. We will add this before any real family data is used.
Sign-in with a passkey is planned. Authenticator-app codes work today.
Backups and recovery drills depend on deployment and are not in place yet.
We plan an independent penetration test before the product is released to the public.
A data processing agreement and a way to ask for deletion are planned before launch.
Alerts for unusual exports or sign-ins are planned.
Our assistant, Ruppert, is not built yet. We intend never to train AI models on customer records, and will put that in our terms.
Formal certifications such as ISO 27001 are not planned yet. They cost more than an early product can justify.
Oikos is in development and is not yet available to the public. No real family data should be entered until the planned controls above that protect it are in place.