Use AI and stay compliant
You ask: How can we use AI and stay compliant?
You want to use AI and stay within the rules, with the data of the people you serve protected.
B Team produces the records your compliance needs as you work. The duty stays with your organisation, and this page is not legal advice. B Team does not make you compliant, and it holds no certificate yet. It makes five records, and each is shown as built or not built.
Today the base is measured and most of the records are planned. Security is built in from the start, and its state is shown. The boxes below list what is not met.
How it answers
- Who asked for what, and who approved it. Today triage and a person's approval. Not built: a record for each change (claim 62). Measured, with a recorded deviation Record not built
- Which AI produced each output. Today every model call is recorded. Not built: the model, provider and version on each change (claim 63). Measured Link not built
- Who checked it. Today a separate reviewer who cannot change the work. Not built: its findings kept with the change (claim 62). Measured (pair runs) Findings not built
- Which providers may see which data. Today the model of each role is a setting. Not built: a data policy for each project (claims 28 and 54). Measured Policy not built
- A record nobody can quietly change. Today nothing. Not built: a log that shows any change to it (claim 27). Planned, not built
- A compliance reviewer on every change. Its first rules are the GDPR and the AI Act. A rule is added only once it is written down with its article. Planned, not built
Reliability on this page
The "traced" leg is the base of the records: every model call is recorded and you can read who said what to whom (claims 8 and 9). Traces hold full words by default, so they are a risk to your data as well as a record (claim 25). How we raise reliability
The honest limit
- Secrets sit in plain, git-ignored files, and traces hold full words by default (issues #51, #84).
- No data policy is checked against any provider's terms (issue #57). Prompts go to Anthropic and sit in plain text in the workflow service's history. Today's deviation: every decided role runs on Anthropic (issue #82), which is the engine's own setting and not a client's.
- There is no audit log, and no secret scanning in the build pipeline (issues #56, #116). Code that agents run has no sandbox (issue #176).
- One provider key and one bill serve all projects (issues #170, #171). The web page has no sign-in (issue #113).
- There is no record of each change, no model link on it, no evidence pack and no supplier package (claims 62 to 65). There is no processing agreement template, and B Team holds no certificate (claims 66 and 67).
For NGOs
The personal data of the people you serve, the GDPR, the AI Act, and the confidence of your board and funders. This site makes no claim of compliance: the duty stays with your organisation, and no list of rules written for B Team exists yet to be compliant with.
A compliance reviewer on every change
The compliance reviewer is the fifth standard reviewer, next to security, documentation, done-when and architecture. Its first rules are the GDPR and the AI Act. A rule is added only once it is written down with its article, so the reviewer never works from memory. Planned, not built (compliance reviewer, C10; issue #107)
The rules in view (not legal advice)
"Read" means the research report on issue #280 read the text itself on 2026-10-13. "Tool summary" means a fetch tool reworded the page. Anything left unread is not used here. Where a rule's reach on B Team is the report's own reading, it says so, and a lawyer must confirm it. The rules are listed for an NGO first.
The GDPR (in Dutch, the AVG), Regulation (EU) 2016/679
It binds your organisation as the controller of personal data. It comes first for you.
- B Team is a processor when it can process your personal data for you, for example by hosting or by support access. Then Article 28 needs a written contract: acting only on your documented instructions, staff confidentiality, security measures, rules for sub-processors, help with requests and breach notices, deletion or return at the end, and information for audits (read).
- If you run B Team in your own account and B Team has no access to your data, it is probably not a processor. That is the report's inference from the European Data Protection Board's examples (read), not a finding. A lawyer must confirm it.
- A processor that decides for itself why and how to use your data is treated as a controller (Article 28(10), read). So B Team plans to sign a processing agreement before it can see personal data, never to use your prompts, issues or feedback for its own purposes, and to keep its own access to your data off by default, time-limited and logged. Planned, not built (processing agreement, C1; no own use, C2; access off by default, C3)
- You decide which AI providers may see your data. A change of sub-processor needs your authorisation (Article 28(2), read). A transfer outside the EU needs an adequacy decision or standard clauses (Articles 44 to 46, read). A lawyer must say how far to rely on the adequacy decision for the United States. B Team plans the data policy and European models first. Planned, not built (data policy, S12; providers and transfers, C4)
- A data protection impact assessment is yours to decide. B Team plans to give you the facts about its data flows to paste into one. Planned, not built (impact assessment support, C5)
The EU AI Act, Regulation (EU) 2024/1689
- B Team is an AI system in the Act's sense. A tool that writes software is not in the Act's list of high-risk areas (Annex III, read), so B Team is most likely minimal risk. That is the report's reading. A lawyer must confirm it.
- AI literacy applies now (Article 4, read). B Team plans short training material on what the agents can and cannot do. Planned, not built (AI literacy material, C9)
- Marking AI output (Article 50(2), read): whether code counts as text, and whether agents are exempt, is a question for a lawyer. The record of which AI produced each output is the raw material. Planned, not built (model provenance, C7)
- Software the agents build could itself be high-risk, for example a system a public authority uses to judge eligibility for public benefits (Annex III, read). Then your organisation, not B Team, is the provider of that system. B Team plans to flag such builds for human oversight. Planned, not built (human oversight, C8)
For NGOs
- The Dutch charity recognition scheme, norm 3.5.1, asks a recognised charity for a current policy on privacy and information security with organisational and technical measures (read). B Team plans a one-page answer for charities. Planned, not built (supplier package, C21)
- The ANBI publication duties (tool summary) say nothing about software.
- Standard agents are planned not to build features that profile individual donors without a named responsible person and an impact assessment first. Planned, not built (no donor profiling by default, C6)
Rules that bind B Team as the maker (Dimero BV)
- Cyber Resilience Act: software installed in your own account counts as a product, so B Team probably owes a software bill of materials, a public vulnerability policy and five years of support. A lawyer must confirm that B Team is a product. B Team's own pinned versions and bill of materials are measured. Measured (lockfile, bill) The public policy and the reporting desk are not built. Planned, not built
- Product Liability Directive: software is a product, and no contract can limit it towards an injured person (read). The exposure is software the agents build that other people use. Insurance and recourse are for a lawyer.
- Data Act: only if B Team hosts. From 12 January 2027 a hosting provider may not charge for switching (read). The hosted service is an intention only.
- Copyright of what agents write: unsettled, so this site promises no ownership until a lawyer has answered.
For public bodies, later
- NIS2 and the Dutch Cyberbeveiligingswet: an organisation in scope must look at its suppliers' secure development and vulnerability handling (NIS2 Article 21, read). It will ask B Team those questions. The supplier package answers them. Planned, not built
- Accessibility: public sector bodies must make websites and apps accessible. The standard is EN 301 549 version 3.2.1, which rests on WCAG 2.1 level AA (tool summary). B Team's own screens are not tested for it. Planned, not built (accessibility, C26 and C27)
Organisations that hold ISO standards
B Team supports your controls with records and a supplier package. It does not make you certified. If your organisation holds ISO/IEC 27001, 27701, 42001 or ISO 9001, your auditor asks for records and for evidence about your suppliers. B Team's records and package are meant to be that evidence. A certificate of B Team's own would not make you certified either.
| Standard | What it is for | The theme B Team supports | State |
|---|---|---|---|
| ISO/IEC 27001 (and 27002) | Information security | Change records, logs, supplier evidence | 8 Measured 27, 62, 65 Not built |
| ISO/IEC 27701 | Privacy information | Where personal data went; sub-processors | 28, 66 Not built |
| ISO/IEC 42001 | AI management system | Which AI is used and by whom; oversight | 8, 13 Measured 63 Not built |
| ISO 9001 | Quality management | Change and review records as quality records | 62 Not built |
- No clause of any ISO standard was read: iso.org refused the research tool and the texts are paid. So this site says "supports the theme of", and never "meets clause X".
- No ISO standard is a legal duty of the maker. An ISO/IEC 42001 certificate would not prove AI Act compliance.
B Team itself holds no certificate yet
Its assurance comes in stages: a self-assessment, then an independent penetration test, then an independent audit report or an ISO/IEC 27001 certificate scoped to development and support. The plan, the cost and the dates are not decided. Planned, not built (independent assurance in stages, C29; claim 67) The site says what independent proof B Team holds today, which is none.
Who to call, and whether you can leave
- Who to call when something breaks: there is no published contact yet, no vulnerability policy and no reporting desk. Planned, not built (vulnerability policy, contact and support period, C12 to C14)
- Can we leave? The aim is that you can leave with everything, with no charge. Planned, not built (exit, C23)
- Logs: kept for six months by default, once built. Planned, not built (log retention, C19)
- Price and term: each offer is meant to state the total price, the term and the exit. Planned, not built (procurement-ready offer, C28)
The technical detail
The claims behind this page, with their states as the evidence page records them.
| No. | Claim | State | What it serves | Check or issue |
|---|---|---|---|---|
| 8 | Every model call is recorded: project, role, model, tokens, cost. | Measured | Every call traced (F6) | trace_checks |
| 9 | You can read who said what to whom in the team. | Measured | Full team tracing (F18) | team_trace_checks (6 of 6); #84, #159 |
| 10 | A separate reviewer checks work before you see it. Nobody has shown that a reviewer catches a real fault. | Measured (pair runs) | Independent review (F13) | reviewed_checks; #28 |
| 13 | Nothing is published or merged without a person. No self-approval. The recorded deviation: whoever holds a project's key (Temporal token) to the engine's workflow service can send a decision under any name. | Measured, with a recorded deviation | Human approval (F9, S9) | inbox_checks; #32 |
| 17 | New work is triaged before anything starts. | Measured | Mailboxes, triage first (F4) | mailbox_checks (40); 1 real item |
| 19 | Text from outside the team is data, never orders. | Measured | Outside text is data (S8, S14) | injection_checks (9 attacks) |
| 22 | Agents hold only needed tools. A worker has no write key. | Measured (in part) | Least agency (S2, N4) | reader_write_checks |
| 23 | Agents reach only the network a role is allowed. | Measured | Network denied by default (S7) | egress_checks +3; #245, #174 |
| 24 | Each project has its own credentials. Measured for workflow tokens; one provider key is shared. | Measured (tokens) | Least-privilege identities (S3) | temporal_auth_checks; one provider key shared (#170, #171) |
| 25 | Secrets stay out of prompts, traces and logs. | Not built (not met) | Secrets (S5) | #51, #84, #57 |
| 27 | A full, tamper-evident audit log. | Not built | Audit log (S11), tamper-evident log (C17) | #56 |
| 28 | A data policy says which provider may see a project's data. | Not built | Data policy per project (S12), providers and transfers (C4) | #57 |
| 54 | You may pick only models your data policy allows that passed the test set. | Not built | Model choice bounded (S21) | #294 |
| 62 | Each change has a record: diff, test result, findings, risk note with rollback, approver, time. | Not built | Change record (C16) | #307 |
| 63 | Each change records which model, provider and version wrote or reviewed it, and the agent role. | Not built | Model provenance (C7) | #302 |
| 64 | You can export an evidence pack for a period, in open formats. | Not built | Evidence pack (C18) | #307 |
| 65 | A package for your buyer or auditor, from live data: suppliers, data flows, exit plan. | Not built | Supplier package (C21) | #309 |
| 66 | A processing agreement before B Team sees personal data. No own use. Its access off by default. | Not built | Processing agreement (C1), no own use (C2), access off by default (C3) | #297, #300 |
| 67 | Independent assurance for B Team in stages, with dates. B Team holds no certificate today. | Not built | Independent assurance in stages (C29) | Waits for a decision by the founder (Codrin). #306 |
The other four questions
-
Question 1
Build what actually matters
Start from your goal. End with real users. Judge by use.
Read the answer -
Question 2
Choose your models, keep your freedom
You choose your models and where they run.
Read the answer -
Question 3
People and AI, building together
Agents write. People decide, guide and check.
Read the answer -
Question 5
Fit your people and your budget
Work follows your rhythm. Much of it runs in batches.
Read the answer
Tell us you are interested
B Team is not offered to anyone yet. NGOs come first. If you want to hear when that changes, or you would like to be one of our first pilots, write to us.
Write to: [contact address to be decided]
This draft has no form and collects no data. Once there is an address, what happens next is meant to be this: we tell you whether we can work with your organisation yet. We promise no date and no price.