Skip to content

Security & trust

You are handing us your application. Here is exactly what we do with it.

ReadyForUsers is designed so that the worst case, a full compromise of our systems, still cannot charge your customers or delete your data. Every claim below is either true today or marked ROADMAP.

or email hello@readyforusers.com (open in your mail app)
Tenant isolation

Every workspace is separated by row-level security, and each run executes in its own short-lived machine. Nothing about your application is used to serve another customer.

  • Row-level security on every tenant table
  • One isolated machine per run
  • No cross-customer model training
  • Per-tenant encryption keys ROADMAP
Environment controls

Classification happens before permission. An unclassified host is treated as production, and production is observation-only by default.

  • Automatic environment detection
  • Typed hostname confirmation
  • Owner or Admin required
Encrypted secrets

The read-only connection string you give us is encrypted at rest, decrypted only for the run, and never displayed again after entry.

  • AES-256-GCM at rest
  • Write-only in the UI
  • Managed key vault ROADMAP
Production protection

Mass creation, destructive fuzzing, live purchasing and heavy load are structurally blocked on production, not merely discouraged by policy.

  • Enforced in the executor
  • Sandbox payment keys only
  • Concurrency hard-capped
Model-data boundaries

Your evidence is never used to train a model, ours or a provider's.

  • No training on your data
  • Zero-retention provider terms ROADMAP
  • Published model-provider list ROADMAP
Evidence storage

Recordings, screenshots, network captures and snapshots are stored per run in a private bucket and are addressable only through your workspace.

  • Signed short-lived URLs
  • No public buckets
  • Region pinned per workspace ROADMAP
  • Per-incident deletion ROADMAP
Data retention

There are no self-serve retention settings yet. Ask us and we erase a run or a whole workspace for you.

  • Erasure on request
  • Per-class retention windows ROADMAP
Deletion

On request, we erase a workspace's run data: its database rows and its stored evidence. Email hello@readyforusers.com and we confirm by email when it is done.

  • Erasure of rows and stored evidence
  • Immediate self-serve deletion ROADMAP
  • Provider-side cache purge ROADMAP
Audit logs

Runs, billing changes and owner actions are recorded on a hash-chained log with the acting user, so tampering is detectable. A copy is available on request.

  • Hash-chained, append-only log
  • Retained for the workspace life
  • Self-serve export as JSON or CSV ROADMAP

The hard boundary

Production is observation-only until you say otherwise, in writing.

Environment classification happens before any action is permitted, and it defaults to the most restrictive reading. An unclassified host is treated as production. Enabling destructive testing on production requires an Owner or Admin, a typed confirmation of the hostname, and it is written to the audit log with that person's name attached, permanently.

Cannot charge

Live payment keys are rejected by the executor even if present in your configuration.

Cannot delete

Destructive verbs are unavailable on production regardless of the credentials supplied.

Cannot overwhelm

Concurrency on production is capped far below your capacity and is not configurable upward.

Planned retention defaults ROADMAP

Session video7 days
Screenshots30 days
Network & logs30 days
Incidents & findings1 year
Audit logWorkspace life

Retention settings are not built yet. Today, ask us at hello@readyforusers.com and we erase a run or a whole workspace for you.

What we will not claim

ReadyForUsers is not a penetration test and not a compliance certification. It finds failures a realistic population would cause. Anything else on this page you can verify: ask for the report.

Engineers ask

Do I have to give you a production database or a clone of it?

No. For the guided pass we run a copy of your app with its own seeded database, built from your repository or a container image. We never ask for production data.

Can the witness modify my data?

No. It only issues reads, against the seeded database of the copy we run. When direct staging runs ship, use a read-only database role so your database enforces it as well.

How do you reset state after a collision?

The copy of your app and its seeded database are thrown away after the run, so there is nothing to reset. Your own staging is not touched.

Do synthetic users act as my real users?

No. Each run creates its own test identities with separate sessions.

What if the evidence is incomplete?

The verdict is UNVERIFIABLE. We never present a model's opinion as a fact about your database. Invented evidence is always zero, and the receipt says so.

What happens to my connection string?

You do not need to give us one for the guided pass. If you do, it is encrypted at rest, never logged, never shown to a model or an actor, and you can revoke it any time. It is only used once direct staging runs ship.

Where does a run execute and what can it reach?

The guided pass runs on infrastructure we control, against the copy of your app, and the copy is thrown away afterwards. Our hosted runs (today, our own demo apps) use a dedicated machine with deny-by-default egress that is destroyed when the run ends; hosted runs for your app are on the roadmap.