ScanPass Pro — demonstration privacy policy
Version demo-1.7. Last updated 25 October 2026.
This is a limited demonstration. Check each result before using it. Closing or reloading the page does not delete exported files or copies held by an extension or another website.
The demo processes passport images in your browser. The scanning workflow does not send images or passenger fields to our server. Hosting, support and any optional extension are described below.
What the browser stores
The browser stores language, a document-version acknowledgement, technical recognition preferences and a usable-result counter, not passenger values in those settings. The current list and images are held temporarily in the page's working memory. Files are saved only by explicit action; downloads, clipboard history or a synchronised folder can retain copies.
Five-result limit and reset
The five-result counter is local and contains no passenger fields. Clearing site data resets its settings and counter. A new notice version asks again without resetting the counter. Clearing site data does not delete exports or extension storage.
Contact and language versions
ScanPass Pro is provided by Naftali Ravinov, Nof HaGalil, Israel. Contact: support@scanpasspro.com. The English version is the authoritative one. The Hebrew, Russian and Arabic versions are provided for convenience; where they differ, the English governs. See the demonstration terms.
Hosting, extension and support
Cloudflare hosts the demo and receives technical connection information, such as an IP address, to deliver and protect it. If you contact support, your email and message are routed through Cloudflare to Gmail so we can reply. Contacting support is optional; without contact information we cannot reply. Do not send passports or passenger details. An optional extension has separate storage and can disclose filled fields to your chosen supplier before you submit its form. For provider details, retention and your rights to access and correct customer information, see the full privacy policy.
Cookies & storage
This section explains the cookies and browser storage used by ScanPass Pro. The items below apply according to the features you use. Passport recognition takes place on your device; account and payment services are handled separately.
- Sign-in: signed scanpass_access cookie, up to 365 days for email sign-in or 30 days for the shared-password route; scanpass_challenge, up to 15 minutes; scanpass_device, a random identifier for the computer you sign in on, for the same period as the sign-in. Online entitlement is checked separately. For email sign-in, these cookies include your email address. They contain no passport fields, and the device identifier describes neither you nor the computer. For each sign-in address we keep how many computers it has signed in on and when each was first and last seen, so that a subscription is used by the people it covers. We do not keep a network address, a browser description or a location.
- Preferences: language, export columns, scanner settings, locally recorded terms version and demo counter remain until changed or site data is cleared. Clearing the counter does not delete exported files.
- Offline use: the browser keeps application files and recognition models. It may also remember access to a folder you selected, without keeping a copy of that folder's files. You can manage site data and folder permissions separately in browser settings.
- Passport results are held temporarily in page memory. Refreshing does not remove downloads, clipboard history, synchronised folders or the extension's separate storage. The extension expires passenger data after 45 minutes without a new scan or Fill; suspension can delay cleanup.
- Payment: Paddle loads when you choose to open checkout. Paddle and its providers receive connection and transaction information and may use their own storage. Their retention and processing differ from the application's local storage.
- You can clear site data or block cookies in browser settings. This may sign you out, reset preferences or prevent payment and offline use. We do not add advertising or scan analytics to the recognition path.