Publisher and privacy contact
Tianjin Illuso Information Technology Co., Ltd.
天津伊路索信息技术有限公司 · Tianjin, China
support@illuso.app1. Who operates the app
ID Scanner is a single-device document-reading and age-check assistant for venue and counter staff. This policy covers the iOS and Android app with identifier com.rkvpxdr.idscanner; its displayed store name may vary by language. It supplements our general Privacy Policy with the app-specific practices below.
The venue decides why a visitor’s ID is checked and must provide its own notice and lawful basis. Contact the venue for access, correction or deletion of records it holds. We do not have remote access to its local visitor database. This policy does not authorize a venue to retain identity data in any jurisdiction.
2. What stays on the device
When you start scanning, camera frames, barcode or machine-readable text, and readable identity fields are processed locally to support age, expiry and field comparisons. iOS uses Apple Vision; Android uses bundled Google ML Kit barcode and text recognition. We do not use a cloud ID-reading or generative-AI service.
This workflow does not save ID photographs, camera audio or raw barcode text as a photo library or visitor record. Temporary inspection fields are released when the workflow clears them, including cancellation and privacy suspension. This is not a guarantee of forensic erasure of every memory or operating-system copy.
Quick age check is the current production mode: it retains coarse shift counts rather than personal visitor history, VIP/ban profiles or a stable visitor lookup. Personal-record features require a separately reviewed region/purpose/field/retention policy. No such production policy is currently enabled; buying Pro does not enable it.
If a reviewed records policy becomes available in a later configuration, approved fields, local matching indexes, decisions, visits, lists and expiry rules will be disclosed before enabling that mode. A keyed matching index can still relate to a person and is not anonymous.
3. Local storage, permissions and security
Business data is kept in an encrypted local database with keys protected by the operating system. Management uses a local passcode and optional device biometrics. The app receives the authentication result, not a face or fingerprint template. Biometrics do not tell the app which employee is using the device.
Camera permission is requested for scanning and may be changed in device settings. This workflow does not require contacts, microphone or precise-location access. File export/import uses system-selected locations. Locks, privacy covers and encryption reduce exposure but cannot protect against every compromised device, external photograph or recipient copy.
4. Exports and encrypted backups
An authorized manager can explicitly export reports or create a password-encrypted business backup through the system file/share interface. The destination may be another app or a cloud storage provider you choose. CSV/PDF reports are not automatically encrypted just because backups are. Recipients and storage providers apply their own practices.
We do not operate visitor-data cloud storage, automatic business-data recovery, employee accounts or cross-device synchronization. Purchase restoration restores eligible Pro access; restoring business records requires the separate compatible backup and its password. We cannot recover a forgotten backup password.
Deleting data in ID Scanner cannot recall exported files, already-open shares or recipient copies. On Android, app-issued temporary share access expires no later than five minutes after the private share copy is created, and may end sooner; cleanup may run later when the app resumes. A selected destination is not proof a file was delivered. Manage and destroy obsolete backup/export copies yourself; an old backup can reintroduce records that a new device does not know were later deleted.
5. Services that communicate over the network
Local document processing does not mean the entire app is offline or collects no data. The following services receive technical, advertising, purchase or optional usage data; identity documents, extracted identity fields, visitor indexes and business backups are not attached to these service requests.
- Google ML Kit on Android: recognition input and results stay on-device. Google may receive installation-scoped identifiers, device/app information and feature usage, configuration, performance and error-code metrics, and may contact its servers for maintenance. These technical metrics are separate from the optional Share app usage switch.
- Apple App Store / Google Play and RevenueCat: purchase receipts or tokens, product and transaction information, trial/renewal/entitlement status and a randomly generated RevenueCat app-user identifier support subscription verification, restoration, purchase analytics and fraud prevention. RevenueCat also processes technical/device/network information. We do not send venue, visitor, operator, email or advertising attribution fields to it, and the app does not receive your full payment-card details.
- Google AdMob and its User Messaging Platform: Google processes regional consent choices, IP-derived approximate location and technical interaction/performance data to manage privacy messages, including before ad permission is obtained. When ads are allowed, Google and advertising partners may process device/app or advertising identifiers where available, ad interactions and diagnostic/performance data for ads, measurement and fraud prevention. Only after you affirmatively allow Ad personalization and the required Google regional consent and, on iOS, App Tracking Transparency permission permit it, ads may be selected or measured using activity across other companies’ apps and websites, including an available advertising identifier. This choice does not guarantee personalized ads; Google’s privacy signals and ad availability still apply. If you decline, withdraw permission or leave the choice unset, requests remain restricted and may yield non-personalized/contextual or limited ads, or no ads. Google may still use app- or publisher-scoped identifiers; non-personalized does not mean identifier-free or consent-free. We do not supply identity, visitor, venue, business-record or biometric information for advertising. An active Pro entitlement, including an eligible trial, removes in-app ad placements; it does not erase previous ad data or turn off every consent or service connection.
- Mixpanel, only after optional opt-in: bounded actions such as app opening, onboarding, feature use, scan completion source, paywall/purchase/restore outcomes and ad interactions, with finite categories plus app ID, version, platform and language. Its SDK can attach a random analytics identifier, event time and device/OS/network information. IP geolocation is disabled. We do not enable screen recording, session replay, automatic screen capture, contact profiles or identity-document payloads. These pseudonymous statistics are not described as anonymous.
6. Your privacy choices
Share app usage is off until you explicitly opt in. You can change it in Settings. Turning it off stops new Mixpanel collection and clears pending app/device analytics events; requests already sent cannot be recalled. It does not automatically delete records already held by Mixpanel, cancel a subscription or control ML Kit, store or advertising processing. If a choice cannot be saved, the app reports the error and keeps current usage collection off.
Google’s regional consent message is shown when required before ad requests. The in-app advertising Privacy choices entry is offered when Google requires it. Ad personalization is a separate, optional Settings choice: allow or decline it, and change your choice later. On iOS, a separate tracking-permission review is offered when eligible; you can change that permission and manage advertising identifiers in device settings. Declining personalization, tracking permission or optional analytics does not block local document reading, safety tools or purchases. Advertising/privacy-message controls are separate from the Share app usage switch.
7. Retention and deletion
Transient ID fields are not a Quick-mode personal history. Coarse summaries remain until cleared. Any future approved personal-record mode uses its displayed reviewed expiry policy; no universal identity-record retention period is promised. Authorized local deletion, business-data clear and full local reset have different previews. Full local reset erases the venue data and manager access covered by that operation; it does not erase store purchases, all system keychain items, separate app consent preferences or external copies.
For information we directly control, such as support correspondence and identifiable service records, our general policy normally limits retention to 24 months after last use/contact, subject to legal, tax, accounting, security, fraud-prevention and dispute needs. This is not a 24-month rule for venue-controlled ID records or a verified setting for every vendor account. Third-party service data follows the applicable provider arrangements and retention requirements.
Email a privacy request to the contact below. For valid requests we delete eligible data under our control or initiate provider deletion within seven business days, subject to verification and justified retention exceptions. Provider completion may take longer; we distinguish a request from confirmed erasure. We cannot promise deletion of every store receipt, provider security record or recipient backup. Later app use or purchase restoration can create new service records.
8. Support, rights and identifying your records
If you email us, we receive your address and the information you choose to send. Include ID Scanner, iOS/Android, app version and a description of the request. The current app does not automatically attach or display RevenueCat/Mixpanel support identifiers. An email address alone may not locate randomly identified service records; we may ask for the minimum non-sensitive information needed to verify and locate a request, such as a redacted store order reference.
Do not send ID photographs, raw barcodes, visitor lists, management/backup passwords or payment-card details. We cannot search your local venue database or bypass its manager lock. Depending on applicable law, you may have rights of access, correction, deletion, restriction, objection or portability, and the right to withdraw consent or complain to the relevant authority. Withdrawing consent does not undo prior lawful processing.
Optional analytics and consent-based advertising rely on consent where required. Purchase support, responding to requests, service security and legal recordkeeping rely on the applicable contract, legitimate-interest or legal-obligation basis. Processing and service providers may operate outside your country, including China and the United States; applicable contractual and legal safeguards govern those transfers. This is not a promise that all information remains in your country.
9. This website and policy updates
Opening an external support, terms, privacy or provider page uses your browser and its network connection. This existing website uses Vercel hosting/Vercel Analytics and Google Analytics for browser/device, page-visit and technical measurement data; Google Analytics may use cookies. The app’s Share app usage setting controls app Mixpanel collection, not this website or the sites linked below. Consult the general website policy and provider controls for those services.
The app is an operational tool for staff, not a service for children to submit identity documents to us. If a venue checks a young person’s ID, the venue remains responsible for applicable law and notice. We will update this page when app practices change and show the revision date.