evID reads your document on your device. It keeps no document history.

Which versions this policy covers

This policy covers evID on iPhone and iPad, on Mac and on Android, in the versions released from 28 October 2026. The release notes of each version name the policy version that applies to it. If a release would change how data is handled, a new version of this policy explaining the change is published before that release.

The Mac version is the iPhone and iPad app adapted to Macs with Apple silicon, and the Android version follows the iPhone app. All three work the same way, apart from the platform differences summarised below and noted in each section.

Who is responsible for what

evID processes document data only on your device, at your request. ALBeID OÜ does not receive that data. ALBeID OÜ is responsible only for the data it receives itself: the technical details of requests to its servers when evID downloads public files, and anything you choose to send it, such as emails or beta feedback. The company and website privacy policy describes that processing, its legal basis and how long the data is kept.

If you use evID to read a document that belongs to another person, for example at a reception desk or in an office, what you do with the data shown on your screen is your responsibility. If your use falls under data protection law, you are the one who needs a lawful basis for it and who must inform the document holder.

How a document is read

A document chip opens only with an access key printed on the document itself: the fields of its machine-readable zone (MRZ) or its card access number (CAN). You type the key in or scan the MRZ with the camera. evID then reads the data the issuing authority stored on the chip. Depending on the document, this can include the holder's name, nationality, date of birth, document number, validity dates and facial image. evID checks the chip's content and signatures and shows you the data with the results.

The reader depends on the platform:

• iPhone: the built-in NFC reader.
• iPad: an iPad has no NFC reader, so it reads through another device that you choose as a helper, as described below.
• Mac: a compatible contactless USB card reader connected to the Mac, or another device that you choose as a helper.
• Android: the device's built-in NFC reader.

The facial image is shown so that you can compare it with the person and the printed document. evID does not perform face matching or any other biometric identification.

evID checks the chip according to the ICAO Doc 9303 specifications and the technical guidelines of the German Federal Office for Information Security (BSI). It follows these specifications but does not endorse them, and it does not claim certification by ICAO, the BSI or any other body. The result is a technical check of the chip's content. How you use it is at your sole discretion.

Camera and text recognition

The camera is optional: you can always type the access key instead. It is also used to scan the one-time QR code that pairs two devices. Recognition runs entirely on the device:

• iPhone, iPad and Mac: Apple's camera and Vision frameworks, built into the operating system.
• Android: Tesseract, an open-source recognition engine included in the app together with its recognition data. evID for Android does not use Google ML Kit, which sends usage and diagnostic data to Google. The pairing QR code is also recognised on the device.

evID does not save or upload camera images. Recognised text is placed in the access fields for you to check, and is cleared with them. Anything the operating system itself does with the camera is governed by its maker's privacy policy.

What happens to document data

The access key, the data read from the chip, the facial image and the results of the checks are processed in the device's memory. evID never writes them to storage, never uploads them to ALBeID OÜ or any other server, and keeps no history of the documents it reads. On every platform:

• When the connection ends: the result stays on screen after the connection with the chip or reader ends, so that you can review it. Ending the connection does not clear it.
• If reading is interrupted: the data already read stays in memory, so that reading can continue when you present the document again. It is not cleared at the moment of the interruption.
• Read another document clears the result, the access key you entered and any helper session.
• Cancelling stops the reading in progress.
• Closing or quitting the app, or the system ending it, releases everything evID held in memory. An interrupted reading cannot be continued after that.

Some copies are outside evID's control: screenshots you take, files you choose to save or share, and crash diagnostics handled by the operating system. Like any app, evID also cannot guarantee that the operating system immediately erases every copy left in memory.

Reading with the help of another device

You can choose another device running evID as a helper to read a document for you. This is how an iPad reads documents, and it lets any device running evID use the reader of another one. You start the assistance yourself on both devices and pair them by scanning the helper's one-time QR code. The two devices then connect over an authenticated, encrypted Bluetooth connection, without the internet.

The access key is entered on the requesting device, which carries out the access to the document and all the checks. The helper connects its reader to the document and passes the commands and the chip's responses between its reader and the requesting device. The document's responses therefore pass through the helper. The helper does not upload them to ALBeID OÜ or anyone else. Both devices keep their working data only temporarily, and stop when you cancel or close the app.

Two limits are worth knowing. The Bluetooth connection is encrypted, but that is separate from the document's own secure messaging. Secure messaging protects the parts of the exchange its protocol covers. The first exchanges with the chip, before secure messaging starts, are not encrypted between the requesting device and the chip, so the helper can see them. Pairing also does not prove that the helper runs an unmodified evID, or that it is physically next to the document. Use only a helper device you trust.

Connections to the internet

evID connects to the internet only over HTTPS, and only to obtain public files. These requests never contain document fields, access keys or facial images.

• Trust material: to check the signatures on a chip, evID needs the public certificates of the Country Signing Certificate Authorities (CSCAs), their certificate revocation lists (CRLs) and related signed lists, and can use optional reference data. ALBeID OÜ publishes a default set on albeid.eu. evID downloads it, or checks for an update, only when you ask. Downloading is separate from trusting: you review and approve a source before evID uses it. You can also import files yourself or use another publisher's address.
• Languages: English and Albanian are built in, and other languages are signed packs downloaded from albeid.eu. When the language selection is shown, including in the welcome guide when you first open evID, the app downloads the list of available languages. A pack is downloaded only after evID shows you its size and you agree.

As with any HTTPS request, the server receiving it sees your device's IP address and the standard request details. For albeid.eu, which runs through Cloudflare on a server in Germany, the company and website privacy policy describes how these details are logged and how long they are kept. If you use another publisher's source, that publisher's own privacy policy applies to its server.

