Privacy notice

How Leengoconnect handles voice, text and participant data under the EU General Data Protection Regulation (GDPR). Last updated June 2026.

1. Who is responsible

  • Leengoconnect provides the live translation platform. For the events they run, the organiser (church, school, company) is the data controller and Leengoconnect acts as their data processor under Article 28 GDPR. For organiser accounts, billing and platform security, Leengoconnect is the controller.
  • Questions or requests about your data: contact the organiser of your event, or (organisers) use Settings → Feedback in the dashboard. We reply within 30 days.

2. What we collect and why

  • Participants (no account): a random device ID kept in your browser, your chosen language and listening mode, and join/leave times. Purpose: attendance statistics and keeping your connection stable. Legal basis: legitimate interest of the organiser (Art. 6(1)(f)).
  • Questions, ratings and problem reports you choose to send: the text (or a voice recording that is turned into text and then deleted), your language and an optional name. Legal basis: your consent by sending it (Art. 6(1)(a)); you can ask the organiser to delete it.
  • Speaker audio: sent in short pieces for speech recognition, translated, and then discarded. Raw audio is never stored. Transcripts are stored only if the organiser turns on 'Store transcript'.
  • Organisers and co-hosts: name, email, organisation, plan, usage minutes, and a security log of important changes. Legal basis: contract (Art. 6(1)(b)) and legal obligations.
  • Payments: the plan, billing period, amount, card brand and last 4 digits, and when you accepted the Terms. Full card numbers and security codes are never stored by us. Card payments are currently in practice mode and no money is charged.
  • Website analytics: only if you accept analytics cookies — pages viewed and anonymous session replays (PostHog). Legal basis: consent (Art. 6(1)(a)), which you can withdraw under Cookie settings.
  • We only collect what is needed to run the service. We do not collect location, contacts or advertising IDs, use no advertising cookies, and never sell or share personal data for marketing (including 'sale' or 'sharing' as defined in Californian law).

3. Special categories of data

  • Religious services or other events may reveal beliefs or health information (Art. 9). Organisers must have a valid basis (e.g. Art. 9(2)(d) for religious bodies, or explicit consent) and should not enable transcript storage unless needed.

4. Sub-processors

  • OpenAI (USA) — speech recognition, translation, voice for some languages.
  • Google Gemini (USA) — translation when selected by the platform.
  • ElevenLabs (USA/EU) — natural translated voices.
  • Clerk (USA) — sign-in for organisers.
  • Resend via Emergent (USA) — security codes and account emails.
  • PostHog via Emergent — website analytics, only after consent.
  • Hosting and database: Emergent cloud infrastructure.
  • Transfers outside the EEA/UK rely on the safeguards each provider offers, such as the EU–US Data Privacy Framework or Standard Contractual Clauses. Providers process data only to deliver the service.

5. How long we keep it

  • Transcripts and questions: the retention chosen per session (1–365 days, default 30), then deleted automatically.
  • Attendance and feedback: deleted when the organiser deletes the session or their account.
  • Security confirmation codes: 10 minutes. Issue logs: 90 days. Audit trail of admin and security changes: 2 years.

6. Your rights

  • You have the right to access, correct, delete, restrict or object to processing of your data, to data portability, and to withdraw consent at any time without affecting earlier processing.
  • Organisers can download all their data and delete their account themselves in Settings → Your data. Participants can ask the event organiser.
  • You may complain to your data protection authority — for example the Garante (Italy), CNIL (France), the ICO (UK), the Office of the Privacy Commissioner of Canada, or the OAIC (Australia).
  • Residents of California and other US states have similar rights to know, correct, delete and opt out, and will not be treated differently for using them.
  • The service is not intended for children under 16 to create accounts. Organisers running events for children are responsible for any parental consent required.

7. Security

  • All traffic is encrypted (HTTPS/WSS) and strict security headers are applied. Sessions use random links and optional PINs; repeated wrong PINs are blocked.
  • Each account belongs to one organiser who can never be removed. Co-hosts join only by an email invitation from the organiser, accept it with that same email address, and get access only after the organiser approves. Every security change (approving or removing a co-host, deleting data, changing roles) must be confirmed with a one-time code emailed to the organiser.
  • Offensive questions and comments are filtered automatically before anyone sees them. All admin and security actions are recorded in an audit trail.

8. AI transparency

  • Subtitles and voices are generated by AI and may contain mistakes. They are labelled 'AI translated' on the participant screen. No automated decisions with legal effects are made about you.