Where does my data actually live.
It is the first thing everyone asks, so it goes first. Your own database, on AWS in the region assigned to your firm, which today is Sydney for every customer, never used to train models, and removed from production systems within the period stated in our Terms when you leave.
Who can open it, and what they see inside it.
These get conflated constantly and they are not the same control. Most tools have the first one. A practice cannot roll anything out past two partners without the second.
User groups
Decide who can open a report at all, and who a Pulse sends to. Team A gets the productivity pack; the board gets the consolidated one.
Row-level security
Decides what they see inside one they are allowed to open. Applied before the query runs, so restricted rows are never selected - not stripped out on the way back.
Never used to train models
EVA runs on Amazon Bedrock under our AWS agreement: neither model developer receives your data, and no model is trained on it. Under our Xero partnership we are contractually prohibited from training on client data.
Scoped to your data
Every business has its own database credentials, and EVA holds only the credentials for your data. EVA can build export files from your data when you ask, and can act on tools your business has connected only after you confirm each action.
She does not guess
EVA writes SQL against your own database. When the data is thin she says so instead of filling the gap, and she will not render a figure she cannot source.
Multi-factor authentication
Available to every user, with authenticator app and SMS support. Firms can require it for all of their users. Required for all VibeCFO staff. Automatic session timeout.
Encryption
TLS 1.3 for every connection from the internet. Uploaded documents, logs and backups encrypted at rest (AES-256). Encryption at rest of the production database and encryption of the remaining internal connections are scheduled, with completion targeted for 2026-10-16.
Access controls and audit logging
Role-based permissions enforced on the server. Infrastructure and administrative actions logged (AWS CloudTrail), database connections audited, and EVA questions and answers traced. Threat detection and suspicious-activity monitoring (Amazon GuardDuty).
Certification and assessment
Gap analysis complete, management review held, remediation under way with an independent internal audit and external audit scheduled. Target certification: December 2026.
Passed, August 2025Operating today: infrastructure audit logging (AWS CloudTrail), threat detection (Amazon GuardDuty), database connection auditing, daily immutable backups of platform records with a restore test performed, TLS 1.3 at every public endpoint, and a documented incident response process with customer notification within 72 hours of a confirmed incident.
Security, answered.
Where is my data stored?
In the AWS region assigned to your firm, which today is Sydney, Australia, for every customer. Encrypted in transit with TLS 1.3; uploaded documents and backups encrypted at rest, with encryption at rest of the production database scheduled for completion by 2026-10-16. AI model processing may take place outside Australia; see our Privacy Policy.
Does my data leave Australia when EVA answers a question?
Our platform runs on AWS in the region assigned to your firm. Today that is Australia (Sydney) for every customer, wherever they are located, and we will say so here before any customer data is hosted in another region. EVA runs on Amazon Bedrock under our AWS agreement. The model that orchestrates each request is supplied by Anthropic and runs in AWS Australia. The model that does the heavy lifting is supplied by OpenAI and runs on AWS infrastructure, which may be outside Australia. Neither model developer receives your data through Amazon Bedrock, and no model is trained on it. We also use the Anthropic API directly for web search, for document exports and as a backup, and that processing takes place in the United States. Those providers do not train on your data. We move to newer model versions from each provider as they are released, and we update this page if the provider, the country of processing or the categories of data we send change. Each provider is listed, with where it processes data, on the subprocessors page.
Is my data used to train AI models?
No. Your financial data, numerical results and client information are never used to train any model, ours or anyone else's, and that holds whichever model sits underneath the product. Our Terms commit that we do not use Customer Data to train third-party AI models, and our AI model providers' enterprise terms prohibit training on your data.
Can I put confidential business data into VibeCFO?
Yes. Every business gets its own database. Access is controlled at two layers: the application resolves which database a request may reach from the signed-in user's own firm membership, and each business has its own database credentials, which are the only credentials EVA holds for your data. Firm-level segmentation: firms managing multiple clients get row-level security, so each client organisation only sees its own data. Tenant isolation is part of the scope of our security testing programme.
What is row-level security and why does it matter?
Row-level security decides which rows a person may see inside a report they are allowed to open. It is applied before the query executes rather than filtering results afterwards, so restricted rows are never selected at all. That is a permission rather than a filter, and it is the distinction auditors ask about.
Can I share reports with my team or my clients?
Yes, through user groups. A group decides who can open a report; row-level security decides what each of them sees inside it. A pack sent to nine people can legitimately produce nine different documents.
Do you support SSO and MFA?
Yes. Single sign-on and multi-factor authentication are built into the platform rather than bought in from an identity vendor. Multi-factor authentication is available to every user, with authenticator app and SMS support; firms can require it for all of their users, and it is required for all VibeCFO staff. Sessions time out automatically. Role-based permissions are enforced on the server. Infrastructure and administrative actions are logged (AWS CloudTrail), database connections are audited, and EVA questions and answers are traced. Access control is a security claim and a product surface at once: the same groups and row-level rules that govern reports govern every question asked.
Are you ISO certified?
Not yet - and we will say certified when we are certified. In progress, not yet certified: ISO/IEC 27001:2022 and ISO/IEC 42001 certification. Gap analysis complete, management review held, remediation under way with an independent internal audit and external audit scheduled. Target certification: December 2026. Operating today: infrastructure audit logging (AWS CloudTrail), threat detection (Amazon GuardDuty), database connection auditing, daily immutable backups of platform records with a restore test performed, TLS 1.3 at every public endpoint, and a documented incident response process with customer notification within 72 hours of a confirmed incident.
What happens to my data if I leave?
When you leave, your data is removed from production systems within the period stated in our Terms.
Ask us the hard questions.
Jez runs the demo himself and would rather tell you it is not a fit than sell you a fortnight of your own time.