Privacy

This version is a translation for information only; the German version alone is legally binding. German version

Draft of 16 November 2026, translated from the German draft – complete the details in square brackets before publication.

1. Controller

[Full name/company] [Address] Email: [Email address]

neolinga translates spoken contributions at events live into text and audio. The organization holding the event is responsible for the transmitted event content; we process this content on its behalf (Art. 28 GDPR; agreement at /avv). Please direct questions about event content to the organization.

2. Visiting the website and hosting

When you visit the website, we process your IP address, the time, the requested address and technical connection data in order to deliver pages, text and audio, fix errors and secure the service (Art. 6(1)(f) GDPR). We do not keep access logs with IP addresses; server error and security logs, which occasionally contain IP addresses, are deleted after 30 days.

The website is operated by UpCloud Oy (Finland) on a server in Germany; the provider processes the data on our behalf (Art. 28 GDPR).

3. Account and organization management

You need an account to manage an organization; you do not need one merely to read or listen to a translation. Sign-in uses Firebase Authentication (Google) with email address and password, with a Google account or, where offered, with an email link. Only Firebase receives your password, not our server. Firebase itself sends a sign-in link by email. We store your email address, Firebase identifier, organization name, memberships, roles, invitations, acceptance of the data processing agreement (version, time, accepting account) and administrative changes. An invitation may contain your email address, entered by an authorized person in your organization. The legal basis is Art. 6(1)(b) GDPR; for employees and agents of an organization and for security measures it is Art. 6(1)(f) GDPR (legitimate interest: secure management of the organization). Information from Google: https://firebase.google.com/support/privacy

We send emails to confirm your address and to reset your password via Resend (Plus Five Five, Inc., USA), which delivers them on our behalf (Art. 28 GDPR). For this purpose Resend receives your email address and the content of the email including the link, and stores delivery logs. The legal basis is Art. 6(1)(b) GDPR; to prevent abuse, we limit requests per IP address and email address for 15 minutes (Art. 6(1)(f) GDPR).

We store account data until the account is deleted. When an account is deleted, we remove the email address, the link to the sign-in account, memberships, sessions and invitations and have the Firebase account deleted; only an internal identifier remains as a reference for billing and change records. Suspended accounts are deleted in this way one year after suspension, entries in the change log after one year. So that each person uses the free Free allowance only once, we store hash values of the email address and Firebase identifier for as long as we offer the Free allowance (Art. 6(1)(f) GDPR; legitimate interest: preventing abuse of the free allowance).

4. Live translation

When an organization starts a translation, the released audio input is transmitted via our server to Google's Gemini API. Google recognizes and translates the speech and returns text and audio; names and other personal information contained in what is said may also be processed. Under the terms for paid services, Google does not use the content to improve its products, but may store it for a limited time to detect abuse (https://ai.google.dev/gemini-api/terms). A local microphone test sends nothing to Google.

Anyone who has the organization's link and, where applicable, its access code can see and hear the translation, including on a projection screen. We do not store audio. Text remains readable for 30 minutes after a broadcast ends and is then deleted. If the organization enables transcript saving for follow-up for a broadcast (not with "Start privately"), we store on its behalf, from then on, the recognized text and its translations together with the event title, times and markers. Only signed-in members of the organization can read and download these transcripts, and only its administration can delete them; we delete them 30 days after enabling.

5. Usage data and security

For each session we store technical values such as start, duration, languages, number of listeners, errors, latencies and consumption, but no spoken content. They serve billing (Art. 6(1)(b) GDPR) as well as quality, fault analysis and capacity planning (Art. 6(1)(f) GDPR; legitimate interest: stable and economical operation). We delete detailed session statistics after 90 days and consumption summaries after one year. To analyze individual faults, operations may enable a technical event log without audio and text for an organization for a limited time; it is deleted after 14 days. To protect against abuse and to count language requests, we briefly process IP addresses or hash values derived from them (Art. 6(1)(f) GDPR; legitimate interest: protecting the service and recording language demand); we delete stored values after 48 hours at the latest.

6. Payments

Paid plans are processed via Stripe (Stripe Payments Europe, Ltd., Ireland). You enter payment and billing details directly with Stripe; we do not receive payment data. We transmit to Stripe the organization's name and identifier and, where applicable, your declaration of non-commercial use, and we store customer, subscription and invoice identifiers, plan and payment status. Stripe also processes payment data as an independent controller, for example for fraud prevention (https://stripe.com/de/privacy). If you choose PayPal when buying a package, PayPal (Europe) S.à r.l. et Cie, S.C.A. additionally receives the payment data as an independent controller. The legal bases are Art. 6(1)(b) GDPR and, for statutory retention obligations, Art. 6(1)(c) GDPR; we retain invoice and booking data for the statutory periods, at most ten years.

7. Cookies and storage in the browser

We use only technically necessary storage (Section 25(2) no. 2 TDDDG), no advertising or analytics tools: - "identity_session": sign-in, at most five days; - "visitor_…": confirmed access code of an event, until the browser is closed; - "preferred_plan": selected plan, at most 30 days; - "neolinga_admin_language": language of the administration, one year; - local storage: reading, display, audio device and presentation settings as well as the email address for a requested sign-in link (removed after sign-in), until you delete the website data; - session storage: invitation (code and email address) and details for resuming a broadcast after reloading, until the tab is closed.

Further processing is governed by the legal bases stated above.

8. Recipients and third countries

Recipients are the providers named in sections 2 to 6 and 9. With Google, Resend, Cloudflare, Stripe and our email provider, data may also be processed in the USA. Google LLC, Plus Five Five, Inc. (Resend), Cloudflare, Inc. and Stripe, LLC are certified under the EU-US Data Privacy Framework; the European Commission's adequacy decision applies to this (Art. 45 GDPR), supplemented by standard contractual clauses (Art. 46 GDPR). You can obtain a copy of the safeguards via the email address stated above.

9. Contact and backups

We process enquiries to us, including via "Support & Feedback" in the administration, in order to answer them (Art. 6(1)(b) GDPR, otherwise point (f) with the legitimate interest of handling your enquiry) and delete them once they have been dealt with and no retention obligation applies. A message via "Support & Feedback" contains your text, your account address and role as well as the name, number and status of your organization. The application does not store it: it goes via Resend to our support address, Cloudflare forwards it to our email mailbox, and we reply to your account address. To prevent misuse of the form, we limit the number of messages per account for 15 minutes (Art. 6(1)(f) GDPR). We overwrite backup copies on the server after 14 days; we additionally store encrypted copies with UpCloud at a second location in the EU and overwrite them after 13 months at the latest.

10. Your rights

You have the right of access, rectification, erasure, restriction of processing and data portability (Art. 15–20 GDPR) as well as the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). You are not legally required to provide us with data; without account or payment details, however, we cannot provide administrative access or a paid plan.

RIGHT TO OBJECT: Where processing is based on Art. 6(1)(f) GDPR, you may object to it at any time on grounds relating to your particular situation (Art. 21 GDPR).

Optional event transcripts

The event organizer can enable transcript saving for follow-up before or during a public event. Saving starts when enabled. Without this selection, no complete transcript is archived. Source text and translations, title and time are saved; audio recordings are not.

Transcripts are accessible only to signed-in members of the respective organization. They remain available for up to 30 days; at most 20 events and 1 million characters per event are retained. Older entries are deleted when using the archive and during regular cleanup. Members with the Administration role can delete transcripts earlier after the event ends. Downloaded files and existing backups are subject to the responsible party’s own retention policies.

Before enabling saving, the event organizer must inform participants and ensure the necessary permission to store transcripts.