Designed for sensitive evidence, not casual screenshots.
AuditFetch treats evidence as sensitive security data. The local runtime is designed around least privilege, local credential storage, audit logs, artifact hashing, and explicit user-controlled exports.
How we handle your data
Local-first, customer-controlled
Your Local installation stores evidence, credentials and audit history. You control exports and optional synchronization. Licensing, update checks, external AI and support have separate data flows. Review the Local operating guide before enabling them.
Least-privilege, read-only access
Connector credentials are scoped and read-only, and every collector method is validated read-only before it ships. AuditFetch never writes to your systems.
Tenant-isolated storage
Database row-level security isolates every tenant, enforced in the database itself rather than in application code, alongside role-based access control. Connector credentials are encrypted at rest under a key only you hold.
Evidence integrity with clear limits
Stored artifacts have content hashes. Packet generation checks payload bytes against those hashes. A hash can detect changed bytes when compared with a trusted value; it does not prove source accuracy or control effectiveness. Packet exports do not carry an independent Ed25519 signature for each artifact.
Optional external audit checkpoints
External audit-log anchoring requires a configured signing secret, an Object Lock storage bucket and a running worker. Without that configuration, do not assume an external immutable checkpoint exists. The checkpoint uses HMAC-SHA256 and requires the configured secret to verify; it is separate from an artifact signature.
Local audit log
An append-only, hash-chained record of collection, review, and export actions, plus evidence redaction support and customer-owned deletion controls.
Approved browser playbooks
Only declarative, approved routes with an outbound host allowlist. No free-form browser roaming. Navigation trail and redaction rules are recorded with the evidence.
Our trust boundary
Local-first, always
With AuditFetch Local, evidence and credentials stay in your environment by default. You control exports and synchronization to other systems.
Read-only, always
Never writes, remediates, or changes access to your systems.
Collect configuration evidence
Use supported configuration and access records. Do not upload patient data or secrets. Review source scope and redaction before collection.
Traceable evidence
See where evidence came from and when it was collected, with integrity checks and an audit log.
- Never your card data — payments run through Stripe; we store no card numbers.
- AI is non-authoritative — it assists, humans decide, and AuditFetch never certifies compliance.
- Optional telemetry, off by default — product-usage telemetry is optional.
- Customer-controlled exports — with AuditFetch Local, evidence stays in your environment unless you choose to export or synchronize it to another system.
Check the operating requirements
Self-hosting includes responsibility for host security, backups, restore tests, storage and updates. Source access records can contain personal information. Check collection scope and redaction; do not assume that every source or upload is free of sensitive data.
Ready to stop chasing audit screenshots?
See AuditFetch pricing and get started with local-first evidence automation for SOC 2, HIPAA, and ISO 27001.