Encrypted Clipboard

Open Source & Verification

Transparent, verifiable, and secure. Here's how you can prove our encryption works and verify we can't access your data.

@encryptedclipboard/crypto

Apache License 2.0 Dependency-free
View on GitHub View on npm

Dependency-free: Our encryption library uses only the browser's native Web Crypto API. No external dependencies means fewer attack vectors and easier verification.

Verify It Yourself

We believe security should never be a black box. Here's how you can verify our zero-knowledge claims:

1 Network Tab Inspection

  1. 01

    Right-click the extension icon and select Manage Extension.

  2. 02

    Enable Developer Mode and click on the service worker link under 'Inspect views'.

  3. 03

    Go to the Network tab.

  4. 04

    Copy some text — you'll see a request sent to our API.

  5. 05

    Inspect the payload: it contains only unreadable ciphertext. Your raw data never leaves your browser.

2 AI Code Analysis

Modern AI models can analyze minified Chrome extension builds and determine exactly what the code does. You can:

  1. 01

    Download the extension's source code from the Chrome Web Store (via CRX extractor or similar tools).

  2. 02

    Paste the minified code into ChatGPT, Claude, or any AI coding assistant.

  3. 03

    Ask: "Does this code send any clipboard content in plain text to any server? Does it steal user data?"

  4. 04

    The AI will confirm that our extension only sends encrypted data and never transmits your actual clipboard content.

Why Browser Extensions Are More Transparent

Unlike desktop or mobile applications that compile to unreadable binaries, Chrome extensions remain as JavaScript, HTML, and CSS files that can be inspected by anyone — including AI.

PlatformCode TypeHuman ReadableAI Scannable
Desktop AppBinary/Compiled❌ No❌ No
Mobile AppBinary/Compiled❌ No❌ No
Chrome ExtensionMinified JS⚠️ Partially✅ Yes

Our Extension: Un-minified Encryption Library

We've specifically disabled webpack minification for our encryption library in the build process. This means:

  • You can directly search for @encryptedclipboard/crypto in our extension's .js files

  • The library is imported and used in plain, readable code — not hidden behind minified blobs

  • Finding our encryption usage takes seconds, not hours of reverse engineering

How to Find Our Encryption Library in the Build

  1. 01

    Download the extension CRX file from the Chrome Web Store (using a CRX extractor tool).

  2. 02

    Extract the .zip and navigate to the folder containing the built JavaScript files.

  3. 03

    Open any .js file in a text editor or use grep/search.

  4. 04

    Search for encryptedclipboard/crypto, CryptoEngine, encryptData, or decryptData.

  5. 05

    You'll find the import statement showing exactly where and how we use our open source encryption library.

I believe in transparency with users, but as a solo founder, I can't afford the risk of having my hard work copied and rebranded by others. This isn't about hiding anything — my zero-knowledge encryption is verifiable as shown above. It's about protecting my business from competitors who might take my work and monetize it without any of the development effort.

The encryption core is open source because it builds trust. The full extension remaining proprietary is a business decision, not a concealment of malicious code.

Absolutely. I'm fully open to any official security team or independent researcher auditing my codebase. I've nothing to hide — my zero-knowledge architecture means I physically cannot access user data even if I wanted to.

As a solo founder, I can't currently afford formal paid security audits, but I welcome any volunteer security researchers to review the code. If you're a security professional interested in auditing our encryption implementation, please reach out.

Security Researchers & Partners

Interested in security research or partnership opportunities? We'd love to hear from you.

support@encryptedclipboard.app