LAST REVIEWED · 10 OCTOBER 2026

Privacy, clearly.

iScan is an offline Android QR and barcode toolkit. This page describes the current implementation. iScan is available through Google Play closed testing. Access requires an eligible tester account; a public production release is not announced.

On-device scanning and generation

Camera frames and selected images are processed locally for barcode recognition. Scanning, generation and history do not require an internet connection. The Android app requests no internet permission and includes no ads, analytics, cloud synchronization or account system.

Local history can contain sensitive data

Scans and generated codes are saved by default in the app's local database, including raw content, code format, record type, time and optional title/style. Wi-Fi passwords, contact details and other personal content may therefore be present in history. Hiding a field in the UI does not remove it from the stored payload.

You can delete a record or clear history in the app. Clearing Android app data or uninstalling removes local app data. App backup is disabled; iScan does not provide a cloud restore service. Generated code images exported to your gallery or another destination remain there until you remove them separately.

Permissions and selected images

Camera permission is used for live scanning. Images are selected using Android's picker; export uses Android storage flows. iScan does not request broad storage, contacts, direct-call or location permissions. Coordinates in a QR code are payload content, not device location tracking.

Copy, share and external actions

Content is not opened automatically. When you copy, share, save an image or open another app, the chosen destination may receive that content. Android clipboard handling and destination apps have their own behavior and policies.

Wi-Fi Connect uses Android network approval or settings. Phone and contact actions open the dialer/contact editor. UPI actions open compatible payment apps for review; iScan does not process or approve a payment. A supported bank-card action launches a banking/wallet app without card extras; card enrollment happens in that app.

This website

The landing page loads no analytics, ads, remote fonts or third-party embeds. It does not use a contact form or set application cookies. The Vercel hosting platform and delivery infrastructure may process standard request information such as IP address, user agent and access logs to serve and secure the site. This hosting behavior is separate from the offline Android app.

Availability and updates

Features and handling may change with future app versions. This document is based on the current project implementation and is not a claim that every device or third-party app behaves identically.