Privacy policy
Last updated: 15 November 2026
Zenyola is a language-learning platform with its own immersive method: you learn a language from shows you enjoy. It shows two subtitle tracks, synchronized, over a video you are already watching on a video platform you already have access to, and, step by step, adds the study features the method calls for. This policy explains what Zenyola collects, why, where it is kept, and what you can do about it. It is written to be read, not skimmed: it names every kind of data we collect and what each is for. Zenyola is growing, and its study features — lessons from an episode, cards, reviews, practice — need to know more about what you have watched and learned than the first version did. When a new kind of data appears, this policy names it before it is collected, and your account page shows you what is held about you.
Zenyola is run by the people who build it ("we"), and support@zenyola.com reaches them directly.
1. The short version
- You register with an email address and sign in through a link we send to it. No password.
- The extension reads the subtitle tracks the video platform already serves to your browser, and the position of the player, so that it can draw both lines in time. It does not read your platform account, what you browse, your credentials, or the video itself.
- What we keep about you: your email, the languages you choose, when you signed in, the approximate place you connect from (country, region and city, never your IP address), and a small set of typed usage events (for example "an episode was watched for 21 minutes"). Titles appear in those events as a code computed from the platform's identifier, not by name; the people who run Zenyola can match that code to the title in the learning library (section 4.3).
- Subtitle text captured while you watch goes into a shared learning library, stored once for everyone, with nothing that says who watched it. The library also keeps, per title, the platform's identifier and the series and episode name the player shows: facts about the title, with no person attached.
- Your learning history is on from the moment you sign in: we keep for your account every word you tap, with the line it was in, which episodes you watch, when and for how long, and which words you mark as known, so that your study material is built from what you watched and nothing is repeated to you as new. To sign in you tick that you accept this policy. You can see it, export it, remove a word, or switch it off at any time from your account page; switching it off deletes it.
- You can see, export and delete everything we hold about you from your account page. Deleting your account deletes it all.
- If you come from one of Zenyola's ads on a social network and fill in its form, the form gives us your name and the email you leave in it, so that we can write to you about Zenyola — starting with the link to install it — and know whether the ad worked. You can stop the emails at any time. No account is created for you (section 4.11).
- We do not sell data, do not show advertising, and do not share personal data with anyone except the infrastructure provider that runs our service. The one exception is the ad network's pixel on the site's install pages, which tells that network a page was visited (section 4.6).
2. Who this applies to
This policy applies to the Zenyola browser extension, the website at zenyola.com and the account portal on it, the service behind them, and the forms of Zenyola's ads. It does not apply to the video platforms the extension works with: they have their own policies, and Zenyola has no access to what they hold about you.
3. What the extension does on the platform's pages
The extension runs only on the pages of the video platforms it supports. On those pages it:
- reads the list of subtitle tracks the platform offers for the episode you are watching, and fetches the two tracks it needs, exactly as the platform serves them to your browser;
- reads the identifier the platform gives the episode, so that it knows when the episode changes;
- reads the player's current time, so that the two lines are drawn in step with the picture;
- draws its own subtitle lines over the player and hides the player's own subtitle while it does so. It changes nothing in your platform account and never touches your subtitle or audio settings there.
It does not read your platform profile, your watch history, your search or browsing on the platform, your payment details, or any cookie of the platform. It does not record, download or store the video or the audio.
4. What we collect, and why
Read this section as kinds of data and the purposes they serve, not as a frozen inventory. Within the purposes named here — running the service, making it work, knowing whether it is useful, and building your study material — the detail of what we collect will grow as the features do. A purpose we have not named is a change to this policy, announced as section 12 says, and anything that needs your permission asks for it.
4.1 Your account
When you register we collect your email address. It is your identity in Zenyola and where sign-in links are sent. We do not ask for a name, a password or anything else.
When you choose them, we keep the language you are learning and the language you read in, so the subtitles come up in the right pair. Until you choose, they are empty.
To sign in you tick a box saying you have read and accept this policy; without it no sign-in link is sent. We keep when you accepted it and which version, so that we can show that you did and ask again when it changes.
We keep the date your account was created, your plan (today every account is on the free plan) and your role (member, or operator for the people who run the service).
4.2 Sessions
When you sign in, the service issues a session token that the extension stores in the browser's extension storage, out of reach of any web page, and sends to our service with each request. We keep a one-way digest of that token, when it was issued, when it expires, and when it was last used, so that we can recognise your extension and let you sign out or revoke a session. The token itself is never stored on our side.
Where you connect from. Like most online services, we can tell from your connection roughly where you are. The first time the extension contacts our service in each session, we keep the approximate country, region and city our infrastructure provider derives from your connection, together with the date: the first place we saw, and the latest one. We use it to understand where the people who use Zenyola are, and to plan languages, content and communities. It is approximate — a VPN, a mobile network or a company network can place you elsewhere — and it is never your precise location. We do not store your IP address: it is read by the network to deliver the request and is not kept by us.
4.3 Usage events
The extension sends typed events so that we know whether Zenyola works, how much it is used, and which parts are worth building. Each event is one of a fixed list, never free text, and the list grows as the service does; what is on it today is:
- the extension was installed, and the first time it drew a pair of subtitles;
- an episode started, and an episode was watched for a number of minutes;
- the extension failed to capture or draw, with the technical reason;
- the title has no subtitles in the language you are learning, with the language code;
- a word was tapped for its entry, and the panel was left for an outside dictionary — as counts per title, never which dictionary. The word itself, when it travels with the event, is counted in a table of its own by language and day, with no account and no title behind it, so that we know which words people look up;
- where in the subtitles a tapped word is — which track of the learning library (section 4.4), the moment of its line and the word's position in that line, never the text — counted by day with no account behind it, so that we know which lines are hard to follow; your learning history keeps it for you only while it is on (section 4.9);
- you recommended Zenyola from the settings — that it happened, not where the link went nor to whom;
- a card over the video asked you to review or recommend Zenyola — that it was shown, and whether you opened the review page, shared the link or put the card away. To decide when to show it, your browser keeps a count of the episodes you watched and the words you looked up; that count stays in your browser and is never sent;
- which features of the extension you used, as a count per feature per episode — resting the pointer on a word, stepping between lines, opening a category or a mark, playing a pronunciation, hearing a line again, following a word, searching, changing a setting and the option chosen (a language only as its code) — never the word, nor what you searched for, nor the title's name;
- events that could not be sent earlier and were dropped, as a count.
In these events a title is identified by a hash: a short code computed from the platform's identifier for the title, never its name. The people at Zenyola who run the service can match that code against the titles of the learning library (section 4.4), and so see which titles an account tapped words in and where the panel did not answer it. They use it only to understand how Zenyola is used and to fix what fails; it is never shown to anyone else, sold, or used for advertising. Events never carry a page address or subtitle text. From the minutes and episodes we keep a usage count per month for your account.
We use these events to keep the service working, to measure whether it is useful, to decide what to build next and which titles to analyse first, and to protect the service from abuse. While your learning history is on (section 4.9), the same events also build it, and then a title is named as well as hashed, because your history has to say which episode a word came from.
4.4 The learning library
When you watch an episode with Zenyola, the two subtitle tracks the platform served to your browser are sent to our service and kept in a library: the text of each line and its timing, its language, the kind of track (subtitles or captions), the platform's identifier for the title, the name of the series and of the episode as the player shows them, the season and episode number when the platform gives them, and a code computed from the content itself. The name and the numbers are facts about the title, kept so that study material can say which episode it is about; they carry no reference to any person. Each track is stored once for everyone: if someone has already watched the same episode, nothing new is stored.
The library carries no reference to who watched what: the usage events of section 4.3 are where an account's activity is kept, by the title's code. A track is not linked to your account, and deleting your account leaves the library exactly as it was, because there is nothing of yours in it. We keep, per title and language, a count of how often it is watched, so that we can decide which titles to analyse first.
The library exists for one purpose: to align and, later, to analyse the language of the dialogue, so that the text a viewer sees is enriched with explanations. It contains text and timings, never video, audio or images, and it is served only to a viewer who is watching that very episode on the platform. See the terms of use for how rights holders can ask for a title to be withdrawn.
4.5 Problem reports
If you report a problem from the extension, the report is prefilled with the extension version, the build, the platform adapter in use, the last technical failure, and the title's hash. If you send a report and leave the box ticked, the report also carries the title's name as the player showed it, the moment on the timeline, and what the extension had captured for that episode (the languages, the tracks it kept and their line counts, and the pair of lines on screen at that moment), so that what you saw can be reproduced. Untick the box and none of that is sent. You may also add screenshots to a report; a screenshot shows whatever was on your screen, so only add what you mean to share. They are stored with the report, seen only by the people at Zenyola who read reports, and deleted with it, or earlier if the title they show is withdrawn. You see the whole report before sending it, and it goes to us by email.
You can also write to us from the contact form on this site, with or without an account. A message sent there carries only what you write, the kind of message you choose, the screenshots you add, the language of the page and the version of the site; it is kept, read and deleted like a report from the extension.
4.6 The website
The registration page uses Cloudflare Turnstile to tell people from automated scripts; Turnstile may set a cookie of its own for that purpose and is governed by Cloudflare's policy. Signing in to the portal sets a session cookie that lasts as long as your session. We use no analytics cookies.
The ad pixel. The public pages that tell you how to install Zenyola — the install page and the welcome page that opens after installing — may load Meta's pixel, a small script from the network where Zenyola advertises. It tells Meta that the page was visited and, on the welcome page, that Zenyola was installed, together with the page's address, technical data about your browser and Meta's own cookies; if you have an account on Meta's services, Meta can relate the visit to it. We use it to measure and improve our ads: to know whether they bring people who install Zenyola, and to show Zenyola's ads to people who visited these pages and to people similar to them. What comes back to us are aggregate figures, never who you are. The pixel never carries your email or anything from your Zenyola account, and it never loads in the portal, on the sign-in page or in the extension. Meta handles what the pixel sends under its own privacy policy. You can block it with your browser's settings or with an extension that blocks trackers, and Zenyola works the same without it.
The home page shows its video as a still picture. The player comes from an outside video service and loads only when you press play, from its address that sets no cookie until then; once it plays, that service's own policy applies to it. Nothing of it loads before you ask.
4.7 What the extension keeps in your browser
In the browser's extension storage, on your device only, the extension keeps: your session; a cached copy of the remote configuration it reads from us; a cache of aligned subtitle pairs for the episodes you watched recently, so that they come up faster next time; and the position of the on/off switch. Removing the extension removes all of it.
4.8 The remote configuration
At start, and every few minutes, the extension reads a small configuration document from us that says which platform adapters are switched on and which extension version is the minimum supported. That read carries your session and nothing else; it is how we can switch the extension off for everyone within minutes if a platform changes its player.
4.9 Your learning history
Zenyola's study features — a short session after an episode, cards with the line where a word appeared, reviews that come back in the next episode of the same series, and later the practice of saying a line aloud — need to know what you have watched and learned. That knowledge is your learning history. It is on from the moment you sign in, because ticking the box at sign-in is your acceptance of this policy (section 4.1). If you do not want it, switch it off from your account page: switching it off deletes everything in it at once, and nothing more is kept until you switch it on again.
While it is on, we keep for your account what you do with Zenyola. Today that is:
- the episodes you watched with Zenyola, by the platform's identifier and by the name the player shows, with when and for how long;
- every word you tap: there is nothing to save by hand, a tap is enough. Each word is kept with how many times you met it, when, and where: which track of the learning library, the moment of its line and the word's place in that line. The line's text is not copied into your history; your account page reads it from the library when it shows it to you, so a title withdrawn from the library leaves the word without its line;
- where each word stands for you: to learn, where every tap lands, or known, when you mark it so. A known word you meet again in another episode goes back to to learn on its own;
- a word written as a name in its line is not vocabulary, and never enters your history;
- when they arrive, the results of your study sessions, as scores and the items you got wrong, and when each word is due for review;
- when the practice of speaking arrives, your voice recordings of dialogue lines and the assessment of each, kept for as long as you keep the recording. Your voice is biometric data and we treat it as sensitive data everywhere: giving it is optional, it is asked for separately, and it is not needed to use Zenyola (section 6).
As the study features grow — new kinds of exercise, new ways of reviewing — what they record grows with them, always inside this purpose: to build your study material, to know whether it is teaching you anything, and to make it better. A purpose beyond that is a change to this policy and asks for your permission first.
Models and your data. We do not train models on your personal data. Models are used to analyse the dialogue of a title once, for everyone, and to generate study material from that analysis; they never learn from a person. If we ever wanted to train on anything of yours, we would ask you first, in plain words, and you could say no and keep using Zenyola. Section 4.10 says what we do with data that no longer names anyone.
Your account page shows your learning history as it is: your words with their lines, and the episodes you watched. From there you can mark a word as known or bring it back to learn, remove a single word with its lines, export the whole history as a spreadsheet file (CSV) or as JSON, and switch it off. It is deleted with your account, or on its own when you switch it off.
4.10 Improving Zenyola, and data that no longer names you
To make the teaching better we look at what works across everyone: which explanations are read, which concepts most people get wrong, which episodes are too hard for the level they claim. That work is done on aggregated or de-identified data — counts and patterns with no account behind them, which we cannot turn back into a person. Data in that state is not personal data, we may keep and use it without the limits of this policy, including to build and improve the analysis, the lessons and the exercises, and to say publicly how the service is used.
Everything before that state — your account, your events, your learning history — stays under the rest of this policy, and the controls in section 9 apply to it in full.
4.11 If you come from one of our ads
Zenyola advertises on Meta's social networks. Some ads carry a form inside the social network: if you fill it in, Meta hands us the name and the email address you leave in it, with the date and the ad it came from. The form comes filled in with them from your profile, and you can change them before sending it. We use them to write to you about Zenyola: first the link to install it on your computer and, later, news, tips for using it and offers. Also to know whether the ad worked: if you later create a Zenyola account with that same email, we count it.
No account is created for you from the form. Your account is born, as anyone's, when you sign in from the extension and accept this policy. Every email we send you from the form carries a link to stop receiving them; using it, or writing to us, deletes your name and email from our contacts. Meta keeps its own copy of what you sent in the form, under its own policy.
5. What we do not collect
Some things we will not collect, whatever we build. We do not collect your platform credentials, the video or audio of anything you watch, the pages you visit outside the platform's pages, or precise location (such as your device's GPS). The approximate place in section 4.2 comes from the connection, without storing your IP address. We never read your watch history on the platform: the only titles we can know about are the ones you watch with Zenyola on. We do not use fingerprinting. The extension and the portal carry no advertising or third-party tracking networks — what we measure there, we measure ourselves, with the typed events of section 4.3. The one exception is the ad pixel on the site's public install pages (section 4.6).
And two promises that are not about collection at all, because they are the ones that matter: we do not sell your data, and we do not show you advertising. If a payment plan arrives, payment details will be handled by the payment provider and named here before it does.
6. What permission we process your data on
Everything rests on your permission, given in the knowledge of what this policy says and withdrawable whenever you like. That is deliberate: explicit permission is the most demanding thing any data-protection regime can ask for, so a text written on it holds wherever you live, without having to pick a country.
- Your email and session data are what the service needs in order to exist: without them there is no account and no way to recognise you. Withdrawing permission for those is the same as closing your account, and you do that from your account page.
- Usage events and problem reports are processed to keep the service working, to know whether it is useful, to decide what to build, and to protect it from abuse. Accepting this policy when you register covers them.
- Your learning history (section 4.9) is on from sign-in, covered by the same acceptance; you can switch it off from your account page whenever you want, and switching it off deletes it.
- Your voice recordings, when the practice of speaking arrives, stand apart too. Voice is biometric data and we treat it as sensitive everywhere: it will be asked for separately and expressly, and nobody loses access to Zenyola for declining.
- The contact from an ad's form (section 4.11) rests on the permission you give by sending the form, which links to this policy. It covers writing to you about Zenyola and counting whether the ad worked. Stop the emails, or write to us, and it is deleted.
- The ad pixel (section 4.6) runs only on the pages that explain how to install Zenyola, to measure our ads. You can refuse it by blocking it in your browser, without losing anything.
The learning library holds no personal data, and neither does aggregated or de-identified data (section 4.10).
If a data-protection regime applies where you live, you also have every right that regime gives you. This policy does not attempt to cut any of them down.
7. Who processes data for us
Our service runs on Cloudflare: the application, the database, the storage of the library, the sending of our emails and the Turnstile challenge. Cloudflare processes data on our behalf and under its own privacy commitments. We may add a processor when a feature needs one — a payment provider, a speech or language model service for the study features — and each one is bound by a contract to use the data only for what we ask; the list here names them before they start. We do not share personal data with anyone else, we do not sell it, and we hand it over to an authority only when the law requires it.
Cloudflare operates a global network, so your data may be processed in a country other than yours. Every processor is bound by contract to use the data only for what we ask, and accepting this policy is your permission for that processing outside your own country.
If you come from one of our ads, Meta handles the ad's form and the pixel of section 4.6. Meta is not a processor working on our behalf: it is an independent service, and it handles what it receives under its own privacy policy. The contacts its form hands us are kept on Cloudflare like everything else, and our emails to them leave through it.
8. How long we keep things
- Your account, languages and usage counts: until you delete your account.
- Where you connect from (first and latest place): until you delete your account.
- Sessions: thirty days from issue, or until you sign out or revoke them; expired and revoked sessions are removed.
- Usage events: twenty-four (24) months, after which they are deleted or reduced to aggregate counts with no account reference.
- Your learning history: while it is switched on; deleted when you switch it off or delete your account. Voice recordings: until you delete them, and at most twelve (12) months each.
- Aggregated or de-identified data (section 4.10): kept without a time limit, because there is no one in it to keep it about.
- Sign-in links: fifteen minutes, single use.
- The learning library: it holds no personal data. Tracks stay until the title is withdrawn at a rights holder's request, or removed because nobody watches it.
- Problem reports, and the screenshots added to them: twelve (12) months.
- Contacts from an ad's form (name and email): until you stop the emails or ask us to delete them.
9. Your rights and how to use them
From your account page you can see what we hold about you, export it, sign out everywhere, and delete your account. Deleting your account removes your email, your languages, your sessions, your usage counts, your usage events and your learning history, at once and without asking why. What remains afterwards is nothing that refers to you.
If all we have is your contact from an ad's form, the link in our emails, or a message to support@zenyola.com, is enough to delete it.
You also have the right to know what we hold about you, to correct it, to ask us to delete it, to be told what use we make of it, and to withdraw your permission — none of which you have to justify.
How to use them. Write to support@zenyola.com from your account's email address, or from another one saying which account it is. That mailbox is attended by whoever builds Zenyola. We commit to answering you within fifteen days, and to telling you why if we ever need longer.
If there is a data-protection authority where you live, you can go to it, and you have whatever rights your regime recognises, including access, correction, deletion, restriction, portability and objection.
10. Security
Everything travels over HTTPS. Session tokens and sign-in codes are stored only as one-way digests. Secrets are kept outside the code and the repository. The extension sends your session to our service and to no other address.
11. Children
Zenyola is not directed at anyone under eighteen, nor at anyone below the age of majority where they live if it is higher there, and we do not knowingly hold an account for one. If you believe a child has registered, write to us and we will delete the account.
12. Changes
When this policy changes, the date at the top changes, and a change that affects what we collect or why is announced in the extension before it applies, and asked for again at your next sign-in. Continuing to use Zenyola after that means you accept the new version.
13. Contact
support@zenyola.com. That mailbox is the channel for anything about your data or this policy, and it is attended by whoever builds Zenyola.