Strict Privacy
LegalEffective November 21, 2026

Privacy Policy

Strict is designed around a zero-account local architecture. When you run Standalone mode on your own hardware, fleet telemetry never leaves your tailnet or local disk.

1. Standalone Mode vs. Optional Cloud Monitoring

  • Local Standalone (default): Runs standalone.ts locally (typically behind tailscale serve) and stores host state atomically on your machine at ${STRICT_DATA_DIR}/state.json. Strict does not collect analytics, host metrics, or GitHub repository metadata from Standalone deployments.
  • Optional Cloud Monitoring: If you explicitly opt into hosted monitoring on strict.ai, workspace state is stored inside an isolated per-workspace Cloudflare Durable Object (WorkspaceState) and workspace membership metadata is stored in Cloudflare D1.

2. Source Code, Builds & GitHub Secrets

Strict never proxies GitHub Actions workflows through third-party build servers. Official actions/runner workers execute directly on your Mac or Linux hosts over outbound HTTPS to GitHub, so repository source code, build artifacts, and GitHub Actions secrets stay strictly on your own machines.

3. Data Collected in Optional Cloud Monitoring

CategoryWhat Strict stores when opted in
Identity & MembershipEmail address, display name, workspace role (owner, admin, member), and OAuth subject identifiers when signing in via GitHub, Google, Apple, or email magic links.
Host TelemetryHost label, OS/arch, CPU/RAM/disk metrics, reclaimable cache estimates, runner slot statuses, preflight strict doctor pass/warn/fail results, and 12 toolchain versions.
Encrypted CredentialsOptional Tailscale OAuth/API secrets and Slack/Discord/generic alert webhook URLs are encrypted at rest with AES-256-GCM (v1.*) before persistence and never returned to browsers.
Agent Tokens & Audit LogsHost tokens (str_v1_...) are stored exclusively as SHA-256 hashes; administrative mutations record audit entries visible to workspace admins.

4. Cookies, Tracking & Email

Cloud Monitoring uses a single HttpOnly HS256 JWT session cookie (strict_session) for authentication. Strict does not use third-party advertising trackers, behavioral analytics scripts, or data brokers. Alert and sign-in emails are dispatched from noreply@strict.ai via Cloudflare Email Sending.

5. Retention, Deletion & Contact

Standalone data lives solely in your local ${STRICT_DATA_DIR}/state.json and is deleted whenever you remove that file. For Cloud Monitoring workspaces, you can revoke credentials in settings or request full erasure by emailing privacy@strict.ai (completed within 30 days). See Data deletion instructions.