Security

How your financial data is handled.

In plain language for owners, with the technical detail a procurement review asks for. The short version: the least access the work needs, revocable by you in one click, and your data stays in your own systems wherever the work allows.

Revocable in one click AES-256 at rest, TLS 1.2+ in transit MFA on every account Never used to train AI
At a glanceStandard v.2026.2
Review accessRead-only
Revoking accessOne click, any time
EncryptionAES-256 · TLS 1.2+
AccountsMFA on every one
Data residencySydney by default
AI trainingNever on your data
Access, by service

Different work, different access. One standard.

The free reviewFractional CFOA read-only user invite to your accounting system that you grant, plus any files you choose to send. View only: nothing is changed in your system, with no payments and nothing exported beyond the review. You can revoke it at any time, and I confirm in writing when the review is done. Files are deleted within 14 days if no work follows.
A CFO projectFixed-fee buildAccess carries over from the review, so nothing is collected twice. Write access to named areas (chart of accounts, tracking categories, journals) only where the agreed scope needs it, agreed in writing. Revoked on handover, with a change log of everything touched in your system.
Ongoing CFOMonthlyA monthly accounting export plus the operating data agreed at scoping. If you use the client portal, it is named users only, with per-client isolation and a CSV export at any time. Stop any month: the portal closes within 30 days of the work ending, with a full CSV export, and the model stays with you.
BookkeepingXeroXero adviser access, which is what weekly reconciliation and month end need, and read-only wherever the work allows it. You grant it and you can revoke it in one click. Your books stay in your Xero: you own the file throughout and keep it, with every monthly note, if you leave.
Controls

The technical layer.

Production runs on Supabase, Render and Vercel, each SOC 2 Type II attested. The attestation applies to those providers; Infraxus does not hold its own. Links are available on request.

Layer 03 · Portal

Named users, role-scoped, audit-ready.

Session auth · MFA · SSO on request

Each named user sees only the clients they are mapped to. MFA is enforced on every portal account, sessions expire on a set schedule, and a user can be revoked in minutes. The named-user audit log is exportable at any time.

Layer 02 · Application

Encrypted in transit and at rest.

TLS 1.2+ · AES-256 · service-role keys

Every connection terminates TLS 1.2 or higher, and every stored byte sits behind AES-256. Backend access uses service-role keys only, with no long-lived tokens shared with anyone.

Layer 01 · Database

Per-client isolation, enforced in SQL.

Postgres · row-level security · 7-day recovery

Every query is scoped to the requesting user’s clients through row-level security. Daily automated snapshots with seven-day point-in-time recovery.

The founder’s own accounts are locked down too.

Infraxus is founder-operated, so MFA is enforced on every account that touches client data: hosting, database, application, email and AI provider. Admin credentials sit in 1Password, devices are disk-encrypted, and client working data lives in access-controlled, MFA-gated cloud storage, never on a local disk.

Incidents are reported within 24 hours.

If a security incident affecting your data is confirmed, you are told within 24 hours what happened, what was affected and what was done about it, in line with the breach-notification law that applies where you are.

AI handling

AI-assisted, reviewed by a person, never trained on your data.

AI helps with data preparation, reconciliation, anomaly checks and first drafts. Calls route through OpenRouter to Anthropic, per query only. Prompts are not logged by default, and your data is not used to train any model.

Every output is reviewed by Liam before it reaches you. AI produces analysis; it does not take responsibility for what the numbers mean.

Residency and sub-processors

Sydney by default. Other regions on request.

The portal database and hosting sit in Sydney (ap-southeast-2). Frankfurt (eu-central-1) and US-east (us-east-1) can be provisioned before work begins, and residency does not change without a written request.

ProcessorRoleWhere
SupabaseDatabase, auth, session managementSydney, AU
VercelPortal and website hostingSydney, AU, and global CDN
RenderBackend API and ingestion, in transit onlySingapore
OpenRouterRouting for AI requests to AnthropicUnited States
AnthropicAI model providerUnited States
ResendTransactional emailUnited States
PostHogWebsite analyticsUnited States
StripeBookkeeping subscription paymentsUnited States
CalendlyCall schedulingUnited States
DropboxAccess-controlled working storageOperator account, MFA-gated
Bookkeeping access

Your ledger stays in your own file.

Bookkeeping runs inside the accounting file you already own, in QuickBooks Online or in Xero. Infraxus is granted access from inside that file, as a user you invite and can remove. Nothing is copied into a ledger of ours, because there is no ledger of ours.

  • How access is granted. You invite liam@infraxus.com from inside your own file. In QuickBooks Online that is Settings, then Manage users, then Accountants. In Xero it is Settings, then Users, as an Adviser. You choose the role and you can see the access in your file at any time.
  • Online banking. Infraxus never asks for your online-banking password and never holds one. Bank feeds reach your accounting file through the connections that file already has with your bank.
  • Removing access. Remove Infraxus from your users at any time, without telling us first. The steps are on the disconnect page. The ledger and its history stay in your file.
  • What Infraxus holds. Your work email, your business name, which platform your books are on, your revenue band, and your billing record with Stripe. That is the whole list. See the US privacy notice.
  • No Intuit app, today. There is no OAuth application and no token to store, because access is a user invitation inside your own file rather than a connected app.
Exit and procurement

You leave with everything.

Models are built in your own Excel or Google Sheets from day one, with every formula visible. If ongoing work ends, the workbook stays with you, the portal is closed within 30 days, and you get a full CSV export of its history. Your books never leave your Xero.

Available on request
  • Provider SOC 2 attestation links
  • Data Processing Agreement (DPA)
  • Current sub-processor list
  • SSO for the client portal
  • A mutual NDA
Next step

Book the twenty minutes.

Free. A written verdict on your finance function within 24 hours. Yours to keep whatever you decide.

Need the books done first? Bookkeeping, first month free, no card needed. See bookkeeping

What happens next.

  • 01You pick a time for the 20 minute call, straight after a short form.
  • 02Nothing to prepare. Twenty minutes, phone or video, whichever you prefer.
  • 03If the review is worth doing, your written verdict lands within 24 hours, then a 45 minute call where I walk you through it.