Privacy Policy — Credential Hub & Credential Cookies

verified_user 1. Our Commitment & Single Purpose

At Credential Hub (including the Credential Cookies browser extension and desktop utilities), your privacy and data autonomy are fundamental principles. We operate strictly on a Zero-Knowledge and Local-First architecture.

Single Purpose: Credential Hub and the Credential Cookies extension are designed solely to empower individuals, developers, and teams to inspect, manage, store, export, and synchronize their authentication credentials, session tokens, and HTTP cookies securely.

Zero Knowledge Guarantee: Your passwords, authentication tokens, and cookie values are encrypted on your local device before transmission. We cannot read your master passwords, view your vault secrets, or inspect your private session tokens.

extension 2. Credential Cookies Browser Extension Disclosures

The Credential Cookies Chrome extension (Manifest V3) operates locally within your browser environment. It gives developers full visibility and control over web cookies and session tokens.

How Cookie Data is Processed

Local Sandbox Processing: Cookies displayed in the extension are read directly from the browser's native Cookie API. They reside in your local machine's memory and are never sent to external tracking servers.
User-Controlled Vault Sync: Synchronizing session tokens with your Credential Hub vault occurs strictly upon your explicit user action (e.g. clicking "Save to Vault"). All transferred data is encrypted and tied to your authenticated vault.
File Downloads: Browser-wide exports (JSON, Netscape, Header string) trigger direct local downloads to your machine's Downloads folder without routing through any intermediary servers.

Permissions Declared in Manifest V3 & Justifications

Permission	Purpose & Justification
`cookies`	Required to read, create, modify, and delete HTTP cookies for the active domain as directed by the user.
`tabs`	Required to detect the active tab URL and domain so the extension displays only the relevant cookies for that tab.
`storage`	Required to store user preferences (e.g., dark theme, export format) and vault authentication state locally.
`sidePanel`	Required to allow developers to dock the cookie editor in Chrome's native Side Panel for persistent monitoring.
`unlimitedStorage`	Required to prevent quota errors during large browser-wide cookie exports and imports.
`scripting`	Required to coordinate session token synchronization between the active tab and the local extension context.
`host_permissions (<all_urls>)`	Required because a developer cookie manager must be able to inspect and modify cookies on any website or localhost domain being tested.

block 3. Information We Do NOT Collect

We do not collect, transmit, or monetize your personal information:

No Personal Identifiable Information (PII): We do not collect names, phone numbers, government IDs, or contact lists.
No Browsing History: We do not log the websites you visit, search queries, or browsing timestamps.
No Keystroke Logging: We do not monitor mouse position, clicks, or keystrokes outside of direct inputs into our interface.
No Analytics Trackers: We do not embed Google Analytics, Facebook Pixels, or third-party behavioral trackers into our extension or core vault.
No Data Selling: We never sell, rent, trade, or monetize your data to data brokers, advertisers, or third parties.

lock 4. Security & Cryptographic Standards

Security is deeply engineered into Credential Hub:

Client-Side Cryptography: Vault secrets are encrypted with industry-standard AES-GCM (256-bit) and Argon2/PBKDF2 key derivation.
No Remote Code: In accordance with Chrome Web Store policies, all extension logic, stylesheets, and assets are packaged locally. Zero remote code or eval() scripts are executed.
End-to-End TLS: All network communication with Credential Hub services uses TLS 1.3 encryption.

admin_panel_settings 5. User Rights & Data Control

You maintain complete ownership of your credentials and data at all times:

Export at Any Time: You can export all your stored cookies and vault credentials in standardized formats (JSON, Netscape, CSV).
Instant Deletion: Deleting a cookie or vault item removes it permanently. You can delete all cookies browser-wide with a single button.
Account Deletion: You may request complete account deletion at any time, wiping all server-stored encrypted blobs.

contact_support 6. Transparency & Contact Information

Credential Hub and Credential Cookies are developed transparently. For any privacy inquiries, audits, or support requests:

Website: https://credentialhub.kaywat.codes
Credential Cookies Repository: github.com/itsKayWat/Credential-Cookies_crx
Credential Hub Issues: github.com/itsKayWat/Credential-Cookies_crx/issues
Developer Profile: github.com/itsKayWat