Privacy notice

Team AI Conversation 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.

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 and error logs. We use PostHog to understand how the tool is used and Sentry to capture errors, so we can keep it working. These may include a user identifier, pages visited and technical event data. Our lawful basis is legitimate interest in maintaining and improving the service.

Payments. If you buy anything, payment is handled by Paddle, who act as merchant of record. We receive confirmation of your entitlement, not your full card details.

When a host generates a pattern summary, the reflection text and display names in that session are sent to our AI provider through the Lovable AI gateway to produce the summary. This happens only at the moment a summary is generated, and only for that purpose. The content is not used to train AI models.

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.

• 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.

Session data is held in a managed PostgreSQL database (Supabase, provided through Lovable Cloud), encrypted in transit and at rest. We can confirm the specific hosting region on request. Analytics, error and payment data are held by the providers named above under their own terms.

We use a small number of trusted providers (sub-processors) to run the service:

• Lovable — application hosting and the AI gateway.
• Supabase — the database.
• PostHog — product analytics.
• Sentry — error monitoring.
• Paddle — payments (merchant of record).

• 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.

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).

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.

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.