Guardyx AI is infrastructure that sits in the path of real actions.

Encrypted in transit and at rest. All traffic uses TLS 1.2 or higher. Data is encrypted at rest with AWS KMS, and credentials get a second layer of application-level encryption (AES-128-CBC + HMAC) with keys held in AWS Secrets Manager — never in code. Agent authentication secrets are stored as one-way SHA-256 hashes, not encrypted. Encryption keys support staged rotation with no downtime.

You set the window; the schema enforces it. Every workspace has an explicit governance-evidence retention period — indefinite retention isn't an option. The default is 730 days, which is also the ceiling: a workspace can shorten its window, never extend it. Database-level constraints mean a misconfiguration can't silently destroy your trail. Workspaces that self-declare as high-risk AI deployers get a 183-day floor, matching EU AI Act Article 26(6). Searchable audit history is a separate plan entitlement: 7 days on Free, 90 days on paid plans, and longer for Enterprise as agreed, within the evidence retention window. Expiration of searchable history does not itself delete stored evidence, and a longer history entitlement cannot restore deleted records. The Terms specify a 90-day storage minimum unless an Order Form or DPA provides otherwise; shorter configured windows must be consistent with that agreement and applicable minimums. Retention is two-tier: keep governance evidence for years while scrubbing tool-call content on a shorter clock. Every purge is attested by a retained, hash-chained record — and a purge aborts entirely if audit-chain verification fails, so cleanup can never destroy evidence of tampering.

Every record is scoped to your workspace at the row level, and every query and export is filtered to the calling workspace. Administrative endpoints are role-gated. Guardyx AI records the tool calls your agents make, including call arguments and results — that's the evidence the product exists to produce — and you control how long that content is kept independently of the surrounding audit metadata.

Your audit trail is tamper-evident. Every governance event is linked into a per-workspace SHA-256 hash chain, so any after-the-fact modification is detectable at the exact record. Verification runs on demand and its result is embedded in every evidence pack you export.