Inputs and consent.
Workspace records contain your authorized targets, verification status, scan history and findings. Consent records include your user identifier, timestamp, IP address and accepted scope. Test sessions and audit connection credentials are encrypted for worker use.
Secrets and evidence.
Discovered secret values are masked before durable storage, logs or reports. Evidence contains bounded, redacted samples rather than full responses. Evidence objects are encrypted and scheduled for deletion after 30 days; the configured object-store lifecycle and cleanup job must both run.
Finding metadata and consent records are separate from evidence and do not automatically expire at the same time. Source snapshots and test-account credentials must be reviewed as part of the operator’s retention configuration.
External providers.
Hosted deployments use Better Auth, running inside OkToShip with its own isolated database schema, for accounts and sign-in; Stripe or Razorpay for payments; configured S3-compatible storage for evidence; GitHub for authorized repository access; and Claude for redacted explanations and repair prompts. Detection is deterministic. Each provider account must be configured by the operator.
Local preview.
The local demonstration uses a shared fake identity, encrypted local evidence and simulated billing. Entering the demo does not create a real account. Use only synthetic data in this preview.
Before a public release.
This page describes application behavior. The operator must publish its legal identity, privacy notice, support contact and applicable retention and deletion processes before accepting real customer data or live payments.