Last updated: 25 October 2026

ReTrapper for YouTube is a browser extension that changes how YouTube looks and behaves. It has no accounts, no analytics, no advertising and no tracking. The developer does not run any server and does not receive any data from you.


Your settings (which options are on, page order, filters, backups and similar) are saved only in your browser's local extension storage. They are never sent anywhere. Backup codes are text you copy yourself.


Some features contact outside services. Nothing is sent unless the feature is used.

• YouTube (youtube.com): the extension reads YouTube pages you open, and requests pages such as your Watch Later playlist and subscriptions list, using your existing YouTube session, to show dates and lists. This is the same traffic your browser already sends to YouTube.
• Return YouTube Dislike (returnyoutubedislikeapi.com): when you open a video, the video's ID is sent to get the like and dislike counts. No account information is sent.
• DeArrow (sponsor.ajay.app and dearrow-thumb.ajay.app), only if the DeArrow option is on: a short hash of video IDs, and the ID of a video when a replacement thumbnail is requested, is sent to get community titles and thumbnails.

These services have their own privacy policies. ReTrapper does not send them your name, email, YouTube account details, cookies or watch history.


The bug report screen builds a report on your device. Nothing is sent automatically. If you choose to send it, it opens a draft in your own mail app and you press Send. The report contains your browser version, which options are on, layout measurements and recent page errors. It does not contain cookies, your account name or your watch history. Titles and names can be masked before you copy it.


For Firefox, ReTrapper declares "browsing activity" because the ID of the video you are watching is sent to the services above.


The extension is not directed at children and collects no personal information.


If this policy changes, the date above will be updated and the new version published with the extension.


Questions about this policy can be sent through the developer contact listed on the extension's store page.