Privacy Policy

Account data: your email address (used for login codes and, if you opt in, notification delivery) and a theme preference. There are no passwords — login is by one-time code.

Workspace content: the configuration values, database structure, API definitions, validation rules, branches, comments, and audit history you and your team create. Secret values are encrypted at rest (AES-256-GCM) and masked in the interface by default.

Billing data: plan state, usage counts, and (for legacy paid workspaces) invoice history per workspace. Custom-inquiry details you submit (name, work email, company, and what you describe) are stored and emailed to our team only to respond to you. If you added a card under a legacy plan we store only the last four digits and the card brand — never the full number.

Operational data: IP addresses are used transiently for rate limiting; login codes are stored hashed with attempt counters and expire within minutes.

Operating the product: authenticating you, delivering notifications you opted into (email/webhook), enforcing workspace permissions and plan limits, showing audit history to your workspace, and computing your bill. We do not sell personal data, run third-party advertising, or use your workspace content for anything other than serving it back to your workspace.

Access inside a workspace follows its permission model: members see only services they've been granted visibility on; secret values are masked outside export; billing is Owner/Admin-only. Our operators access customer data only to run the service, investigate abuse, or comply with law.

Workspace data lives until you delete it: archiving hides a workspace immediately and reversibly; after 30 days archived workspaces become eligible for permanent deletion (purge), which irreversibly removes all content, membership, billing, and audit records. Expired login codes and refresh tokens are pruned automatically. You can export everything first via workspace takeout. For account-level deletion requests, use the contact page.

Secrets encrypted at rest; TLS in transit; login codes hashed with attempt limits and per-IP rate limiting; refresh-token rotation with theft detection; scoped, revocable CI tokens stored only as hashes; server-side permission enforcement on every route. Report vulnerabilities via the contact page — we'd rather hear it from you than read about it.

Material changes to this policy are announced by email at least 14 days in advance. Questions and data requests: contact page. See also the Terms of Service.