Data deletion instructions
Strict keeps local deployments entirely on your own disk, and lets you remove Cloud Monitoring credentials or workspaces at any time.
1. Delete local Standalone & agent data
- Stop and remove host runner agents via
bash ~/.strict/agent/remove.sh(orstrict remove) on enrolled Macs and Linux machines. - Uninstall the Standalone server service via
bun run standalone:uninstall(or remove itslaunchd/systemd --userunit). - Delete
${STRICT_DATA_DIR}/state.json(and optional local Tailnet cache directory) to erase all local host history and tokens.
2. Revoke Cloud Monitoring integrations & OAuth grants
- Tailscale & Webhooks: Open Workspace Settings in the Strict console and clear or rotate Tailscale API credentials and webhook URLs (deleted immediately from workspace storage).
- GitHub: Open GitHub Settings → Applications → Authorized OAuth Apps (and repository/org Runners settings) to revoke Strict and deregister self-hosted runners.
- Google / Apple Sign-In: Remove Strict from your Google Account Connections or Apple Account Sign in with Apple settings.
3. Request full Cloud Monitoring workspace deletion
Email privacy@strict.ai from your workspace owner email address with the subject "Data deletion request" and include your workspace ID or email address. Verified requests delete workspace Durable Object state, D1 membership records, and audit entries within 30 days.