Overview
Effective date: October 6, 2026. This policy explains how UnTrap, operated by Yevhen Tretiakov, collects, uses, stores and shares data in its browser extensions, apps and related website and cloud services. Contact: support@untrap.app.
UnTrap's purpose is to help you customize YouTube, reduce distractions and use optional focus and video-summary tools. Core interface changes and local settings work without an account. Account access, settings sync, purchases and AI features involve the data processing described below.
Data collection and use
- Local YouTube controls: the extension reads relevant YouTube page content and URLs to hide, filter, redirect or adjust content according to your choices. Preferences, filters, schedules, focus state and local protection settings are stored on your device. This does not upload your general browsing history or a continuous record of videos you watch.
- Account and authentication: when you register or sign in, we process your email address, account identifier, password or verification information, and session tokens to provide and secure your account. Passwords are stored as hashes, not readable passwords. Verification and password-reset messages are sent to your email address.
- Optional settings sync: when enabled, selected settings and their synchronization metadata are stored with your account on our server and retrieved by your other signed-in devices. Synced settings can include filters and preferences you enter. Turning sync off stops future synchronization; it does not itself delete an existing server copy.
- Video summaries, comment summaries and transcript tools: when you request a cloud operation, your device sends the selected YouTube video URL, requested operation and language, and applicable duration or transcript-chunk information. An authentication token identifies your account for access, credits and subscription checks. Our server obtains video metadata, transcripts or public comments and sends the relevant text and instructions to an AI provider. Results, source content and technical job records may be cached or stored. Although reusable content caches are keyed by video and language, request and usage records can be associated with your account; the entire process is not anonymous.
- Subscriptions and purchases: we process account, customer, transaction, product and subscription identifiers and entitlement status to provide paid access, restore purchases and handle billing requests. Payment details are entered with the payment provider or app store, rather than into the extension's local settings.
- Technical requests and diagnostics: requests for configuration, service availability, recovery time, authentication and cloud features expose normal connection information, such as an IP address and request headers, to our servers and infrastructure providers. We process operational records such as timestamps, outcomes, errors, performance, account identifiers or pseudonymous identifiers where needed to run, secure and troubleshoot the service.
- Product communication and website events: we count events such as viewing or dismissing a Plus announcement, following its explanation link, and visiting offer pages. Announcement event payloads contain a bounded event name and source, not your YouTube URL, email or account ID. The network request still reaches our infrastructure. Purchase flows may also retain event and transaction references to diagnose checkout and account provisioning.
- Support: if you contact us or send diagnostic data, we process the contact details, message and technical information you choose to provide. Copy Diagnostic Data prepares a report for your clipboard; copying alone does not send that report to support.
Handling and security
Cloud communication uses HTTPS. Access to account and cloud operations is authenticated where required. We use measures such as password hashing, scoped session tokens, access controls and bounded diagnostic records. These safeguards reduce risk but do not make any service completely risk-free. Local settings remain subject to the security of your device and browser profile.
We use data to deliver the feature you request, synchronize your selected settings, authenticate you, verify paid access, prevent abuse, resolve failures and answer support requests. We do not sell personal data or use YouTube browsing data for advertising, data brokerage or unrelated profiling.
Storage, retention and deletion
- On your device: local settings and cached state remain until you reset or remove them, clear the browser's extension data or uninstall the extension, subject to browser and device backup behavior. Removing the extension does not delete a cloud account or cancel a subscription.
- Account and sync: account records and synced settings are retained while needed to provide your account. Account deletion removes the active account, authentication sessions, verification/reset challenges and synced settings handled by our account-deletion service. You can use the account controls or contact support for a deletion request.
- AI content and jobs: reusable transcripts and generated content may remain in caches independently of your account. Authenticated execution, credit, delivery and diagnostic records have separate operational lifecycles. We retain these for delivery, retries, credit accounting, abuse prevention and troubleshooting, and remove or compact them through service maintenance when no longer needed for those purposes. Deleting an account does not necessarily erase every shared video cache or historical diagnostic record immediately.
- Billing and support: purchase records and certain customer relationships may be retained after account deletion for subscription administration, restoring an existing purchase, accounting, disputes or legal obligations. Deleting an account does not cancel a subscription with a payment provider or app store. Support correspondence is retained as needed to resolve and document your request.
- Logs and backups: operational records and backup copies can outlast active records until maintenance or backup replacement removes them. Retention depends on the record's purpose, active incidents and legal obligations. A deletion request can be used to ask about remaining data and applicable exceptions. We do not promise that deleting an account immediately erases every provider's record or backup.
Your choices
You can use local interface controls without creating an account. Cloud requests occur when you use the corresponding feature; technical service requests and the limited event counts described above can also occur without an account. You can leave sync disabled, avoid cloud summary tools, sign out, reset local settings, delete your account or contact support about your data. Signing out or disabling a feature does not automatically erase data already stored.
Before using optional cloud features, review the information provided in the extension and this policy. Where additional disclosure or consent is required, it must occur before the relevant collection. Access, correction and deletion requests can be sent to support@untrap.app; we may need to verify that the request concerns your account.
Browser permissions
Access to YouTube pages, active-tab access and scripting support the page changes and tools you select. Storage keeps extension state and settings; alarms support timed functionality. Permission availability differs by browser and version. Permissions do not by themselves mean that all accessible page data is uploaded: the actual cloud transfers are described above.
Changes and contact
We update this policy when relevant practices change and show the effective date above. Material changes requiring additional notice or consent will be handled before the affected processing. Questions or requests: support@untrap.app.