Privacy policy
ReelLess does not collect, transmit, sell, or share personal information. It has no analytics, advertising, tracking pixels, remote code, accounts, or external network requests.
What is processed
On sites the user enables, ReelLess scripts inspect the current page URL and specific local page elements and links needed to find Shorts, Reels, and other selected entry points. If the user starts the optional Ultimate Lock release ritual, the reflection remains only in the open Settings page and is discarded when it closes or reloads. ReelLess does not transmit or store that reflection, URLs, page contents, video titles, account details, messages, comments, cookies, or browsing history.
What is stored
ReelLess stores settings, section choices, pause and schedule state, optional Ultimate Lock state, custom entries, first-run state, an active-day count used only to delay the neutral review prompt, and a daily/all-time count in Chrome’s local storage. The count contains only {localDay, todayCount, totalCount}. No URL, title, or platform history is retained.
Site access and permissions
YouTube, Instagram, Facebook, and TikTok are included. Seven Advanced sites and custom domains use optional HTTPS access requested from a user action. Storage saves local settings and counts; alarms refresh schedules; scripting registers granted Advanced guards; declarativeNetRequestWithHostAccess blocks user-added custom destinations after access is granted.
Contact
Open a privacy question through GitHub Issues.