Privacy Policy

Last Updated:
Extension Version: 7.0.0
Contact: diptodesignstd@gmail.com

TL;DR - No Data Collection

Clify works 100% locally in your browser. No data is collected, stored externally, or sent to any servers. Your privacy is fully respected.

1. No Data Collection Policy

Clify is designed with privacy as a fundamental principle. We believe your browsing data should remain yours alone.

What We Don't Collect:

  • No browsing history - We don't track what you watch on YouTube
  • No personal information - We don't collect names, emails, or account details
  • No usage analytics - We don't track how you use the extension
  • No external communication - The extension doesn't phone home

2. Local Storage Only

All data generated by Clify is stored exclusively on your local device using your browser's storage systems.

What's Stored Locally:

  • Blocked videos list - IDs and titles of videos you've blocked
  • Custom keywords - Keywords you've added for automatic blocking
  • Extension settings - Your preferences (theme, language, etc.)
  • Usage statistics - Local counters showing how many videos you've blocked

This data remains on your computer and is never transmitted anywhere.

3. YouTube Access Permissions

Clify requires certain permissions to function properly on YouTube:

Required Permissions:

  • Access to YouTube.com - To modify the page and add blocking functionality
  • Local storage access - To save your preferences and blocked videos locally
  • Browser tabs permission - To detect when you're on YouTube

These permissions are standard for browser extensions and are used only for their intended purpose.

4. Open Source Transparency

Clify is 100% open source. You can:

  • Review all code on GitHub
  • See exactly what data is accessed and stored
  • Verify that no hidden tracking exists
  • Contribute to or modify the code yourself

Code Transparency

Since Clify is manually installed, you can inspect every file before installation. There are no hidden binaries or obfuscated code.

5. Third-Party Services

Clify does not use any third-party services, analytics tools, or tracking frameworks.

No Integration With:

  • Google Analytics or any analytics services
  • Advertising networks
  • Social media trackers
  • Data collection services

6. Manual Installation Safety

Since Clify is manually installed (not from Chrome Web Store), users have complete control:

  • You download the source code directly from GitHub
  • You can review all files before installation
  • You control when updates are installed
  • No automatic updates that could introduce unwanted changes

7. Your Control Over Data

You have full control over your data:

You Can:

  • View all stored data in the Clify dashboard
  • Export your blocked videos list at any time
  • Clear all data with one click
  • Uninstall the extension completely
  • Remove specific blocked videos individually

When you uninstall Clify, all locally stored data is automatically removed by your browser.

8. Updates to This Policy

If we make changes to this privacy policy (which would only happen if we add features that require different data handling), we will:

  • Update the "Last Updated" date at the top of this page
  • Clearly communicate any changes in the release notes
  • Never silently change how your data is handled

Since Clify doesn't collect data, changes to this policy would be rare and minor.

9. Contact Information

If you have any questions or concerns about this privacy policy, please contact:

Email: diptodesignstd@gmail.com

GitHub: Open an Issue

Telegram: @Clifybydd

10. Data Security

Since all data is stored locally in your browser:

  • It's protected by your browser's built-in security
  • It's not accessible to websites or other extensions
  • It's encrypted if your browser supports encryption
  • It's deleted when you clear browser data or uninstall

Summary: Your Privacy is Protected

Clify is designed to be the most privacy-respecting YouTube blocker available. We don't collect data because we don't need to - the extension works perfectly while keeping everything local to your browser.

Back to Home View Changelog