Security

Your books
stay your books.

Argus is a read-only audit layer. We can't write to your books — there is no API path for it. We can't sell your data — there's no business model for it. Here's the technical detail on how that works.

— TL;DR for security teams

Five things to know.

01 Read-only QuickBooks access. OAuth 2.0 with read scopes only. No write scopes are requested or granted. Argus has no programmatic ability to modify a transaction, journal entry, customer, or vendor. ENFORCED BY OAUTH
02 Encryption end to end. QuickBooks tokens are AES-256-GCM encrypted at the application layer with a per-environment master key. Disk is encrypted by Azure (AES-256). All transport is TLS 1.2+. AES-256-GCM
03 Data resident in Canada. All Argus infrastructure runs in Azure Canada Central (Toronto). Backups stay in-region. We don't replicate to US or EU regions without explicit customer consent. CANADA CENTRAL
04 No data sale, no model training. Customer data is never sold, anonymized for resale, or used to train external AI models. Internal anomaly heuristics are tuned per-tenant — they never leave your dataset. CONTRACTUAL
05 Right to be forgotten. Disconnect any QuickBooks account and Argus immediately stops fetching. Cached snapshots are purged within 30 days. Account deletion is honored within 7 days of request. 30 DAY PURGE
— How data flows

QuickBooks → Argus → your screen.

Every data touch is read-only, encrypted, and scoped to the smallest possible blast radius. Below is exactly what happens between you clicking "Connect" and seeing your first health check.

— Step 01

OAuth handshake.

You sign in to QuickBooks directly — Argus never sees your QuickBooks password. Intuit returns short-lived OAuth tokens scoped to read-only access on a single realm.

— Step 02

Token encryption.

Tokens are immediately encrypted at the application layer with AES-256-GCM using a per-environment master key, then stored in our database. Decryption happens in-process, in-memory, only when Argus calls QuickBooks.

— Step 03

Read, summarize, store.

Argus pulls the QBO reports needed for the active checks — P&L, balance sheet, AR aging, GL detail. We store summaries (per-day snapshots) and check results, not the entire general ledger.

— Step 04

Run the checks.

The 11 deterministic rule-based checks run first; the AI-augmented anomaly detection runs second. Both run inside our Canada Central deployment — data never leaves the region for processing.

— Step 05

Render to your dashboard.

Results stream over an authenticated SSE channel. All transport is TLS 1.2+ with HSTS. Sessions are signed with a rotating server-side secret and expire on inactivity.

— Step 06

Purge on disconnect.

Click "Disconnect" and Argus stops calling QBO that minute. Cached transaction snapshots are purged within 30 days. Account deletion (full tenant wipe) is honored within 7 days.

— Authentication

Sign in with what
you already use.

Argus uses Better Auth for self-managed authentication. Three sign-in methods are supported, with optional MFA on email/password. SSO via Google or Microsoft is available on Firm-tier plans.

— Method 01

Email + password.

Hashed with Argon2id. Optional TOTP MFA on every account. Rate-limited login with exponential backoff after failed attempts.

— Method 02

Google sign-in.

Standard OAuth 2.0 with OpenID Connect. We never see your Google password. MFA inherits from your Google account.

— Method 03

Microsoft SSO.

Azure AD / Entra ID via OAuth 2.0. SCIM provisioning available on Firm-tier plans. Conditional access policies inherited from your tenant.

— Infrastructure

One region.
One deployment.

Less is more for security. Argus runs in a single Azure region with a small attack surface, well-understood dependencies, and short data paths.

Hosting Azure App Service for Containers · Canada Central · single region · no cross-region replication without explicit customer consent. CANADA CENTRAL
Database SQLite (better-sqlite3) on a persistent Azure Files volume. WAL mode. Daily encrypted snapshots retained for 30 days, weekly retained for 90 days. SQLITE WAL
Encryption at rest Disk volume encrypted by Azure with AES-256. Application-layer AES-256-GCM on top, for QuickBooks tokens and any user-generated note attachments. AES-256-GCM
Encryption in transit TLS 1.2+ enforced. HSTS with 1-year max-age and preload. CSP headers prohibit external script execution. Modern cipher suites only. TLS 1.2+
Secrets management All credentials (master keys, OAuth client secrets, third-party API keys) in Azure Key Vault. Rotated quarterly. Never committed to source control. AZURE KEY VAULT
Access controls Production access is limited to two co-founders. All admin actions are logged to an immutable audit trail with originating IP and timestamp. 2 ENGINEERS
— Where we are, where we're going

Compliance, honestly stated.

We won't claim certifications we don't have. Below is exactly where Argus stands today and what's on the roadmap.

— Today

PIPEDA-aligned.

Argus operates under Canadian privacy law (PIPEDA). Data minimization, consent, retention, and deletion practices follow PIPEDA principles. A signed DPA is available on request for any plan.

— Not yet

SOC 2.

No SOC 2 audit at this stage. We may pursue Type I when customer demand justifies the cost. We will not claim "in progress" until an auditor is engaged and a window is scoped.

— Not yet

ISO 27001.

Not pursued. Our security posture mirrors many ISO 27001 controls in spirit, but we don't hold the certification and won't claim alignment we haven't earned.

— Available

Annual pen test.

Third-party penetration test scheduled annually. Latest summary report available on request under NDA for prospective enterprise customers.

— Incident reporting

Found something?
Tell us.

Security disclosures go to security@argus.app. We commit to acknowledging within 24 hours, publishing a summary within 7 days of resolution, and crediting reporters who ask to be named. We don't currently run a paid bug bounty, but we do say thank you with real money.

Have a deeper
security question?

We'll happily walk a security or IT team through the architecture, encryption design, and data flow on a 30-minute call. NDA available on request.