At SnapTextify, we are committed to protecting your privacy. This Privacy Policy explains how we collect, use, and protect your information when you use our Chrome Extension and associated services.
We respect your data privacy. The core functionality of SnapTextify—including capturing screenshot coordinates and performing Optical Character Recognition (OCR)—runs fully offline inside your local browser context using local WebAssembly (Tesseract.js). We do not send your captured images, text selections, or extracted prompts to any remote server for processing. To establish complete transparency for security auditors, we have open-sourced our core offline OCR WebAssembly execution setup on GitHub: SnapTextify Core PoC.
When you purchase a license key, we collect minimal personal information to manage your access:
Your license credentials and activation statuses are stored securely inside the Extension's Chrome Storage API locally, and synced securely using SSL/TLS encryption to our backend hosted on Supabase databases. We do not store or transmit financial information—all payments are securely processed by Razorpay, which complies with strict banking security standards.
Our website utilizes Razorpay to handle payments. Their collection and use of your payment details are governed by their respective Privacy Policies.
We may update this Privacy Policy from time to time. We recommend checking this page periodically to remain informed of how we protect your data.
If you have any questions or feedback regarding this Privacy Policy, feel free to contact us at: support@snaptextify.com
We believe in absolute transparency. Unlike cloud-based OCR products, SnapTextify runs entirely locally inside your browser. You can audit and verify this yourself at any time by following these steps:
Our extension's manifest.json permissions do not request access to read full system details or intercept network calls. The code complies fully with the Chrome Web Store's program policies, and all operations execute without background tracking or outbound telemetry (as there is none).