DevelopmentFlagsmith and the GDPR: agreement, role and data location.
Flagsmith is a development tool. Its role depends on the activity, it publishes its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Development
- Usual role
- Depends on the activity
- Data location
- Set per account or project
- Agreement
- Published by the vendor
What does Flagsmith do with personal data?
Manage source code, software development and deployment workflows. That is how Privacyboard describes a typical use of Flagsmith, as a starting point you can edit.
The data usually involved: names, Email addresses, contribution metadata, information included in repositories, issues
Is Flagsmith a processor or a controller?
the appendix also describes Flagsmith as a data controller for customer personal data.
Privacyboard does not prefill a role for this vendor on purpose. You are asked to choose, since the answer changes what your privacy policy says and which agreement matters.
Where does Flagsmith store personal data?
Flagsmith does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable.
How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Which legal basis usually applies to Flagsmith?
For the usual use of Flagsmith, companies most often rely on legitimate interests (GDPR Article 6(1)). Source code and deployment tools are needed to build and run the product.
The interest you would state: “Building, testing and deploying our software efficiently and securely.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
The balancing test is yours to do: the interest must be real, the processing necessary for it, and people’s rights must not outweigh it.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Sources: GDPR Article 6, lawfulness of processing, EDPB Guidelines 1/2024 on legitimate interest
Does Flagsmith have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
Yes. Flagsmith publishes the text of its data processing agreement on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep.
What we noted when we opened the page: Terms of Service updated Sep 2026 with a Data Processor Appendix. Contracting entity Bullet Train Limited t/a Flagsmith (London). Appendix says no transfer outside the EEA, while a DORA annex lists app data replicated in 8 AWS regions incl. US.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Read the Flagsmith agreementHow to declare Flagsmith
- 1
In your privacy policy
Name Flagsmith as a recipient, say what it is used for (manage source code, software development and deployment workflows) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Flagsmith with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Flagsmith to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Flagsmith
- Keep secrets and customer data out of repositories and issues.
- Review who has access and how departures are handled.
- Check the retention of issues, logs and deleted repositories.
- Record the provider where personal data is processed through it.
Go online for free. Grow when you need to.
Free puts you online. Pro adds requests, domains and your team; Business, your brand only.
Free
$0 forever
No card, no time limit
For getting compliant and going online on your own.
Start for freeKey features:
- Privacy and cookie policies
- Vendor and processing registers
- Requests and breaches tracked
- Impact assessment screening
- Privacy center on privacyboard.io
- Cookie banner on 1 domain
- 1 person
No card needed
ProRecommended
$32 per month
Billed $384 a year Save $84
For taking requests, covering all your sites and working as a team.
Start with ProEverything in Free, plus:
- DPA for your clients
- PDF and Excel exports
- Email reminders
- Request form and replies
- Your own domain
- Banner on 3 domains, every choice logged
- Weekly site scan
- Complete DPIAs and TIAs
- AI assistant connector
- Up to 5 people, with roles
Cancel any time
Business
$109 per month
Billed $1,308 a year Save $240
For proving it to customers and auditors, under your brand only.
Start with BusinessEverything in Pro, plus:
- No Privacyboard mention
- Security section and vendor alerts
- Evidence pack in one click
- Banner on 10 domains, daily scan
- Up to 50 people
- Two-step verification required
- Activity log kept 3 years
Bank transfer on request
Questions, answered.
Is Flagsmith GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Flagsmith is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it publishes a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Flagsmith have a DPA?
Yes. Flagsmith publishes the text of its data processing agreement on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep. You can read it at https://flagsmith.com/legal/tos.
Is Flagsmith a data processor?
It depends on the activity. the appendix also describes Flagsmith as a data controller for customer personal data.
Which legal basis applies when I use Flagsmith?
For the usual use of Flagsmith, companies most often rely on legitimate interests (GDPR Article 6(1)). Source code and deployment tools are needed to build and run the product. The interest you would state: “Building, testing and deploying our software efficiently and securely.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Where does Flagsmith store data?
Flagsmith does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable. How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
Do I need to mention Flagsmith in my privacy policy?
Yes, if Flagsmith handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Flagsmith to my vendor list?
In Privacyboard, pick Flagsmith from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Similar tools
Privacyboard is not affiliated with Flagsmith. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.