Security
Financial data deserves serious handling
These are the controls implemented in the product today, described plainly.
Tenant isolation at the database boundary
Every financial table carries an organisation identifier and enforces row level security, so a query can only ever reach data belonging to an organisation you are a member of.
Credentials stay server side
Provider tokens are encrypted before storage and are never sent to the browser, to logs, to analytics or to a language model.
Data minimisation before any AI call
The model receives a small, purpose-built evidence package. Customer names, account numbers and connector tokens are removed first.
Answers you can audit
Every answer records the evidence, the calculation method, the assumptions and the data freshness behind it.
Least privilege by default
Support access is disabled unless explicitly granted, and every grant writes an audit event.
You stay in control
Disconnect a provider, export your data or request deletion from settings at any time.
What we have not claimed
FounderOS has not completed an independent security certification. We do not display SOC 2, ISO 27001 or similar badges, because we have not earned them yet. If a certification is important to your decision, ask us where it sits on the roadmap.
Before FounderOS is offered publicly in Australia, the financial services boundaries, privacy obligations, consumer law representations and CDR arrangements must be reviewed by appropriate professionals.