PRIVACY MODEL

Private by design.

This page describes implemented service behavior. It is a draft and must be reviewed by qualified counsel before a public commercial launch.

Account and sign-inWhen passwordless sign-in is configured, StoreReady stores the verified account email and sends the supplied address plus a one-time sign-in link through its configured email provider (Resend when selected by the operator). The link token is random, expires after 15 minutes, is single-use, and only its SHA-256 hash is stored. After verification, an API key is returned once and held only in the current page session; API-key hashes, not plaintext keys, are stored.
Source inputsSource ZIPs, GitHub repository snapshots and QA session files are temporary audit inputs. They are deleted after audit completion by default unless the operator explicitly enables upload retention.
GitHub accessStoreReady stores non-secret GitHub App installation metadata and audit provenance such as repository, requested ref and resolved commit SHA. GitHub user access tokens and installation tokens are not persisted. A temporary user token used to verify an installation is explicitly revoked after verification.
Reports and billingAudit reports, source provenance, payment/order and entitlement records, account email and subscription metadata persist so customers can use paid features and retrieve report history. Dodo Payments handles checkout when configured; payment data handling is subject to its terms and privacy materials.
Scanners and AISecurity tools execute behind the private StoreReady service. Operators must disclose any scanner configuration that sends vulnerability metadata externally. StoreReady does not intentionally send customer source to third-party AI.
Retention and deletionTemporary source is deleted automatically by default. Production operators must define backup, account/report/connection deletion, legally required retention, support and processor procedures. This page does not promise a self-service account deletion feature.