CleanTrail

Automatically delete cookies and block trackers for better privacy.

Protect your privacy. Stay in control. CleanTrail is a lightweight, privacy-first browser extension that reduces online tracking, removes unwanted cookies and site data, hardens against fingerprinting, and warns you about unsafe sites — all in a simple, easy-to-use interface. We design CleanTrail so core protections run locally on your device. Backend services are used where necessary (subscription & license management, cloud sync, community rule updates, and phishing checks). We never execute arbitrary remote code in your browser. Plans & Features Free — $0 / month Basic privacy protection for everyday browsing. - 3 Privacy Profiles: Strict, Balanced, Relaxed - Real-time tracker blocking (on-device) - Basic privacy score meter (A–D) - Manual cookie/cache cleanup - Optional auto cookie deletion for non-essential cookies - Community tracker list (receives updates from our backend) Pro — $4.99 / month Advanced protections and automation. All Free features, plus: - Paranoid & Custom profiles - Scheduled cleanup automation (alarms/back-end coordination) - Malicious tracker detection & blocking (enhanced rules delivered from server) - Persistent cookie alerts (detects cookies that reappear across sessions) - Advanced privacy analytics (local + enhanced Pro reporting) - Website trust management (save site trust decisions) - Cloud sync (standard) — sync settings and trusted sites across devices (Pro) - Fingerprinting detection (on-device detection, optionally reports aggregated signals) - Sync across up to 3 devices Pro+ — $9.99 / month Enterprise-grade security and strongest privacy posture. All Pro features, plus: - Script injection detection (server-updated heuristics + local checks) - Script tamper detection - Session hijacking detection - Phishing site protection (Google Web Risk + our checks) - Ultimate stealth mode — advanced anti-fingerprinting & entropy reduction - Advanced fingerprint spoofing (consistent spoofed values across reloads) - Encrypted cloud sync (AES-256; passphrase-based additional layer) - Sync across up to 5 devices - Passphrase-based extra encryption for Pro+ users What runs locally vs. what uses backend / third parties: Local (on-device) Real-time tracker blocking, cookie cleanup, fingerprinting detection, and most privacy protections. Local analytics (Top blocked trackers) and your blocking preferences. Backend & Third-party services (required for some features) Subscription & license management: our backend validates Pro status. Cloud sync & Pro+ encrypted sync: sync blobs are encrypted client-side before upload. We cannot read encrypted contents. Community tracker list & malicious tracker rule updates: server-delivered rule updates to keep blocking effective. You may opt out. Phishing protection: uses Google Web Risk API for up-to-date phishing/malware checks. Only URLs and verdicts are exchanged. Payments: processed by Stripe; CleanTrail never stores full card numbers. Permissions & data (brief & transparent) CleanTrail requests permissions required to protect you effectively (tabs, webRequest, cookies, browsingData, scripting, declarativeNetRequest, storage, alarms, downloads, activeTab). Key data touches: Web history (URLs) and user activity (request metadata, cleanup actions) — accessed to detect trackers, apply per-site rules, and present in-UI analytics. These are local by default. Tracker blocking behavior (which domains you block/allow/promote) — stored locally to remember your choices. If you enable Smart Sync / community feedback, anonymized and aggregated signals may be uploaded (opt-in). Pro & sync metadata — email and activation tokens for subscription management; encrypted sync blobs are unreadable by our servers. For full details, see our Privacy Policy and Terms of Service: Privacy Policy: https://github.com/YOUR_USER/cleantrail/blob/main/PRIVACY_POLICY.md Terms of Service: https://github.com/YOUR_USER/cleantrail/blob/main/TERMS_OF_SERVICE.md Why choose CleanTrail? Privacy-first architecture: core protections run locally. Flexible control: quick toggles for everyday users and deep customization for power users. Clear transparency: readable privacy policy and terms, and obvious settings to opt out of remote features. Layered protections: automated cleanup, fingerprinting mitigation, and phishing checks together reduce common tracking vectors. FAQ Q: Do you read my emails, messages, or collect GPS? A: No. CleanTrail does not collect personal communications or precise GPS location. Q: Do you sell my data? A: No — we do not sell personal data. Q: Can I use CleanTrail offline? A: Yes — core protections work offline. Disabling remote features disables sync, community updates, and Web Risk checks. Q: How do I delete my data? A: Use the extension settings to clear local data or uninstall. Pro users can request account and sync deletion via email. Q: What should I do if a website stops working suddenly? A: Some websites rely on third-party scripts that may be blocked. Try switching back to the base tracker list and clear blocked trackers for that site. You can also add the site to your trusted list if needed. Q: I can’t sign in to some services. What should I do? A: This may happen if auto-cookie cleanup is enabled, since it can remove login cookies. Disable auto-cookie cleanup and refresh the page — your login should work again. Getting started: Install CleanTrail from the Chrome Web Store. Click the extension icon to open the popup and enable quick protections. Visit the dashboard to configure trusted sites, profiles, and scheduled cleanups. Optional: upgrade to Pro or Pro+ to enable cloud sync, advanced analytics, and enhanced detection. Support & contact Questions, bug reports, or privacy requests? Contact us: businesscleantrail@outlook.com Terms of service: https://saasvetth.github.io/cleantrail-success-page/TERMS_OF_SERVICE.md Legal & licensing (brief) Use of CleanTrail is governed by our Terms of Service (link above). The extension is licensed for personal, non-commercial use only — copying, repurposing, or redistributing the source or binary is not allowed unless explicitly permitted.