Privacy notice
Last updated 16 July 2026.
This notice explains what personal data Good Conversations About AI collects, why, who can see it, where it's held, how long we keep it, and the rights you have. It's written in plain English on purpose. For the plain-language detail on how a session works in practice, see the security & privacy page.
Who is responsible for your data
Good Conversations About AI is operated by Enlighten Training & Consultancy Ltd, trading as EnlightenWorks (“we”, “us”), a company registered in England & Wales. Enlighten Training & Consultancy Ltd is the data controller for the personal data described here.
Questions, or want to exercise a right below? Email ellie.pyemont@enlightentraining.org.
What we collect, and why
If you create sessions (a host/facilitator). Your email address and a display name, so you can sign in and own your sessions. Our lawful basis is performance of our contract with you (providing the service).
If you join a session (a participant). A display name and optional role that you choose, and the reflections, votes and notes you add. There is no participant account, email or password. Our lawful basis is our legitimate interest in running a facilitated team conversation that the host has invited you to.
Session context. Light context the host enters about the team — sector, country, size, operating system, existing tools — to ground the conversation.
Product analytics. We use PostHog to understand how the tool is used, so we can keep it working and improve it. If you host sessions, your account id and email address are sent with these events, so that when you contact us for support we can find your account and see what happened. Also recorded are the pages you visit and technical event data such as browser and screen size. Join codes and session ids are stripped out before anything is sent, so analytics cannot be tied back to a particular team's session. Analytics are off until you accept them: nothing loads and no cookie is set unless you do, and declining does not affect how the tool works. Our lawful basis is your consent, which you can withdraw at any time using the control below.
Error logs. We use Sentry to capture errors so we can fix them. An error report includes the technical detail of the fault and the address of the page it happened on, with join codes removed. An error raised on our server may also carry the internal id of the session being worked on, so we can trace what went wrong. We do not send your name or email address to Sentry, and we do not record your screen or replay your session. Our lawful basis is our legitimate interest in keeping the service working.
Payments. Good Conversations About AI is free while in beta, so we don't take payments or collect any card or billing details. If we introduce paid plans later, we'll update this notice before any payment data is processed.
How AI is used
When a host generates a report, the session's reflection text is sent to Anthropic, which runs the Claude model that writes it. This happens only at the moment a report is generated, and only for that purpose. Names and roles are never sent. The text is de-identified before it leaves the service, so the AI is not told who wrote what.
Sent with it, so the report makes sense for your team: the team name, and the context the facilitator gave at setup — sector, country, rough team size, what the team runs on, any regulatory or sector pressures, and any note about data the team must protect. Nothing else about the session leaves the service.
Anthropic processes that text as our processor, under its Data Processing Addendum, which incorporates the Standard Contractual Clauses. Anthropic does not use it to train its models, and deletes the inputs and outputs within 30 days of receiving them.
The AI surfaces alignments, tensions, open questions and suggested next steps as prompts for the team to weigh. It does not make decisions for you.
Who can see your data
- Within a session: display names, roles, reflections, votes, summaries and notes are visible to everyone who has joined that session with the code.
- The host can see and manage everything in their own sessions.
- Other sessions: nothing. Sessions are isolated from one another, and a session is private to the people who hold its join code.
- Your private participant token is stored only in your own browser and is never shown to other participants or the host.
Where your data is stored
Session data is held in a managed PostgreSQL database (Supabase, provided through Lovable Cloud) in the European Union (Ireland), encrypted in transit and at rest. When a report is generated, the de-identified reflection text is sent to Anthropic to produce it, as described above. Anthropic stores that text in the United States, so this is a transfer outside the UK and the EEA. The transfer is covered by Anthropic's Data Processing Addendum and the Standard Contractual Clauses it incorporates, and Anthropic deletes the text within 30 days. Analytics and error data are held by the providers named above under their own terms.
The providers we rely on
We use a small number of trusted providers (sub-processors) to run the service:
- Lovable — application hosting.
- Supabase — the database.
- Anthropic — the AI that writes the report.
- PostHog — product analytics.
- Sentry — error monitoring.
How long we keep it
- Session content persists until the host deletes the session. Deleting a session removes its members, reflections, votes, summaries and discussion notes.
- Host account data is kept while the account is active.
- Analytics and error data are retained for as long as needed to maintain the service, subject to the providers' retention periods.
Your rights
Under UK data protection law you have the right to access the personal data we hold about you, to have it corrected or erased, to object to or restrict its processing, and to data portability. Hosts can delete a session and all its content themselves at any time. Participants can delete their own reflections while a session is open, or ask the host to remove them.
To exercise any right, email ellie.pyemont@enlightentraining.org. If you're not satisfied with how we've handled your data, you can complain to the UK Information Commissioner's Office (ico.org.uk).
Cookies and local storage
We use local storage in your browser to keep you signed in and to remember your private participant token so you can resume a reflection. Our analytics provider may set cookies to measure usage. We don't use advertising cookies.
Changes to this notice
We'll update this page when our practices change, and revise the date at the top. For material changes affecting hosts, we'll also flag it in the app.