Privacy policy
This page explains what LingoSide processes when you use lingoside.ai, the LingoSide application and our support channels, why it is processed and what you can decide. It applies to every edition of the application, including the one installed from the Microsoft Store.
Last updated: 20 September 2026
Ask a privacy questionWho is responsible
LingoSide decides how and why the data described here is processed. For any privacy question or request, write to the address below. We answer from the same mailbox that handles support.
founder@lingoside.aiThe website
Our hosting provider records standard server logs — IP address, requested page, time and browser type — to run and secure the site. LingoSide does not use them to profile visitors.
On each page load, we send a cookieless page view through LingoSide's server to PostHog in the EU, even before a consent decision or after declining behavioural analytics. It includes the page path, browser and device type, screen size, referring site, campaign and language. PostHog briefly uses the request's IP address and User-Agent with this site's hostname and a daily random value to compute an identifier on its server; the raw IP and User-Agent are not retained in the analytics event. The count writes no cookie or identifier to your browser. This identifier can link this site's page views within a day to estimate visitors and sessions; it does not link the same visitor across days. People sharing the same network and browser details may be counted as one. We respect Do Not Track and Global Privacy Control. The analytics SDK and behavioural events remain off until you choose Allow analytics. We never send form contents, full URLs or advertising identifiers, and session recording stays off. Your language choice and analytics decision are kept locally in your browser; you can change your decision under Analytics preferences in the footer. LingoSide's server also looks up the approximate country in a local DB-IP database and sends only the country code and name; it does not send the visitor's IP to DB-IP or collect a city or coordinates. Country estimates can be inaccurate, especially with a VPN.
The waitlist stores your email address, the list you choose (learners, teachers or pilot participants) and the time you joined. The contact form stores your name, email address and message. Both are kept on our server and emailed to LingoSide so we can reply.
The sign-in page sends your login name and password only to the LingoSide API over an encrypted connection. It records the cookieless page view described above, without inspecting the form or storing analytics identifiers or session data in the page.
The application
LingoSide creates your account for you; there is no self-service registration. We store your login name, your language settings and the operational records needed to run and secure the service, such as sign-in events and session leases.
During a live session, audio from the source you selected is streamed to a speech-to-text provider to produce the transcript. LingoSide does not create or keep an audio recording, and the provider is used in its EU region.
Recognised text — never audio — is sent through LingoSide's server to translation and AI providers to produce translations and reply suggestions. Transcripts, translations and suggestions are stored in your lesson archive, on your device and on LingoSide's server, until you delete them. LingoSide does not use your lesson data to train AI models.
Product analytics (PostHog, EU) and AI quality observability (Langfuse, EU) are off until you grant each one in the application. Granting one never grants the other. They carry pseudonymous usage events or AI operation metadata — timing, token counts, error codes — and never lesson content, prompts or model output. Withdrawing a permission stops new events immediately and drops anything not yet sent.
The Microsoft Store edition is installed and updated by Microsoft under Microsoft's own privacy statement. An edition installed from lingoside.ai checks lingoside.ai for updates, which leaves a standard server-log entry.
A lesson transcript can include what other participants said. Inform every participant and obtain their permission before using LingoSide in a lesson. Local law and the platform you teach on may add requirements.
Providers
Each provider processes data only on LingoSide's instructions, for the purpose listed here. Where a provider processes data outside the European Economic Area, we rely on the safeguards the GDPR provides, such as standard contractual clauses.
What LingoSide does not do
Retention
Deleting your account removes your account data and lesson archive from LingoSide's server and purges unsent telemetry; we then ask the telemetry providers to delete what they hold.
Your rights
Under the GDPR you can ask us to access, correct, delete or export your data, to restrict or object to its processing, and you can withdraw a permission at any time without affecting what was done before. Write to the address below; we may ask you to confirm your identity. You can also complain to a data protection authority — in Poland, the President of the Personal Data Protection Office (UODO).
LingoSide is used in lessons led by a teacher. Where a learner is a child, the teacher, school or guardian arranges the account and informs the learner. Write to us if you believe we hold a child's data without that arrangement.
We update this page when the processing changes and note the date at the top. Material changes are announced in the application or by email.
Use this address for access, correction, deletion and every other privacy request.
founder@lingoside.ai