1. Privacy overview
Remoover is an experimental project with account, dashboard, live proof, and optional payment-related flows. We try to keep data handling limited to what is needed for authentication, dashboard setup, supported features, analytics, and operation of the service.
2. Information you provide directly
Based on the signup and dashboard code, the project may collect information such as:
- username
- email address
- first name and last name
- password credentials stored through Django authentication mechanisms
- selected country and chosen plan
- billing address details if you enter them
- device descriptions and activation-related dashboard entries
- saved YouTube entries, image folders, schedules, favorites, blocked items, and country selections inside the dashboard
3. Technical and usage data
The project may also process technical information needed to run the site and dashboard, such as session data, login state, request metadata, and security or debugging information.
The shared site footer also includes Google Analytics code, which means analytics-related data may be collected according to Google's own technology and policies.
4. Dashboard and product-configuration data
The dashboard is designed to store configuration choices needed for Remoover features. That includes, for example:
- country selections used to filter channels and program searches
- saved YouTube videos used for ad-break replacement
- image folders and uploaded images
- favorite programs and channels
- blocked programs and channels
- Hop & Return preferences
- device settings such as ad-break behavior, delay, sound, and schedule choices
5. Live proof data
The Live Proof page is fed by websocket updates from the recognition service and shows channel-level status such as country, channel, company, category, and whether an ad break is currently detected. Based on the current code flow, this page is intended to show live recognition activity rather than personal user data.
6. Why we use information
We use collected information to operate the website and the dashboard, including:
- creating and authenticating accounts
- storing user preferences and dashboard configuration
- supporting device setup and schedule management
- displaying live proof and related service information
- processing plan, billing, or payment flows when available
- measuring usage and improving the project over time
7. Cookies, sessions, and analytics
The site may use cookies or similar mechanisms for login sessions, security, and basic site operation. It also currently includes Google Analytics in the shared footer, which may set analytics-related cookies or collect usage information.
8. Third-party services
The codebase references third-party services and ecosystems, including YouTube-related workflows, analytics, payment handling, and an IP geolocation helper used during signup. When those services are involved, they may receive limited information needed to perform their role.
Those third parties operate under their own privacy policies and terms.
9. Data sharing
We do not sell personal data. We may still share limited information with service providers or infrastructure partners where reasonably necessary to run the website, dashboard, authentication, analytics, payments, hosting, or security functions.
10. Data security and project limits
We try to handle data responsibly, but no system can promise perfect security. Because Remoover is experimental, security practices, infrastructure, features, and storage patterns may change over time.
11. Retention and deletion
We may retain account and configuration data for as long as reasonably needed to operate the project, maintain records, troubleshoot issues, or satisfy legitimate operational needs. Demo data may be reset or replaced at any time.
12. Policy updates
We may revise this Privacy Policy as the project changes. The latest version published on this page will apply going forward.