Privacy Policy — InfiniteScan
How InfiniteScan handles camera images, documents, OCR text, local history and optional network features.
1. Who we are
InfiniteScan is developed by Infinite IT Company (infiniteitbd.com). Support: support@infiniteitbd.com.
2. Local use and optional accounts
InfiniteScan does not require an account, sign-in, or registration. Local scanning, on-device OCR and local backup remain available without a subscription. Paid cloud backup is unavailable in this release and is not included in the annual ad-removal subscription. Optional account features depend on separately available, configured OIDC identity services. Where those services are available, the app does not store your account password and refresh tokens use platform encrypted storage.
3. On-device processing
- Camera frames are analyzed locally (ML Kit) to detect codes and are not stored as photos by default.
- Decoded payloads may be saved in local history if you enable History.
- Settings and ad frequency caps are stored in local preferences.
- Explicitly saved documents retain page images, originals, edits and reviewed text in app-private storage. Saved contact, math, counter, color and ID results retain structured details. ID saves ask for confirmation of sensitive identity fields; capture photos are omitted.
4. Network use and SDK metrics
- Product and book lookup: when requested, only the selected product code or ISBN is sent to Open Food Facts or Open Library.
- Printed-text OCR: when a private OCR service is configured, the selected image and language are sent over HTTPS only after confirmation. The service processes them in memory without retaining the image or extracted text. Bundled OCR provides an offline/error fallback. Automatic camera probe frames are not uploaded.
- ML Kit SDK metrics: Document scanning, code detection and supported on-device recognition process scan images, text and results locally. Google's ML Kit SDKs also send device/app information, installation or device identifiers, API configuration, feature-event and performance metrics to Google for diagnostics and usage analytics. Google states these metrics use HTTPS and are not transferred to third parties. This SDK telemetry is separate from scan content and is not disabled by Remove Ads.
- Optional account information: Sign-in depends on configured and available OIDC identity services. The identity service processes account identifiers (User IDs) and may include your name and email address in authentication-token claims. The app keeps refresh and ID tokens in platform encrypted storage; access tokens are held in memory and sent to the configured API for authentication. Local use does not require an account. New account registration and password recovery are unavailable in the current deployment.
- Document AI: Document AI is currently unconfigured in this deployment. The app checks availability and blocks reviewed-text and question submission while the service is unavailable. If enabled in a future deployment, only selected, reviewed text would be sent after separate confirmation; the operator would control the model and retention settings.
- Cloud backup: unavailable in this release and not included with ad removal. If a future release offers cloud backup, a separate opt-in would allow saved records and original document images to upload to the configured API. Storage would be encrypted at rest, not end-to-end: the operator would control the encryption key. Such a service would store opaque owner identifiers, revisions and entitlement metadata.
- Advertising and SDK startup: Eligible screens may show ads when ads are enabled and Remove Ads is inactive. Camera and sensitive review workspaces suppress ad display. UMP checks privacy choices at startup; when UMP permits ad requests, Google Mobile Ads may initialize even without a displayed ad. Removing or hiding ads does not itself disable these startup checks. Google Mobile Ads collects and shares identifiers, IP addresses (which may estimate approximate location), app interactions and diagnostics for advertising, analytics and fraud prevention, subject to applicable privacy controls. Settings exposes privacy options when available. Scan content is not sent to advertisers.
- Purchases: the optional annual Remove Ads subscription uses your Google Play account and provides ad removal only, subject to Play availability. It does not grant cloud storage or enable cloud backup. Purchase tokens and known product IDs are sent to the configured verification API. The server may retain encrypted purchase tokens and opaque account bindings for verification; a binding does not grant cloud access in this release. Payment details stay with Google. An unexpired verified local entitlement cache lasts at most 24 hours or until subscription expiry.
- Opening links, maps, phone, SMS, email, contacts, calendar, or Wi‑Fi settings uses Android intents you confirm. Dangerous schemes are blocked; unusual hosts (e.g. raw IP) get an extra warning. Wi‑Fi QR codes never auto-join — you copy details and connect manually.
5. Permissions
- Camera — live scanning
- Photos / media — only when you pick a photo to scan
- Internet — optional lookup, configured OCR, AI and identity services, purchase verification, ads and user-confirmed external actions
- Advertising ID (AD_ID) — used by Google Mobile Ads, subject to applicable privacy choices and device advertising-ID controls.
6. Sharing
We do not sell scan history. We do not share customer scan payloads with advertisers. Google's SDK data handling is described in Section 4 and can occur without a visible advertisement.
7. Retention & deletion
Clear History or uninstall to remove local records. Cloud backup is unavailable in this release. This release does not provide an account or server-data deletion-request workflow. Clearing local History or uninstalling does not erase retained server copies, purchase-verification records or backups. Contact the deployment operator for information about retained records and applicable retention.
Settings → Backup & restore exports an unencrypted library archive with saved records, favorites, document images/originals, edits, reviewed text and structured results, including saved identity fields. Credentials, account bindings, settings and unsaved sessions are excluded. Anyone who can access this file can read its contents; choose a trusted storage location. Restore adds copies without overwriting existing records. This release does not upload restored copies to cloud backup. A future cloud-enabled release would require a separate opt-in before those copies could upload. Clearing History does not delete exported files or copies held by receiving apps: delete those separately.
8. Children
General utility app. Do not submit children’s personal data via scanned content you do not control.
9. Contact
Privacy questions: support@infiniteitbd.com