Security

Your money data, treated like money.

Sign in with Google or Microsoft. No password to steal. Two factors required. proxo is built for financial records, and the controls below ship on every plan — none of them is an enterprise upsell.

View our Trust Center ↗

Sign-in

Zero-password sign-in. Two factors required.

You sign in with a Google or Microsoft account. proxo has no password of its own, so there is no proxo password to steal, reuse or reset.

Customers sign in with a Google or Microsoft account. proxo has no password login, reset or change flow.
Every customer account must enroll an authenticator app or a hardware security key before using proxo
Security keys and passkeys (FIDO2 / WebAuthn) work for every user and are required for proxo's own administrators
Sensitive actions such as API keys, security keys, bank accounts and account deletion ask for a fresh second-factor check, valid for 5 minutes.

Customer sign-in: Google or Microsoft account
Passwords: None to sign in. No login, reset or change flow
Second factor: Required on every customer account: authenticator app (TOTP) or hardware key
Security keys: FIDO2 / WebAuthn keys and passkeys. Required for proxo administrators
Fresh check: API keys, security keys, account deletion, bank accounts

API keys and MCP connections authenticate with a key, which can only be created or rotated after a fresh second-factor check. Read-only reviewer links are minted only by proxo staff and open an isolated demo environment, separate from customer accounts.

Encryption at rest

AES-256-GCM. Every sensitive field.

Account numbers, personal details and retained files are sealed with AES-256-GCM — authenticated encryption, so a value that has been tampered with fails to decrypt instead of returning something wrong.

Keys rotate without downtime: every value names the key that sealed it
Keys live outside the database, never beside the data they protect
Emails and tokens are found by keyed HMAC-SHA256, not stored in plaintext to search on

Cipher: AES-256-GCM
Key size: 256-bit
Nonce: 96-bit, fresh for every value
Integrity: 128-bit GCM tag
Bound to the data: Format version and key id, authenticated with the ciphertext
Lookups: Keyed HMAC-SHA256
In transit: TLS on every connection

Two-factor authentication

Required on every customer account: each user enrolls an authenticator app (TOTP) or a hardware security key (FIDO2) before using proxo, with backup codes. proxo's own administrators are required to use a security key (FIDO2 / WebAuthn).

Full audit logging

Every action is attributed — who did what, when, and field by field what changed. Approvals, edits, logins and AI-chat writes land in the same audit trail.

Encryption at rest and in transit

Sensitive fields and retained files are encrypted with AES-256-GCM under rotatable, versioned keys. All traffic runs over TLS.

Entity isolation

Every query is scoped to the entities you can access — enforced in the data layer, not the UI. Roles grant privilege; your selected organization bounds the view.

Bank statements are never stored

Uploaded statements are extracted in memory and discarded — proxo keeps the transactions, not the document. Failed extractions are retained encrypted for at most 14 days, then deleted unconditionally.

Role-based access

Per-entity roles from viewer to principal, with Maker-Checker Approval thresholds you set. The AI chat obeys the same permissions as the person using it.

Read-only bank connections

Bank links via Plaid are read-only transaction synchronization. proxo never holds credentials to move your money — it is not a payment processor and does not custody funds.

AI writes need your click

The chat assistant previews every create, update or archive as a card and waits for your confirmation before anything touches the database — in the app and in Slack.

You own your data

Your records are yours. Export any list at any time; the Terms of Use say the same thing in writing.

Security on every plan. Not a price point.

Start free for 7 days

Our controls and compliance status are public in the Trust Center. Our SOC 2 Type I program is in progress; the auditor's engagement letter is published there. Questions about our practices — see the Privacy Policy and Terms of Use, or write to security@proxo.ai.

Found a vulnerability? Write to security@proxo.ai. We read every report, reply to good-faith researchers and do not pursue them. The machine-readable contact file is /.well-known/security.txt.