Yokla — Privacy policy

Last updated: 16 October 2026 · Extension version: 2.1.0

Yokla watches for alert words in the audio of the Chrome lesson tab where the user starts it, in BigBlueButton public chat, or in a lesson chat the user has taught it on that site. This policy explains the data the extension processes, the services it is sent to and how long it is kept.

Lesson tab and chat

Only the lesson tab the user selects is accessed. The tab’s ID, title and address are used locally to follow the right tab and to return to the lesson from an alert; they are not sent to the developer or to Telegram. The browser’s browsing history is not scanned.

If chat monitoring is on, new messages in the BigBlueButton public message area are evaluated on the device. The history present at the start, private chats, sender names, reactions and other text on the page are not included in chat detection. Even so, the message content itself may contain personal information.

On another platform, the user can teach the extension the chat by pressing Chat in the popup and clicking a message. In that case, only the site’s root (for example https://lessons.example.edu) and the page selectors that find the message list, the message rows and the message text are stored in local storage on the device; the page path, the lesson link and message content are not stored. In a taught chat too, only the selected text field of rows added after monitoring starts is evaluated on the device; on some platforms this field may also include the sender’s name. Taught sites are listed under Settings → Monitoring settings and can be removed one by one.

Word and context rules run on the device. No messages are sent to a developer server or to an AI service for chat analysis. At most 500 characters of the latest message and the detection status are kept in temporary Chrome session storage.

Tab audio and speech recognition

Only the audio of the tab where you started listening is captured. The microphone is not used; the extension does not make audio recordings or audio files. The audio is routed back to the same device’s audio output so that it can still be heard.

Chrome’s Web Speech speech recognition service is used to turn speech into text. Chrome may use a remote service; lesson audio may be sent to this service, and an internet connection is required. Google’s privacy policy applies to this third-party processing. The extension does not control the third party’s own retention practices.

When monitoring is started for the first time, the extension shows how audio and chat are processed and that audio may be sent to Google’s speech recognition service; monitoring starts only after it is confirmed with Got it, start. If the data processing changes, consent is asked for again.

Audio and chat monitoring can be turned off separately. In chat-only mode, no audio is passed on for speech recognition. The latest speech text and the last 10 alerts are kept in temporary session storage.

Alerts and appearance

Alert text may be shown in the extension’s popup, in the Chrome alert window and, if enabled, in the operating system notification. If quiet feedback is on while the lesson tab is in front, a 6-second message is shown on the lesson page; this message contains a few words around the detected word (the whole heard sentence for a short result) and is in the DOM that the lesson page can access. If the same announcement is heard again, the message is shown again with a “×N” count. Bot details are not added to this message.

Whether the lesson tab is active, and whether the Chrome window is focused or minimized, is read at the moment of an alert to decide on the quiet-feedback preference; this is not passed to any outside service. Alert sounds are generated on the device with Web Audio. If the theme follows the system, the operating system’s light/dark preference is read through the browser; this information is not sent out.

Preferences stored on the device

Monitoring words, speech/interface language, theme, sound, repeat intervals, notification preferences, display options and whether the getting-started guide has been completed are stored in Chrome’s local storage. The confirmation answers the user gives to notification/sound tests, and their times, are also local. This data is not sent to the developer and is not synced with the Chrome account.

Optional Telegram

Telegram is off by default. If you enable it, your own bot and the personal chat you choose are used. The token, Chat ID, options and an unfinished form draft are stored in local storage on the device. The bot token is kept encrypted in this storage: with the browser’s own encryption (AES-GCM) and a key that cannot be extracted from the extension and is kept only in the extension’s data on this device. This protects the stored copy; the extension itself decrypts the token to use it. The saved connection is kept when Chrome is reopened and when the extension is updated.

The token is sent to the Telegram Bot API over HTTPS to verify the bot, check pairing and send messages. It is not given to the lesson page, the popup or the speech engine. Local and session storage are closed to content scripts.

Automatic pairing uses a random code that is valid for three minutes. The link that opens your own bot contains the bot’s username and this code; it does not contain the token. The ID of the paired personal chat first goes into the form; the active destination is changed only with Connect and save. Pairing and the extra chat-finding option may read the bot’s Telegram updates; these may contain the chat ID, name/username and messages. The extension does not delete the webhook and does not send an `offset` that would acknowledge another system’s updates.

The default Telegram alert contains the matched phrase, the time and, where needed, the source. The lesson’s address, title and audio are not sent. If you separately turn on Also send the speech/chat text for the alert, at most 500 characters of the related text are added to the message. Sent messages are subject to Telegram’s privacy policy.

Follow live lesson text in Telegram is a separate preference, off by default. If you turn it on, recognized speech text and new public chat messages are passed to the same personal bot chat even when no detected word is present. This sending continues while the lesson tab is in front too. The text is not summarized; the same silent Telegram message is updated about every 5 seconds as the interim speech text is corrected. Long text is split into new silent messages. Regular attendance alerts continue as separate messages with their own preferences; this option does not turn Telegram alerts on or off. The computer and Chrome must be on and monitoring must be active; the phone does not capture lesson audio.

The live sending queue, Telegram message IDs and completed part IDs are kept only in trusted temporary session storage; the bot token and Chat ID are not kept there. The queue holds at most 8 pages of text; if the connection is down for a long time, older unsent text may be dropped and this is reported on screen. The queue is cleared when monitoring stops, when the connection changes or when this preference is turned off. Earlier messages in Telegram are not deleted. The Telegram service’s own retention and deletion rules apply.

The BotFather link opens the official chat; the user creates the bot. Copying a command writes to the clipboard only when the button is pressed; it does not read the clipboard’s contents.

Retention, deletion and control

• Local preferences, bot details and drafts stay on the device until they are changed or the extension is removed.
• On a permanent audio source error, the temporary speech text is cleared; on a chat source error, the temporary chat text is cleared; the other source that is still working is kept. Stopping manually or a full interruption clears both sources. The last alert can be seen for the duration of the browser session.
• Session storage is cleared when the browser restarts; repeat-grouping information is reset when monitoring is stopped.
• You can turn off Telegram alerts, adding text to alerts and live text forwarding separately in Settings, and you can stop monitoring at any time. Turning them off does not delete the saved token. Settings → Telegram → Delete bot connection deletes the token, Chat ID, draft, live text preference and encryption key from this device and releases the Telegram access permission. Explicitly saving with another bot replaces the old connection; the old bot is managed separately in Telegram.
• Removing the extension deletes the extension’s data in Chrome; it does not delete messages already sent to Telegram or data in third-party services. Those are managed through the relevant service.

How the data is used

There is no data collection server belonging to the extension’s developer, and no advertising, analytics or user tracking code. Data is not sold; it is not used for ad targeting, credit assessment or any purpose outside the extension’s lesson alert function. Telegram forwarding happens only within the feature the user turns on.

Yokla’s use and transfer of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

For privacy questions, you can contact emirbilici@gmail.com.