Privacy policy

Extension is only available in Danish

NyviaNexus is built on a "bring your own database" (BYOD) architecture. This means your privacy is structurally guaranteed. NyviaNexus literally cannot access any of your data.

Last updated: February, 2026

1. Your data, your database

NyviaNexus does not use any central servers to process, store, or transmit your browsing data. All your tabs, workspaces, notes, and archives are synced directly from your browser to your personal Google Firebase project. You have 100% ownership and control over your data.

2. Unencrypted data & security rules

Data stored in your connected Firebase database is saved in plain text (unencrypted). The security of your data relies entirely on the Firebase security rules set up in your Google Firebase project. It is your responsibility to ensure that read and write access is restricted exclusively to you as the authenticated user.

3. Local storage

UI preferences, cache, and API keys are stored locally on your device using Chrome's secure local storage API. This data never leaves your device unless it is being synced directly to your own Firebase instance or sent to your configured AI provider.

4. AI categorization (optional)

If the optional AI sorting feature is enabled, the extension communicates directly with the Cerebras API. The extension sends the URL, title, and basic metadata of your tabs to Cerebras for categorization. NyviaNexus does not proxy this request.

As of today, Cerebras operates with a strict zero data retention policy for their API, meaning they do not store your inputs or use your browsing data to train their models. You can read more in the Cerebras privacy policy. Your API keys are stored locally and are never shared with anyone.

5. No tracking or analytics

NyviaNexus contains no trackers, no analytics, and no telemetry. The extension does not track your identity, the sites you visit, or your usage patterns. It operates completely silently on your machine.

Verification

NyviaNexus is an open-source project. To verify these privacy claims, you can inspect the source code directly on the GitHub repository.