Privacy Policy

Last Updated: July 15, 2026

Local-First Commitment: AI Hub does not maintain remote user accounts, harvest chat transcripts, or store user database profiles. All session cookie values, prompts, and settings configurations are handled locally on your own machine.

At Ofici Labs, we are dedicated to developing deliberate, lightweight utility software for digital power users. This Privacy Policy outlines exactly how the AI Hub browser extension (the "Extension") handles, secures, and interfaces with your data.

1. Data Inventory & Storage Architecture

Because the extension utilizes a local-first design, data sits securely within your local browser database sandbox:

Data Type	Storage Location	Encryption (Transit)	Encryption (At Rest)	Retention
Workspace Cookies (Credentials)	Local `chrome.storage.local`	N/A (Local Swap)	Plaintext (Chromium DB)	Until deleted by user
Prompt Snippets	Local `chrome.storage.local`	N/A (Local Only)	Plaintext (Chromium DB)	Until deleted by user
Broadcast Prompts	Local `chrome.storage.local` (Draft)	N/A (Local Only)	Plaintext (Chromium DB)	Cleared on broadcast
Rate Limit Cooldowns	Local `chrome.storage.local`	N/A (Local Only)	Plaintext (Chromium DB)	Auto-deleted on expiry
License Validation Key	Local `chrome.storage.local`	Encrypted (HTTPS/TLS)	Plaintext (Chromium DB)	Until deactivated

2. Network Communications & API Outflows

The extension contacts external services in only two specific scenarios:

License Verification Check: When you input a Pro activation license key, the extension sends the key via secure HTTPS (TLS 1.3) to our Cloudflare Worker verifier endpoint at ai-hub-license-verifier.srs-felipe-ml.workers.dev. The worker queries our billing partner, Lemon Squeezy, and returns only a validation status. It does not record or save your IP address or key details.
Anonymous Error Telemetry: If enabled in settings, the extension will send sanitized exception logs (error message, stack trace, and target AI site ID) to our verification endpoint. The log helper automatically filters out and masks credentials, emails, prompts, and license keys before transmitting. Users can fully disable this in settings at any time.

3. Browser Permissions Requested & Purpose

AI Hub requests permissions strictly for functional execution:

Optional cookies permission: Requested dynamically when you activate workspaces. Used solely to clear and restore session cookies of targeted AI domains in order to separate account container setups.
tabs permission: Used to check URL domains to identify if an AI tab is already open, preventing opening multiple duplicate tabs.
scripting permission: Enables the quick broadcast component to autofill your typed prompt into the text areas of target AI tabs. It does not hit the "Submit" button automatically.
alarms permission: Operates low-overhead local alarms to clean up expired rate limit badges.

4. Billing & Payments

Payments for AI Hub Pro licenses are processed securely by our billing gateway, Lemon Squeezy (acting as the Merchant of Record). For card transactions, refund requests, or payment disclosures, please refer to the Lemon Squeezy Privacy Policy.

5. Recommended Security Hygiene

Because Chrome extension storage (`chrome.storage.local`) is stored plaintext at rest on your hard drive, we strongly recommend that users secure their devices with full-disk encryption (such as BitLocker on Windows or FileVault on macOS) to prevent local session harvesting in case of physical theft or local device intrusion.