# Trust

> Every assurance document for Keryn in one place, and what Keryn does not have yet.

Source: https://keryn.dev/trust/

This page links what a buyer or reviewer usually asks for. It says plainly what exists and what does not. Dates under "Not yet" are plans, not promises.

## Documents

| Document | What it covers |
|---|---|
| [Security](https://keryn.dev/security/) | Reporting a vulnerability to security@keryn.dev, what we commit to, how to verify downloads |
| [Privacy](https://keryn.dev/privacy/) | What Keryn collects, the Keryn Cloud section, how to make a request about your data |
| [Terms](https://keryn.dev/terms/) | The terms of use |
| [Licensing](https://keryn.dev/licensing/) | The licence, including the rule on publishing benchmark results |
| [Sub-processors](https://keryn.dev/subprocessors/) | The providers that process Cloud customer data, their regions, and how changes are announced |
| [Data and retention](https://keryn.dev/docs/cloud/data-and-limits/) | What Keryn Cloud keeps, the 365-day default retention, export, and evidence deletion |
| [Partner terms](https://keryn.dev/partners/terms/) | Terms for resellers and referral partners |

## Backup and recovery

Keryn Cloud's database is backed up every night. Each backup is encrypted before it is stored and a copy is pulled off the host daily. Nightly backups are kept for 30 days, with at least the seven newest copies retained. Backup failures are logged, and a daily check logs an alert if the latest backup is more than 36 hours old. The alerts are log-only. The declared targets are a recovery point of 24 hours and a recovery time of 4 hours for Cloud data. Deletions and revocations are recorded so a restore does not bring them back, and a restore drill runs weekly. The full rebuild has not been timed. Scans you run locally store nothing at Keryn.

## Incidents

Keryn has a written incident response plan with four severity levels, containment switches that exist today, and a rule to notify affected customers. Reports to security@keryn.dev are acknowledged within 3 business days and a serious report within 1 hour on a working day. There is no round-the-clock on-call yet. A scripted incident exercise ran in a test environment on 2026-11-18. The team walkthrough is planned for 2026-12-07.

## What Keryn does not have yet

| Assurance | Status | Plan |
|---|---|---|
| SOC 2 report | **None.** Keryn has no SOC 2 report. | Policy set by 2027-02-28; Type I report by 2027-06-30; Type II observation window 2027-07-01 to 2027-12-31, report by 2028-02-15 |
| ISO 27001 certificate | **None.** Keryn has no ISO 27001 certificate. | No date is set |
| External penetration test | **None.** No independent firm has tested Keryn Cloud yet. | Window 2027-01-12 to 2027-02-13; an internal review comes first |

Keryn's own scans and in-app control mappings are evidence about your code, not a certification, attestation or audit of anything.

## Ask for more

Write to [security@keryn.dev](mailto:security@keryn.dev) to request:

- the **data processing agreement (DPA)**;
- the **security questionnaire answers** (written answers to the usual vendor questionnaire; where a control does not exist the answer says "Not yet").
