SnapAI Privacy Policy

Privacy Policy

This Privacy Policy explains how the SnapAI Chrome extension handles screenshots, local settings, billing verification, and optional AI features.

Last updated: March 15, 2026
Local-first screenshots
No automatic uploads

Summary

  • SnapAI stores screenshots locally by default.
  • SnapAI does not automatically upload screenshots.
  • SnapAI only sends data to remote services when you explicitly use optional paid, AI, or billing-related features.
  • SnapAI does not sell personal data.
  • SnapAI does not use or transfer user data for advertising, profiling, creditworthiness, or unrelated purposes.

Information SnapAI Handles

1. Screenshot and Website Content

When you capture a screenshot, SnapAI may process visible page content, selected areas, selected elements, full-page content, and desktop or window screenshot content when you choose desktop capture.

This information is used only to create, edit, copy, download, and manage screenshots requested by you. By default, screenshot data is stored locally on your device using browser storage.

2. Local Settings and Screenshot History

SnapAI stores settings locally, including theme preference, output format and quality, editor preferences, local screenshot history metadata, Pro verification state, and optional API endpoint configuration.

3. Billing Email and Subscription Data

If you use Pro billing features, SnapAI may handle your billing email address, subscription status, renewal status, renewal date, and provider customer or subscription identifiers returned by your configured billing backend.

This information is used only to verify whether Pro features should be enabled and to open checkout or billing management pages when you request them.

4. Optional AI Data

If you choose to use optional AI features, SnapAI may send user-selected screenshot content or OCR output to the AI provider endpoint you configure.

5. Optional API Keys

If you enter an API key for AI features, such as an OpenAI API key, SnapAI stores that key locally in extension storage on your device so it can be used for your requested AI actions.

How Information Is Used

SnapAI uses information only for screenshot-related purposes, including capturing screenshots requested by you, editing and exporting screenshots, storing screenshot history locally, verifying Pro access, opening checkout or billing management flows, and running optional OCR or AI features that you explicitly choose to use.

When Information Leaves Your Device

1. Subscription Verification and Billing

If you use Pro features, SnapAI may send your billing email and extension version to your configured subscription backend to verify Pro access, create a checkout link, create a renewal link, open a billing management link, or cancel and manage a paid plan.

If Razorpay or another payment provider is connected through your backend, payment processing occurs on that provider's hosted pages and under that provider's own policies. SnapAI does not collect or process card or bank credentials inside the extension UI.

2. AI Features

If you trigger an AI feature, SnapAI may send screenshot content, OCR text, or related prompt data to the AI endpoint you configured.

3. Local Development

Some development builds may use local test endpoints such as localhost. Those are for developer testing only and are not intended as production services.

What SnapAI Does Not Do

  • It does not automatically upload screenshots.
  • It does not collect browsing history beyond the content needed to perform a screenshot you request.
  • It does not collect passwords, card numbers, or bank details through the extension interface.
  • It does not sell user data.
  • It does not use user data for advertising.
  • It does not use user data for unrelated analytics or profiling.
  • It does not use user data to determine creditworthiness or lending eligibility.
  • It does not download and execute remote extension code.

Permissions and Why They Are Used

  • activeTab to capture the current page after user action
  • scripting to inject screenshot tools into the current page
  • storage to save local settings, local history, and Pro state
  • contextMenus to provide screenshot actions from right-click menus
  • downloads to save screenshots and exported files
  • desktopCapture to capture a screen, window, or tab selected by the user
  • offscreen to stitch and process screenshots locally
  • clipboardWrite to copy screenshots or extracted text when requested
  • unlimitedStorage to keep local screenshot history on-device

Data Retention

  • Local screenshots and settings remain on your device until you delete them, clear history, or remove the extension.
  • Billing verification data stored locally remains until you clear it or remove the extension.
  • If you use a self-hosted or third-party backend, retention on that backend is controlled by the operator of that service.

Security

SnapAI is designed to minimize data transfer by keeping core screenshot functionality on-device. When remote services are used, requests are made only for user-requested billing, subscription, or AI actions, and production services should use HTTPS.

Your Choices and Controls

  • Use the extension without enabling optional AI features
  • Keep screenshots stored locally only
  • Delete individual screenshots from local history
  • Clear all local screenshot history
  • Clear saved billing email or Pro verification state
  • Choose whether to configure external AI or subscription endpoints
  • Remove the extension at any time
Before publishing, replace the placeholder contact information in this page with your real support email and website.

Children's Privacy

SnapAI is not directed to children under 13, and we do not knowingly collect personal information from children through the extension.

Changes to This Policy

This Privacy Policy may be updated when SnapAI features or data practices change. The latest version should be published at the privacy policy URL associated with the extension listing.

Contact

Before publishing, replace this section with your real support contact information.

  • Support email: support@your-domain.example
  • Website: https://your-domain.example