📄 Legal Document

Privacy Policy

📅 Effective date: April 13, 2026
✏️ Last updated: April 13, 2026
⚖️ MIT License
🔒

The short version

Vibe Code Detector collects zero data. No personal information, no browsing history, no page content is ever collected, stored, or transmitted. All analysis runs entirely inside your browser. Nothing ever leaves your device.

On this page
📊
01

What data is collected?

No personal data

We do not collect your name, email, IP address, or any identifier.

No browsing history

We never record which URLs or websites you visit.

No page content

Page HTML, scripts, and DOM data are analyzed in memory and immediately discarded.

No analytics

No telemetry, crash reporting, or usage analytics of any kind.

In plain terms: we collect nothing. The extension is purely a local analysis tool.

🔑
02

Permissions requested

The extension requests the minimum permissions needed to perform local page analysis.

🗂️
activeTab

Grants temporary access to the currently active tab only when you click the extension icon. No background access to any tab is ever granted.

💉
scripting

Allows the extension to inject the analysis script into the active page. The script reads DOM attributes and class names locally — no data is sent anywhere.

These permissions are standard requirements for any browser extension that performs page inspection. They do not grant any persistent access or cross-origin capabilities.

🖥️
03

Local processing guarantee

Every part of the detection pipeline runs entirely inside your browser:

🔍
Heuristic analysis

DOM scanning, class counting, attribute detection — all happens in-memory inside the content script running on your device.

📊
Score computation

The weighted scoring algorithm runs locally and produces a result shown directly in the popup. No external API is called.

🗑️
Data discarded immediately

All intermediate data (class lists, DOM snapshots, attribute sets) exists only for the duration of the analysis and is never persisted.

The extension makes zero network requests of its own. You can verify this with any browser DevTools network inspector.

🔗
04

Third-party services

The extension itself does not integrate with any third-party service.

The documentation pages (the pages you are reading now) load fonts from Google Fonts for display purposes. This is a standard web practice — Google Fonts does not receive any extension-specific data, only a standard font request from your browser.

The extension's source code is hosted on GitHub. If you visit the repository, GitHub's standard privacy policy applies.

👁️
05

Open-source transparency

Vibe Code Detector is fully open source under the MIT License. You do not have to trust this policy — you can read every line of code that runs on your device.

The complete source is available at github.com/paladini/vibe-code-detector. The relevant files for privacy review are:

📄
extension/content.js

The content script injected into pages. Contains all detection logic — no network calls.

📄
src/lib/vibe-detector.ts

The TypeScript source of truth for all heuristics. Mirrors content.js with full type safety.

📄
extension/manifest.json

Declares all permissions and host access. You can verify the minimum-permission scope here.

🔄
06

Changes to this policy

If this Privacy Policy is ever updated, the new version will be published in this repository and the effective date at the top of this document will be updated accordingly.

Any meaningful change that affects user privacy will be communicated via a GitHub release note. Given the nature of this extension — a local, zero-data tool — significant changes are not anticipated.


💬
07

Contact

For questions or concerns about this Privacy Policy, please get in touch via GitHub.

👤

Fernando Paladini

Author & maintainer of Vibe Code Detector