KEEPSTATE PUBLIC SECURITY SUMMARY · 2026-09-30
====================================================

This is a public procurement summary, not a certification or a current
production security audit. It supersedes the older preview packs as a
public summary. Historical results do not establish continuing deployment
assurance. The legal documents retain their published commitments.

1. PRODUCT AND STATE BOUNDARY
   KeepState provides hosted agent sessions. A checkpoint preserves guest
   memory, filesystem and device state. External effects, provider-side
   caches and arbitrary client retry behavior are outside that boundary.
   https://keepstate.ai/docs/architecture
   https://keepstate.ai/docs/limits

2. PROVIDER CREDENTIALS AND WORKSPACE SECRETS
   Gateway-managed provider keys remain outside the guest. Secrets a user
   or agent writes into guest memory or workspace can enter a checkpoint.
   Checkpoint secret scanning is not built or offered as a guarantee.
   Hosted inference uses the customer's provider key. Managed inference
   remains planned and is not currently available to purchase.
   https://keepstate.ai/security

3. RETENTION AND DELETION COMMITMENTS
   Retention and deletion policy v1.0 · approved 2026-09-09
  Checkpoint content
    Retained: while the account exists; no automatic expiry
    Deletion commitment: deletable by the customer, per session; the key is destroyed on account deletion
    Backups: encrypted, and unreadable once the key is destroyed; backup retention 30 days
  Provider credentials
    Retained: same as checkpoint content
    Deletion commitment: same as checkpoint content
    Backups: same as checkpoint content
  Ledgers and billing aggregates
    Retained: 7 years, under legal obligation
    Deletion commitment: the identity is tombstoned on deletion
    Backups: not stated in v1.0
  Service logs
    Retained: 30 days
    Deletion commitment: not stated in v1.0
    Backups: not stated in v1.0
  Support tickets
    Retained: 2 years
    Deletion commitment: not stated in v1.0
    Backups: not stated in v1.0
  Console audit log
    Retained: 2 years
    Deletion commitment: the identity is tombstoned on account deletion
    Backups: not stated in v1.0
  Account data
    Retained: while the account exists
    Deletion commitment: deleted on account deletion, except the tombstone id and the billing aggregates already covered above
    Backups: not stated in v1.0
  Telemetry
    Retained: 13 months, then deleted
    Deletion commitment: first-party, cookieless, and carries no identifiers, so there is nothing to tombstone
    Backups: not stated in v1.0
   Legal holds are not currently supported; retention proceeds as stated unless law requires otherwise.

   Material implementation gaps: customer per-session checkpoint deletion
   and automatic expiry are not implemented in the available record.
   Stopping a session does not delete its saved content. The stated policy
   periods remain commitments; current procedural enforcement evidence is
   not available. These gaps do not amend or suspend the commitments.

   Historical account-deletion tests made the tested checkpoint and
   credential backups unreadable under their stated key-custody conditions.
   Separate account keys must remain outside the credential database backup
   set. Independent key copies and later deployments are not certified by
   those tests.

4. CONTROL ASSURANCE AND KNOWN LIMITS
   No SOC 2 or ISO 27001 certification is claimed. A commissioned external
   penetration-test result and a production SLA are not established by the
   reviewed public evidence. Staff access, least privilege, incident response
   and data-return controls need current implementation evidence. Missing
   evidence does not suspend the published no-training or 24-hour breach
   notification commitments.
   Some resumed forked sessions may have unavailable networking. Host-loss
   tests do not establish cross-region disaster recovery or a recovery-time
   guarantee. Read the dated public findings and current service checks.
   https://keepstate.ai/security/threat-model
   https://keepstate.ai/proof
   https://keepstate.ai/status

5. PUBLIC EVIDENCE
   Reviewed summaries retain test dates, actual results, scope and customer
   limitations. Internal source, original transcripts and operational records
   remain private. A public summary has its own digest; it does not inherit a
   signature over a different original document. Matching a digest establishes
   byte identity, not correctness or access permission.
   https://keepstate.ai/evidence

6. LEGAL DOCUMENTS
   Terms          https://keepstate.ai/legal/terms
   Privacy        https://keepstate.ai/legal/privacy
   DPA            https://keepstate.ai/legal/dpa
   Subprocessors  https://keepstate.ai/legal/subprocessors
   Acceptable use https://keepstate.ai/legal/acceptable-use

Questions: security@keepstate.ai · https://keepstate.ai/contact