ChatSnapAI logoChatSnapAIA JBR Collection product
Get ChatSnapAI
Back to ChatSnapAI ChatSnapAI
Privacy policy

Local-first by architecture.

Effective August 31, 2026 · This policy covers the ChatSnapAI website and browser extension distributed for supported browsers, including Google Chrome and Microsoft Edge.

The short version: ChatSnapAI processes AI conversation content locally on your device and does not send that conversation content to ChatSnapAI servers. Pro licensing uses a separate network path for license/device metadata. If you voluntarily use the website support form, the information you type into that form is sent to ChatSnapAI so we can respond. ChatSnapAI does not use conversation content or support submissions for advertising or profiling.
ON YOUR DEVICEConversation content
  • Privacy Scan
  • Redaction
  • Export generation
  • Backups & notes
stays local
SEPARATE DATA PATHSNo conversation content in licensing requests
LICENSING SERVICEEntitlement data
  • License key
  • Generated device ID
  • Optional device label
  • Signed entitlement
license only

1. Conversation content processed on your device

When you use ChatSnapAI, the extension reads the supported AI conversation in the page you are viewing so it can scan, format, redact, export, and back it up. Those conversation-processing operations happen locally in your browser.

  • Conversation content: messages in the AI chat you choose to work with.
  • Sticky Notes, Prompt Library entries, and settings: stored locally in browser extension storage.
  • Draft Guardian: can locally save unsent text you type into a supported AI chat composer so it can be restored after a refresh or reload.
  • Backups and exports: stored in extension storage or written to files on your own device, depending on the feature you use.

Depending on what is present in the conversation or text you choose to process, this local processing can involve personally identifiable information, health information, financial or payment information, authentication information, personal communications, and website content. ChatSnapAI does not send those conversation-derived categories to ChatSnapAI servers as part of its conversation-processing features.

ChatSnapAI's conversation-processing features do not transmit your conversation text to ChatSnapAI servers.

2. Licensing and subscription validation

If you activate ChatSnapAI Pro, the extension contacts the ChatSnapAI licensing service to confirm entitlement. Depending on the action, the request can include:

  • Your license key.
  • A generated device identifier used to manage device activations.
  • During activation, an optional short device label.

These licensing requests do not contain AI conversation content, Sticky Notes, prompts, exported files, or backup contents. Entitlement responses are signed so the extension can validate cached Pro access locally.

3. Website support form

If you choose to submit the support form on chatsnapai.com, ChatSnapAI receives the information you voluntarily enter, such as your name, email address, support category, AI platform, subject, optional ChatSnapAI version, issue description, and expected behavior. You may optionally attach up to three screenshots in PNG, JPG, or WebP format. ChatSnapAI attempts to re-encode and, when needed, resize screenshots locally before submission so the processed support copy—not the original file—is transmitted when local preparation succeeds.

Support-form submissions, including any optional processed screenshots you choose to attach, are transmitted over the network to ChatSnapAI's website support function and delivered through Resend, our transactional email provider, to the appropriate ChatSnapAI role mailbox. Your email address is used as the reply-to address so the support team can respond. Technical requests route to Support; billing and licensing requests route to Billing; privacy requests route to Privacy; security reports route to Security; legal requests route to Legal; and general product questions route to Hello.

Please do not submit passwords, API keys, medical records, financial account details, or private AI conversation content through the support form or screenshots. Crop or redact unrelated sensitive information before attaching an image. Support submissions may be retained as needed to answer your request, prevent abuse, maintain support records, and meet legal or accounting obligations.

4. Optional AI-platform requests

Some platform-specific features may request conversation history from the AI service you are already using—for example, a ChatGPT history-loading feature intended to retrieve a complete conversation. Those requests are made in the context of that AI platform. They are not uploads of your conversation to ChatSnapAI's licensing service.

5. Payments

Paid subscriptions use Stripe-hosted checkout and payment services. Payment details entered at checkout are handled by Stripe under its own policies. The browser extension does not receive or store your card number or other full payment credentials.

6. What ChatSnapAI does not do with conversation content

  • We do not collect or store your AI conversation content on ChatSnapAI servers.
  • We do not sell conversation content or use it for advertising, profiling, credit, or lending purposes.
  • The extension does not require advertising telemetry or conversation analytics to provide its core features.
  • We do not request general browsing-history access in order to operate ChatSnapAI.

7. Permissions and why they are needed

Access to supported AI chat sites — ChatGPT, Claude, and Gemini domains are required so the extension can read the conversation on the page where you use ChatSnapAI.
activeTab / scripting — used to interact with the active supported page when a feature requires page access.
downloads — used to save exports and backup files you request.
storage / unlimitedStorage — used for local preferences, Sticky Notes, prompts, backup data, and entitlement state.
contextMenus — used for supported user-initiated right-click actions.
alarms — used for scheduled Pro entitlement revalidation. The alarm does not process or transmit conversation content.

8. Remote code

The browser extension package contains the code it executes. ChatSnapAI does not download or execute remotely hosted JavaScript or WebAssembly to replace the extension's packaged application logic. Network responses used for licensing or first-party AI-platform history recovery are treated as data, not executable extension code.

9. Retention and your control

Local conversation-derived data remains under your control on your device. You can remove locally stored extension data through ChatSnapAI or your browser. Subscription, license, device-activation, purchase, and operational records may be retained by ChatSnapAI and its service providers as needed to operate subscriptions, prevent abuse, provide support, and meet legal or accounting obligations.

10. Your rights

Depending on your location, applicable privacy laws may give you rights relating to personal data held by ChatSnapAI or its service providers. For privacy requests involving subscription or license records, contact chatsnapai-privacy@jbrcollection.com.

11. Children

ChatSnapAI is a productivity tool for general audiences and is not directed to children under 13 or below the applicable minimum age of digital consent.

12. Browser extension store data-use commitments

ChatSnapAI is designed to use information accessed through the extension only to provide disclosed, user-facing product features. Its data use is intended to remain consistent with the user-data and Limited Use requirements of the Chrome Web Store and the applicable privacy and data-use requirements of Microsoft Edge Add-ons. ChatSnapAI does not sell extension user data, use it for unrelated purposes, or use it to determine creditworthiness or for lending.

13. Changes and contact

If the extension's data practices change, this policy will be updated with a revised effective date. Privacy questions can be sent to chatsnapai-privacy@jbrcollection.com.