Privacy notice

Account and workspace information

We store the name, email address, and profile image that you provide or receive through your chosen sign-in provider.

We store workspace memberships, roles, invitations, and setup preferences. If you register a passkey, we store its public credential and device information.

Toggld does not receive your device PIN or biometric template when you use a passkey.

Flag and evaluation information

We store the flags, variant values, targeting rules, segments, and identifiers that workspace members submit.

Evaluation requests contain the context that your application sends. The evaluation engine uses that context to choose a result.

Evaluation collectors store aggregated counts by flag, environment, variant, reason, and time bucket. These counts do not contain the full evaluation context.

Segment membership and targeting rules can contain personal identifiers if you put them there. Send only the attributes that your rules need.

Security and operational records

Session records can include IP addresses, browser information, and sign-in times. Cookies maintain your session and selected preferences.

Audit events record the actor, action, affected resource, and saved changes. Saved changes can include personal data that you place in workspace content.

Request logs, rate-limit counters, and dependency status records help us investigate faults and limit abuse.

This application does not include advertising cookies or cross-site advertising trackers.

Why we process these records

We use account records to authenticate you, authorize workspace access, and send requested sign-in links, invitations, and service messages.

We use flag content and evaluation context to operate the feature flag service. We use evaluation counts to show activity and diagnose errors.

We use security and operational records to protect accounts, enforce limits, investigate incidents, and maintain the service.

Who receives information

Workspace members can access content according to their roles. Owners and administrators can manage members. Members, administrators, and owners can manage SDK credentials.

Hosting, database, email, and backup providers process data to deliver the service. The deployed application uses Cloudflare Workers and its configured storage services.

If you choose GitHub sign-in, GitHub processes the authentication exchange under its own privacy notice.

Information can also be disclosed when a valid legal requirement applies or when needed to investigate abuse and protect the service.

Retention and deletion

Account and workspace data remains until you remove it or the service operator removes it.

Evaluation summaries use a configurable retention period, with a default of 30 days. Scheduled cleanup removes expired records, subject to deployment timing and backlog.

Operational logs and encrypted backups follow the retention of their deployed storage. Account deletion does not immediately erase existing backup copies.

Deleting your account removes your identity, sign-in methods, sessions, and memberships. It does not delete shared workspace flags or historical audit events.

If you own a shared workspace, transfer ownership and step down before deleting your account. You can delete an empty workspace when you are its only member.

Workspace deletion removes its environments, SDK credentials, invitations, and workspace history. An operational audit event records the deletion.

Your account controls

Open Account and security to download your personal account data, manage sessions and passkeys, or delete your account.

Account controls require a valid sign-in. Account deletion also requires confirmation through your account email. If you cannot sign in, use the recovery instructions on the sign-in page.

You can remove local cookies through your browser. This signs you out and resets preferences stored in those cookies.

Your legal rights depend on where you live. These controls do not limit rights that applicable law gives you.

Changes and questions

We update this notice when service practices change and show the effective date above. Review the current notice before you submit new sensitive data.

Use the private controls in your account for personal data actions. The documentation describes supported workflows.

If you cannot use your account controls, contact support@toggld.io. Do not send credentials or private workspace content.

Keep personal data, session cookies, API keys, and private flag content out of public channels.