How to delete your Flagsmith account

About deleting your Flagsmith account

Flagsmith is a robust feature flagging and remote config platform that helps development teams manage feature rollouts, perform A/B testing, and toggle functionality without re-deploying code. By integrating with your application’s backend or frontend, Flagsmith collects identity data and usage metrics to track which feature flags are exposed to specific users.

Users often choose to delete their Flagsmith account due to project completion, transitioning to a self-hosted instance, or auditing data footprints after a service migration. Deleting your account ensures that your organization's configuration history, flag definitions, and linked user identifiers are purged from their cloud environment. Reasons for deletion include:

• Moving from the hosted SaaS version of Flagsmith to a self-hosted installation.
• Simplifying your tech stack after a feature has been permanently rolled out.
• Compliance with strict data minimization policies regarding telemetry and user behavior tracking.

What happens to your data

When you request the deletion of your Flagsmith account, the company processes the removal of your account-level information, including your user profile, authentication logs, and individual API keys. Because Flagsmith handles environment-specific data, you should be aware of the following data categories that are typically processed:

• Personal identity data: Email addresses and profile information used for team access.
• Configuration metadata: Project names, environment definitions, and feature flag states.
• Segment data: Logic sets used to target specific user groups.
• Analytics data: Usage metrics and logs generated during feature flag evaluation.

While Flagsmith removes your primary account access, they may retain metadata for internal billing records or security auditing purposes as required by relevant data protection laws like GDPR or CCPA. Always confirm with the support team if your specific environment data is wiped immediately upon request or if it follows a standard retention period.

Privacy considerations

Using a feature flagging tool like Flagsmith requires trust, as the service acts as a gatekeeper for your application's logic. Privacy-conscious developers should be aware of how user identifiers are passed to Flagsmith's SDKs. If you are concerned about data exposure, consider these privacy steps:

• Use anonymous identifiers: Pass non-PII strings (such as UUIDs) to Flagsmith instead of real emails or names when evaluating flag states.
• Audit SDK logs: Regularly monitor what data is being transmitted from your client-side SDKs to Flagsmith’s servers.
• Limit external integrations: If you link Flagsmith with third-party tools like Google Analytics or Segment, ensure that you understand how that data flows between platforms before deleting your account.
• Review self-hosted options: If your security requirements are extremely high, evaluate whether the open-source self-hosted version of Flagsmith is a better fit than their cloud service.

Frequently Asked Questions

Does deleting my project in the dashboard delete my entire account?

No, deleting a project only removes the specific configuration for that workspace. You must email Flagsmith support to request a full account deletion.

Will my flag evaluations stop working immediately upon deletion?

Once your account and associated API keys are deleted, any application using the Flagsmith SDKs will fail to retrieve flag states, likely defaulting to the fallback values defined in your code.

Can I recover my data after requesting account deletion?

Generally, account deletion is considered permanent to comply with data privacy regulations. Ensure you have exported your flag configurations and project history before requesting removal.

Does Flagsmith share my user data with third parties?

Flagsmith provides the infrastructure to manage feature flags, but they generally act as a data processor. Refer to their latest Privacy Policy for specific details on sub-processors.

Is the self-hosted version of Flagsmith more private than the cloud version?

Yes, the self-hosted version allows you to control the data infrastructure, meaning all telemetry and flag configurations stay entirely within your own cloud or on-premise environment.