Privacy Policy — SnapText OCR

TL;DR — The Short Version

We collect absolutely no personal data.
Your images never leave your device.
All OCR processing runs locally in your browser.
Scan history is stored only in Chrome's local storage, on your machine.
No servers, no analytics, no third-party trackers.

1. Overview

This Privacy Policy describes how Redan Ventures LLC, doing business as SnapTool Labs ("we," "us," or "our") handles information in connection with the SnapText OCR Chrome extension ("the Extension," "SnapText").

We built SnapText with a foundational commitment: your data is yours. The Extension is engineered to operate entirely on your local device, with no data collection, no user accounts, and no external communications of any kind.

2. Information We Do Not Collect

SnapText does not collect, transmit, store on our servers, or share any of the following:

Images you scan or process
Text extracted by the OCR engine
Your browsing history or visited URLs
Personal identifiers (name, email, IP address, device ID)
Usage analytics or telemetry
Crash reports or diagnostics
Any other data of any kind

SnapText makes zero network requests. There is no server. There is no database. There is no analytics pipeline. We have no way to see your data — by design.

3. Data Stored Locally on Your Device

SnapText uses Chrome's built-in chrome.storage.local API to save the following data on your machine only:

Scan history — The last 20 OCR results (text only, not the source images), stored so you can revisit recent extractions without re-scanning.
Theme preference — Whether you've selected light or dark mode.
Scan counter — A running count of scans performed today.

This data never leaves your browser. It is not synced to any cloud service (Chrome sync is not used). It can be cleared at any time by removing the Extension or clearing extension storage in Chrome's settings.

4. How OCR Processing Works

SnapText uses Tesseract.js, an open-source OCR library compiled to WebAssembly, which runs entirely inside your browser's JavaScript engine. This means:

Image data is processed in-memory, within the Extension's sandbox.
No image data is written to disk (beyond what your OS does for memory management).
No image data is sent to any external server, API, or service.
The OCR engine and language data (English) are bundled with the Extension and loaded locally.

Even in environments with no internet connection, SnapText works perfectly — because it has never required internet access to function.

5. Chrome Permissions Explained

SnapText requests the following browser permissions. Here's exactly why each is needed:

Permission	Why It's Needed	Data Accessed
`activeTab`	Captures a screenshot of the visible browser area when you use the Area Selection tool.	Current tab's visible pixels only, processed locally and immediately discarded.
`contextMenus`	Adds "Extract Text with SnapText" to the right-click context menu on images.	No data accessed — only registers a menu item.
`storage`	Saves scan history, theme preference, and scan counter to local browser storage.	Stored locally only. Never transmitted externally.
`clipboardRead`	Reads images you paste into the popup via Ctrl+V or the Paste Image button.	Clipboard image data processed locally and immediately discarded after OCR. Clipboard text is never read.

SnapText does not request permissions to read your browsing history, access all websites automatically, sync data, or communicate with external hosts.

6. Third-Party Services

SnapText uses the following open-source library, bundled inside the Extension package. No data is sent to the library authors:

Tesseract.js — OCR engine running as WebAssembly in your browser. License: Apache 2.0. Source: github.com/naptha/tesseract.js

There are no analytics services, advertising networks, crash reporters, or any other third-party integrations.

7. Children's Privacy

SnapText does not knowingly collect any information from anyone, including children under the age of 13. Since we collect no data whatsoever, no special provisions are required under COPPA or similar regulations.

8. Security

Because SnapText collects no data and makes no network requests, the attack surface is limited to your local device. The Extension follows Chrome's Manifest V3 security model, including a strict Content Security Policy that prevents code injection and unauthorized script execution.

If you discover a security vulnerability in SnapText, please report it responsibly by contacting us at the address below.

9. Changes to This Policy

We may update this Privacy Policy from time to time. If changes are material, we will update the "Last updated" date at the top of this page and, where feasible, provide notice through the Extension or the Chrome Web Store listing.

Our core commitment — that SnapText will never collect, transmit, or share your data — will not change.

10. Contact

If you have questions about this Privacy Policy or SnapText's data practices, please contact us via email:

SnapText OCR

Redan Ventures LLC, doing business as SnapTool Labs

Email: snap.tool.labs@gmail.com

Chrome Web Store listing: SnapText OCR