Permissions Explained

Understanding what permissions CleanLink Pro needs and why

CleanLink Pro requests only the minimum permissions necessary to function. Here's exactly what we need and why:

Permission Breakdown

Detailed Explanations

Clipboard Access

clipboardRead and clipboardWrite

These are the core permissions for CleanLink Pro's functionality:

• Read: Detect when you copy a URL so we can clean it
• Write: Copy the cleaned URL back to your clipboard

Without these, the extension cannot function.

Storage

storage

Used to save:

• Your cleaned link history (locally)
• Your settings and preferences
• Sync settings across devices (optional, via Chrome account)

All data is stored on your device. We never send data to external servers.

Tab Access

activeTab

When you copy a URL, we need to know the page title to save with your link. This permission lets us read the title of the current tab.

We only access the active tab when you copy a URL - not constantly.

Scripting

scripting

Allows us to inject the clipboard monitoring script into pages. This is how we detect URL copies across all websites.

The script only monitors clipboard events - it doesn't read page content.

Offscreen Documents

offscreen

Chrome extensions need a DOM context for certain clipboard operations. The offscreen permission lets us create a hidden document for this purpose.

This runs in the background and uses minimal resources.

Host Permissions

<all_urls>

To clean URLs from any website, we need access to all sites. This is used only to:

• Run clipboard monitoring
• Extract page titles

We do not:

• Read page content
• Track your browsing
• Modify web pages
• Send data anywhere

Privacy Commitment

Despite having broad permissions, CleanLink Pro:

• Never sends data to external servers
• Never tracks your browsing activity
• Never collects analytics
• Never displays advertisements
• Never shares data with third parties

All processing happens locally on your device.

Verify Yourself

You can verify our privacy claims:

1. Check network activity in DevTools (you'll see zero external requests)
2. Inspect chrome.storage.local to see exactly what's stored
3. Monitor the extension's behavior with Chrome DevTools

Questions?

If you have concerns about permissions, contact us via the Chrome Web Store support page and we'll be happy to explain further.