Essio Privacy Policy

Effective date: August 14, 2026

Essio is a Chrome extension that shows YouTube transcripts and creates concise AI-generated digests when a user explicitly requests one. This policy explains what Essio processes, why it is processed, where it goes, how long it is kept, and how to request deletion. Essio does not require a user account, and this page uses no cookies or analytics.

1. Data processed locally

• Essio reads the title and available transcript of the YouTube video currently open in the browser so it can show the transcript and prepare a requested digest.
• The selected digest language and a randomly generated anonymous installation ID are stored in chrome.storage.local. They remain until the setting is changed, extension storage is cleared, or the extension is uninstalled.
• The current transcript and generated digests are held in page memory for the active browsing session. Essio does not persist them in its server-side telemetry database.

2. Digest generation

Essio does not send a transcript for AI processing merely because a YouTube page is opened. When the user presses the digest generation or refresh action, the extension sends the following over HTTPS to the Essio Backend: video title, transcript, requested digest language, browser interface language, extension version, anonymous installation ID, and request ID.

The Essio Backend sends the title and transcript to DeepSeek solely to generate the requested digest. When the requested language requires translation, the generated draft digest is sent to DeepSeek in a separate translation step. DeepSeek does not receive the Essio installation ID. Essio does not store video titles, transcripts, prompts containing them, or generated digest text in YDB, application logs, or error-report emails.

3. Beta telemetry and limits

To operate the free Beta, enforce the daily limit, prevent obvious abuse, measure reliability, and understand aggregate product use, Essio stores:

• anonymous installation ID and first-seen, last-seen, and first-success timestamps;
• activity date and successful digest count;
• request/event IDs, interface language, digest language, success or error code, request duration, AI-call count, translation-call count, and token-usage totals;
• short-lived request reservations and rate-limit counters.

Essio does not use this information for advertising, cross-site tracking, profiling, credit decisions, or sale to third parties.

4. Network anti-abuse data

The backend receives connection information needed to answer a request. The Essio application does not store the raw IP address. It immediately derives a keyed HMAC hash used only for short-lived network rate limits. This hash is not used to identify a person or browsing history and expires with the related rate-limit counters.

5. User-submitted error reports

Essio sends an error report only after the user presses “Report an error”. A report can contain request IDs, anonymous installation ID, extension version, interface and digest languages, provider and processing stage, error codes and types, HTTP status, duration, AI/token counts, transcript length, caption-track metadata, and similar whitelisted technical diagnostics.

Error reports never contain the video title, transcript text, generated digest text, API keys, or raw IP address. The full technical report is stored in YDB. A compact notification is sent through Yandex Mail to the Essio developer and contains only lookup IDs and limited error metadata, not the full report or content of the video.

6. Retention

• Installation records, daily activity, and digest telemetry: up to 180 days. The installation record period runs from its latest activity.
• Technical error reports in YDB: up to 90 days.
• Rate-limit counters, request reservations, and network HMAC hashes: up to 2 days.
• Content-free application logs in Yandex Cloud: 3 days.
• Video titles, transcript text, and generated digest text: not retained server-side by Essio.

Compact Yandex Mail notifications are used only to locate a submitted report. They are removed when the associated data-deletion request is processed and may otherwise remain until manually cleared from the support mailbox.

7. Service providers and sharing

• Yandex Cloud hosts the Essio Backend, YDB telemetry storage, secrets, and short-lived application logs.
• DeepSeek processes the title and transcript to generate the requested digest and, where needed, processes the draft digest for translation.
• Yandex Mail delivers compact notifications for user-submitted technical error reports.

Data is shared only as necessary to provide, secure, maintain, and measure Essio, or when required by law. Essio does not sell user data or share it with advertising platforms or data brokers. Humans do not review video titles, transcripts, or generated digests because Essio does not retain them.

8. Security

Data sent by the extension is transmitted over HTTPS. Production provider credentials are kept server-side in Yandex Lockbox and are not included in the public extension. Stored Beta data is access-controlled within the production Yandex Cloud environment.

9. Access and deletion requests

To request deletion of server-side data associated with an installation, email inemesis@yandex.ru with the subject “Essio data deletion” and include either the Essio installation ID or an Essio request ID shown in an error or report response. If neither is available, contact the same address for instructions on retrieving the installation ID stored locally.

The deletion procedure removes the matching installation record, daily activity, digest events, technical error reports, request reservations, and installation-specific rate counters. Unlinkable network HMAC counters cannot be matched back to an installation and expire automatically within 2 days. A matching compact support-mail notification is also removed when a request ID is available.

Uninstalling Essio or clearing its extension storage removes local settings and the local installation ID. It does not immediately delete already collected server-side Beta records, which remain subject to the retention periods above unless deletion is requested.

10. Contact and policy changes

Privacy questions and deletion requests can be sent to inemesis@yandex.ru. If this policy changes materially, the effective date will be updated and material changes will be disclosed as required.

Chrome Web Store Limited Use

Essio's use of information received from Chrome and YouTube is limited to providing and improving the extension's disclosed single purpose and complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.