Privacy Policy

Last updated: June 15, 2026

ContextNode provides a prompt library, dashboard, public prompt discovery pages, and a browser extension for supported AI chat surfaces. This policy explains what user data ContextNode collects, how that data is handled and stored, and when it may be shared.

Data We Collect

Account data may include your email address, display name, profile image URL, authentication provider identifiers, password authentication metadata when password sign-in is used, billing entitlement metadata, and security information needed to protect your session.

Prompt library data may include prompt titles, prompt content, prompt variables, tags, folders, collections, workflow steps, shortcut text, cover settings, public/private status, version history, usage counts, and timestamps. If you use the browser extension context menu to save selected page text as a prompt, the selected text is stored as prompt content.

Extension data may include local prompt and workflow records, folder metadata, pending cloud sync queue entries, the optional cloud access token, theme and language preferences, panel position, favorites, recent prompts, dismissed notices, debug state, and other settings needed to operate the Node Bar. The extension does not collect browsing history in the background. It runs on supported AI chat surfaces and only uses page content when you insert prompt text into a composer or explicitly save selected text as a prompt.

How We Use Data

ContextNode uses this data to provide and improve the prompt library, dashboard, browser extension, public prompt discovery, prompt insertion, template variable filling, workflow execution, account authentication, cloud sync, billing entitlements, support, abuse prevention, security, diagnostics, and service reliability.

ContextNode does not use or transfer user data for personalized, retargeted, or interest-based advertising. User data collected by the extension is used only to provide or improve ContextNode features that are visible to the user.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Storage And Handling

The web app stores session tokens in browser sessionStorage under contextnode.accessToken. The browser extension stores local prompts, settings, sync state, and optional cloud access tokens in Chrome extension local storage. Local extension data remains on your device unless you enable cloud sync or otherwise choose to send it to the hosted service.

When cloud sync or account features are enabled, prompt, workflow, and account data is transmitted to the ContextNode API over HTTPS and stored by the hosted service. Authentication tokens are used to protect private account and operator workflows. Operational logs may be used to debug issues, maintain reliability, and protect against abuse.

ContextNode handles user data securely and keeps authentication, payment, and entitlement information private. Data is retained only for as long as needed to provide ContextNode features, meet legal and security obligations, resolve disputes, prevent abuse, maintain backups, or support user-requested export and deletion workflows.

Sharing

ContextNode does not sell personal data. Private prompt libraries are not shared with other users unless you choose a public or team sharing feature. Public prompts, public collections, and public workflows may be visible to visitors when you mark them public or publish them through ContextNode.

ContextNode may share data with service providers only as needed to run the product, such as hosting, database, authentication, email delivery, payment, security, analytics, or infrastructure providers. ContextNode may also disclose data when required by law, to investigate abuse or security incidents, or as part of a merger, acquisition, financing, or sale of assets after obtaining any user consent required by applicable law or Chrome Web Store policy.

Humans may access user data only when needed for support with your consent, security and abuse investigation, legal compliance, or aggregated and anonymized internal operations.

Your Choices

You can keep prompts local in the extension without enabling cloud sync. You can clear extension local data through your browser, sign out to remove the stored cloud access token, or delete prompts and workflows from the dashboard or extension where deletion controls are available.

Contact the project owner to request export, correction, or deletion of account or prompt data stored by the hosted service.