Privacy Policy
Summary
Offline OCR is designed to give users a clear choice between local OCR and optional Cloud AI. Local OCR is intended for everyday recognition on your device. Cloud AI is an optional advanced mode for complex formulas, dense layouts, handwriting, and math assistance.
This Privacy Policy explains how we handle OCR processing, account information, subscriptions, payments, support messages, analytics, and data deletion requests.
OCR processing modes
Local OCR
When you use local OCR mode, recognition is designed to run on your device for everyday OCR tasks. This mode is intended for users who want routine scans, notes, worksheets, and documents to stay local.
Optional Cloud AI
Cloud AI is an optional advanced recognition mode. You may choose it for complex formulas, difficult handwriting, dense page layouts, math-solving assistance, or cases where local OCR is not accurate enough. Cloud processing may require uploading the selected image or document content for processing.
Your choice
You can choose which recognition mode to use based on the document. Use local OCR for private everyday scans. Use Cloud AI only when you want advanced recognition.
1. Introduction
This privacy policy applies to the Offline OCR app (io.github.lingyunzheng.ocr). We respect your privacy and are deeply committed to protecting it. To provide you with both maximum privacy and advanced recognition capabilities, our application operates using a dual-engine architecture featuring a secure local offline mode and an advanced, opt-in cloud mode.
2. Permissions We Request & Data Handling
Camera (android.permission.CAMERA)
Purpose: Used solely to capture images of documents or math formulas for recognition and extraction.
On-Device AI Mode (Default): When using our local AI models, Optical Character Recognition (OCR) processing for everyday recognition is designed to run on your device's hardware. Your images, documents, and recognized text are not uploaded for routine local OCR tasks, supporting a private local workflow.
Cloud Assist Mode (Optional): When you explicitly choose Cloud AI, selected images or document content are uploaded over HTTPS for recognition by Google Gemini / Vertex AI or Baidu AI Studio PaddleOCR. Cloud AI requires readable content and is separate from E2EE Cloud Sync. We do not sell this content or train our models with it. Provider terms and retention policies apply.
Internet (android.permission.INTERNET)
Purpose: Internet access supports optional Cloud AI, authentication, subscriptions, Cloud Sync, support, and Google AdMob advertisements. Routine local OCR does not upload your documents.
Usage Data & Fraud Prevention
For users utilizing the subscription or Cloud features, we temporarily log basic usage metrics (such as request timestamps and token consumption) strictly for the purposes of quota management, billing reconciliation, and enforcing our Fair Use policy. We analyze this metadata to detect and block malicious activities, automated bots, and abuse of our reward systems.
3. Third-Party Services & Data Collection
We use trusted third-party services to enhance app functionality and support development:
- Secure Cloud Processing Engine: Cloudflare Workers route cloud requests; Cloudflare R2 stores optional Cloud Sync archives. When you submit our contact form, Formspree receives your name, email, subject, and message. E2EE protects enabled Cloud Sync content, not content you submit to Cloud AI or support.
- Web Payment Processing (Authorized Reseller): For users who purchase subscriptions or credits through our website, payment processing is handled securely by our authorized online reseller and Merchant of Record. The reseller collects billing details (such as email, billing address, and payment card information) necessary to process the transaction and comply with global tax regulations. We do not store or have access to your full credit card numbers; we only receive anonymous transaction statuses and purchase tokens linked to your account ID to provision your Plus or Pro features. You can view the reseller's privacy practices on their official website.
- Google Play Billing: We use Google Play to process "Pro" or "Plus" subscriptions securely. We do not collect, process, or have access to your credit card information. We only store an anonymous purchase token linked to your account ID to verify your active subscription status across devices.
- Apple In-App Purchase: On iPhone, iPad, and Mac, Apple processes App Store subscriptions and credit purchases. We do not receive your full payment-card details; we receive purchase and entitlement information needed to activate and restore the product you bought.
- Firebase Authentication (Apple and Google): You may sign in with Apple or Google to restore subscriptions and credits across supported devices. We receive basic identifiers and profile information authorized by you and the provider. Apple and Google sign-ins are treated as separate accounts and are not automatically merged merely because they expose the same email address.
- Firebase App Check (Device Integrity): To protect our backend infrastructure from abuse, bots, and unauthorized access, we utilize Firebase App Check. This service collects basic device and network information to verify that requests are coming from a legitimate, unmodified version of our application on a physical device.
- Google AdMob: This service may collect and use data such as your Device ID, Advertising ID, and IP address to provide personalized or non-personalized advertising, analytics, and fraud prevention. For more information, please visit: Google Privacy & Terms.
- Google API Usage Policy: Our application's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use user data obtained through Google APIs to develop, improve, or train generalized AI and/or ML models.
End-to-End Encrypted Cloud Sync & Local LAN Transfer
Optional Cloud Document & Formula Sync (Zero-Knowledge E2EE, offlineocr.e2ee.v1): Cloud Sync is optional. When you enable E2EE with your Sync Passphrase and Recovery Key, .ocrdata archives, document titles, and saved formulas are encrypted on your device with AES-256-GCM before upload. Servers store ciphertext and wrapped key envelopes (PBKDF2-HMAC-SHA256, 600,000 iterations), never your passphrase or plaintext encryption keys.
Local Wi-Fi / LAN Transfer (ocr-lan-v2): Transfers between your devices are peer-to-peer and start only when you open the LAN transfer dialog and authenticate with a short-lived pairing code or QR code. ChaCha20-Poly1305 provides authenticated encryption.
Account, payment, and support data
OCR processing data is different from account, subscription, payment, support, and analytics data. If you create an account, subscribe, contact support, or purchase through a payment provider, we may process the information required to provide those services, manage your subscription, respond to requests, prevent abuse, and comply with applicable requirements.
4. Children's Privacy (COPPA)
These Services are not directed at individuals under the age of 13. We do not knowingly collect personally identifiable information from children under 13. If you are under 13, please do not use the Cloud Assist Mode or the subscription features of this App. If we discover that a child under 13 has provided us with personal information via the cloud features, we will immediately delete this from our servers.
5. Data Retention & Account Deletion
You may request the deletion of your account and associated data at any time via the in-app settings. After requesting account deletion, you have 30 days to cancel the request. If you do not cancel within 30 days, your usage history and account data will be permanently erased from our active databases.
Security Exception: Please note that if an account is suspended or terminated due to a violation of our Terms of Service (such as fraudulent billing or API abuse), we reserve the right to securely retain minimal, hashed identifiers (such as a generic user ID or device token) on a permanent blocklist. This is strictly necessary to protect our platform and prevent the offending user from circumventing the ban.
6. Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page. You are advised to review this Privacy Policy periodically for any changes.
7. Contact Us
If you have any questions, concerns, or requests regarding this privacy policy or your data, please contact us directly at: offlineocr.service@outlook.com
Last Updated: November 22, 2026