evID makes no other connections. It sends no usage statistics and contains no analytics, advertising or tracking code.

What is stored on the device, and how to delete it

evID keeps no document records. On the device, it stores only:

• the public trust sources you have downloaded or imported, pending or approved, with your choices, the approval and update-check details, and any update address you set;
• verified caches of that material, and any reference data you import;
• your choice of language, installed language packs and your progress through the welcome guide;
• keys that protect the stored trust material: in Apple Keychain on iPhone, iPad and Mac, and in the Android Keystore on Android;
• terminal credentials, only if you set them up for an authorised issuer: the certificate chain you approved, and a signing key that stays in Apple Keychain or the Android Keystore on the device;
• on Android, Tesseract's recognition data, installed with the app.

To delete what evID stores:

• A trust source: use Remove approved source. This removes the source, its update address, its check details and its revocation lists.
• Terminal credentials: use Remove approved chain. The device's signing key is kept, so that the credentials can be renewed.
• Everything on Apple devices: deleting the app removes the files it stored. Items in Apple Keychain can survive deleting an app, so evID cannot promise that uninstalling removes every key. The stored files can also be included in your device backups, depending on your backup settings.
• Everything on Android: uninstalling the app, or using Clear storage in the system settings, removes its data. evID's data is excluded from Android's cloud backup and from device-to-device transfer.

Files you exported or saved elsewhere are not affected by any of these steps. You manage them yourself. There is no account, so there is no account to delete.

Exported reports and other apps

You can choose to export a technical standards report about a reading. It is a ZIP file with the results of the checks, an inventory of the checks covered, process details and timings, and the protocol evidence the report format allows: the public BAC challenge or the mutually authenticated PACE nonce. It does not contain the holder's personal data, facial images, certificates, keys, raw document data or the raw exchanges with the chip. It does record how and when a document was checked, so handle it with care. You choose where to save or share it, and the storage or sharing service you choose handles it under its own policy.

No version of evID covered by this policy passes document data to other apps, including other apps published by ALBeID OÜ. A future digital wallet, face matching or server-based identity verification would need its own accurate privacy notice, and your choice, before it starts. This policy does not authorise any of them in advance.

Permissions

evID asks only for the permissions it needs, each for one purpose:

• NFC (iPhone and Android): to read a document chip when you ask.
• Smart card reader (Mac): to use the connected contactless reader.
• Camera, optional: to scan the MRZ instead of typing it, and to scan a helper's pairing QR code.
• Bluetooth, optional: only for reading with the help of another device you have chosen.
• Network: only to obtain the public files described above.
• Files (Mac): only the files you select to import or export.

You can manage these permissions in your device's settings at any time. You can also stop a reading, decline optional downloads and clear the document. Allowing a permission in the operating system is a technical choice; it is not the legal basis for any processing by ALBeID OÜ. Without trust material, evID can still read a document, but some checks cannot be completed. Reading a document never uploads it to a server.

App stores, diagnostics and feedback

Apple distributes evID for iPhone, iPad and Mac under its own privacy policy, and Google Play distributes the Android version under Google's. If you have chosen in your device settings to share diagnostics with app developers, the store may pass ALBeID OÜ crash reports. Feedback, screenshots and emails you choose to send also reach ALBeID OÜ. These come from the store or from you, never from code in evID. The company and website privacy policy describes how ALBeID OÜ handles them.

Before sending anything, remove identity data from screenshots and messages: never send an access key, a document number, a facial image or raw chip data.

Children

evID is not directed at children. Since ALBeID OÜ collects no personal data through it, it collects none from children either.

Security

The strongest protection is not to collect data at all. Beyond that, the chip is accessed through the protocols defined by ICAO, public files are downloaded over HTTPS, language packs and ALBeID OÜ's default trust material are signed and verified before use, stored trust material is protected by keys kept in Apple Keychain or the Android Keystore, and the Bluetooth connection with a helper is authenticated and encrypted.

Your rights

Under the General Data Protection Regulation (GDPR) you have the right to access the personal data held about you, to have it corrected or erased, to restrict its processing, to receive it in a portable format where that applies, and to object to its processing. ALBeID OÜ holds no document data from evID. For server logs, emails and feedback, the company and website privacy policy explains what is held and how to exercise your rights. ALBeID OÜ answers every request within one month. No automated decision-making or profiling takes place. You may also lodge a complaint with the supervisory authority of the country where you live or work, or with ALBeID OÜ's lead authority, Estonia's Data Protection Inspectorate (Andmekaitse Inspektsioon).

Contact

evID is published by ALBeID OÜ, registry code 16874333. Its registered address is public in its entry in the Estonian e-Business Register. For any privacy question about evID, write to a.vrushi@albeid.eu.

Changes to this policy

Every change to evID is described in the app's release notes. If a change to the app requires a change to this policy, the new policy is published as a new version, numbered and dated, before the change takes effect, and earlier versions remain available from this page. Version 1 was published on 9 October 2026. Version 2 changes it as follows:

• one policy now covers iPhone and iPad, Mac and Android, noting the differences between platforms;
• the Android version uses Tesseract, built into the app, instead of Google ML Kit, so no data is sent to Google for text recognition;
• it lists what evID stores on the device and how to delete it;
• it explains that a result stays visible after the connection ends, until you clear it;
• it describes language downloads and the exported technical report;
• it removes the description of reading on behalf of other ALBeID apps, which the versions covered do not offer;
• it corrects the description of reading through a helper: not every exchange with the chip is encrypted between the requesting device and the chip.

You are never asked to accept a new policy in order to keep the app you have. If you do not agree with a new version, you can choose not to install that update and keep using your current version of evID, under the policy that applied to it.