Security & Compliance

Kraal holds client books, so security is a product requirement, not a feature. This page describes Kraal's controls in the language firms use when they evaluate vendors — organized around the SOC 2 Trust Services Criteria of security, availability, and confidentiality — and states plainly where Kraal's formal compliance program stands today.

Share this page with a partner, an IT reviewer, or a client who asks how their data is protected.

Compliance status

Kraal has not yet completed a SOC 2 examination and does not currently hold a SOC 2 report (Type I or Type II). We say this plainly because trust documentation is only useful when it is accurate.

What we can accurately say:

• Kraal's controls are designed in alignment with the SOC 2 Trust Services Criteria of security, availability, and confidentiality. The sections below describe those controls.
• Extended security documentation — control detail, policies, and a current subprocessor list — is available on request to evaluating firms.
• If and when Kraal completes a SOC 2 examination or other formal attestation, this page will state exactly what was achieved — and until then, it will not imply otherwise.

Request extended documentation at hello@kraal.ai.

Data security

Aligned with the SOC 2 Security and Confidentiality criteria.

• Encryption in transit. Traffic between your browser and Kraal, and between Kraal and connected services, is encrypted in transit (TLS).
• Encryption at rest. Application data is encrypted at rest on managed infrastructure.
• Credential and token handling. Credentials and access tokens for connected services (banking, accounting, payroll, e-commerce) are encrypted at rest, never displayed in the app, and never exposed in audit views. Kraal support will never ask you for them.
• Tenant isolation. Every organization's data is isolated by server-side scoping: each request is authorized against the caller's organization, role, and client assignments before any data is returned. Client scoping is enforced by the backend on every request — not by the interface hiding entries.
• Payment data. Card details are entered only on the payment provider's hosted checkout page and are never stored on Kraal systems. See Admin & Billing.

Access control

Aligned with the SOC 2 Security criteria for logical access.

• Role-based access. What a user can see and do follows their assigned role. Administrative functions — team management, billing, organization settings — are restricted to admin and owner roles. External client-portal users see only what is explicitly shared with them. See Team, Roles & Permissions for the role-by-role capability breakdown.
• Least-privilege client scoping. Staff access is scoped to the clients they are assigned, so a team member working three clients sees three clients.
• Multi-factor authentication. Users can enroll in MFA, and sensitive actions require step-up verification — a fresh MFA challenge inside an already-authenticated session — before they proceed.
• Invitation-based onboarding. Team members join by invitation from an administrator and arrive with a defined role. Access is removed by the same administrators when someone leaves. See Admin & Billing for recommended access policies.

Change management & auditability

Aligned with the SOC 2 Security criteria for change management and system monitoring.

• Software change management. Product changes ship through version-controlled pull requests that must pass automated checks — tests, type checks, lint, and secret scanning (in CI and pre-commit) — before merge; direct pushes to production branches are blocked. Production deployments are versioned, with documented rollback to a known-good release.
• A receipt for every AI action. Every autonomous or AI-assisted action produces a receipt recording what was done, on what evidence, and why it was allowed to run.
• Full audit trail. Postings, approvals, rejections, and reversals — human and AI — are recorded per client with actor, timestamp, and before/after context where relevant. See Audit Center and Audit Trail & Activity Log.
• Append-only audit events. Audit events are append-only: corrections are made as new, linked entries (such as reversals), not by editing history.
• Period locks. A locked accounting period refuses further posting — automatic or manual — until an authorized user reopens it, and the reopening itself is audit-logged.

AI autonomy controls

Kraal runs on policy-gated autonomy: low-risk, in-policy work posts automatically — with caps, exclusions, and a receipt for every action — and everything else waits for your approval. The guardrails, in control terms:

• Confidence thresholds. Work posts automatically only when its supporting evidence clears a minimum confidence bar; low-confidence items are routed to review.
• Amount caps and volume limits. Per-entry, per-account, and per-client-per-month dollar caps, plus daily volume limits, bound what automation can do.
• High-risk exclusions. High-risk and judgment-heavy work — tax provisions, equity, revenue recognition, money movement, anything client-facing — always waits for a person, regardless of settings.
• Review by exception. Auto-posted work lands in a dedicated review ledger; your team reviews the exceptions instead of pre-approving the routine.
• One-click reversal. Any auto-posted entry can be reversed in one click, producing a correcting entry with its own audit record.
• Pause controls. Autonomy can be paused per client or across the portfolio at any time; paused work waits for approval instead of disappearing.
• Trust ratchet. Kraal earns more autonomy per work type as its accuracy is proven, and loses it automatically when you correct it.

For the full model, the default limits, and per-client configuration, see Autonomy & Safety.

Availability & operations

Aligned with the SOC 2 Availability criteria.

• Managed cloud infrastructure. Kraal runs on established managed cloud infrastructure rather than self-operated hardware.
• Monitoring and error tracking. Application health and errors are monitored continuously so failures are detected and triaged quickly.
• Backups. Data is backed up automatically through Kraal's managed database provider.
• Your data stays yours. Whatever your billing state, your books remain viewable and exportable, and nothing is deleted. See account lifecycle.

Vendors & subprocessors

Kraal is built on established cloud infrastructure, database, and AI providers with their own published security and compliance programs. A current subprocessor list is available on request at hello@kraal.ai.

Integrations you choose to connect for a client (bank feeds, accounting engines, payroll, e-commerce) are described in Integrations, and their credentials are handled as described under Data security above.

Requesting more detail

For security questionnaires, extended control documentation, or the subprocessor list, email hello@kraal.ai. For how these controls show up in day-to-day product behavior, start with:

• Autonomy & Safety — what posts automatically and what always waits for you
• Audit Center — the client-wide audit timeline
• Admin & Billing — roles, recommended access policies, and billing controls