DE← Home

App privacy

Legal noticePrivacyTerms of useApp support

App privacy

Privacy information for EntryCheck Mobile

EntryCheck Mobile processes ticket numbers for admission checks on iPhone and iPad. The camera works on your device; real ticket checks and changes use the KORONA Entry server you configure. These notices cover the mobile app separately from the EntryCheck Mac app.

Translation notice

This English translation is provided for convenience. If there are any discrepancies, the German version is authoritative.

1. Provider and responsibilities

The app provider and contact for questions about its functions is AmoSystems, Fabian Amos, Christburger Str. 15/2, 10405 Berlin, Germany. Email: info@fabianamos.com.

The organisation that determines the purpose, access and use of its ticket server is responsible for its ticket operations. It determines the legal basis, server provider, processing locations, further recipients and server-side retention. AmoSystems does not operate a KORONA server, has no access to your operator’s ticket or access logs and receives no ticket data from the app. API requests go directly to your own ticket server. AmoSystems is responsible for personal data you provide when contacting AmoSystems directly.

2. Camera and ticket data

The camera recognises barcodes entirely on the device. Images and videos are neither stored nor uploaded. The app does not open web addresses contained in QR codes. Camera use requires your system permission, which you can revoke in system settings. Manual ticket number entry is an alternative.

The app processes the ticket number and identifiers, ticket types, item numbers, usage counts, locks, validity periods and admission details returned by the ticket server, where available. Ticket numbers may be personal data when they can be linked to a person or order.

3. Direct connection to the ticket server

For a check or change, the app sends the required ticket number or identifier, authentication, client identifier and, where applicable, entrance and action parameters directly over HTTPS to the configured KORONA Entry server. The server also receives technically necessary connection data such as the IP address. Certificates are validated and redirects are rejected.

Check connection performs a real authenticated read request even in demo mode. The local sample-ticket workflow itself does not query a real ticket server. No new entry is granted without a network response; unconfirmed changes are not automatically retried.

The recipient of API requests is your ticket-server operator or its hosting provider. Ask the responsible organisation about its storage, possible transfers outside the European Economic Area, and your rights concerning ticket data stored there.

4. Credentials, settings and imports

The saved connection and item mappings are stored in the device-bound iOS Keychain. Access is restricted to the unlocked device; iCloud Keychain synchronisation is disabled. Item mappings can be stored without a connection in a separate Keychain item. Demo mode and sound preferences are local app settings. There is no automatic import of Mac configuration or cloud-sync service of our own.

The app reads only an ENV, JSON or CSV file you explicitly select in the system picker. It is processed as data, never executed or uploaded, and the source file is not permanently copied into the app container. The credentials preview masks the password. Only Save in the connection form stores the draft. The original file remains in its chosen location under your control.

Item import stores only item numbers and names. Selected items are applied; deselected items from the same CSV are removed from existing mappings. Items outside the file are preserved. Save stores this set immediately without changing credentials or demo mode. No additional source or selection history is stored. Item mappings do not affect admission decisions.

5. Local activity log

The protected log is kept in the private app container, excluded from device backups and uses complete iOS file protection. Demo activities are stored separately. It contains the activity ID, timestamps, ticket number, action, entrance, demo flag, result, any server-object reference and a hash of the server base used to associate unconfirmed activities. Passwords and camera images are not included.

Before a change, an unconfirmed activity is saved durably. If this fails, no change is started. After an app interruption or a lost reply, the activity remains and blocks further changes to the same ticket on the same server until explicitly resolved after an external check. The local log is not a complete or tamper-proof server journal.

6. Retention, deletion and pending activities

Completed activities are removed after 30 days when the app starts or writes to the log. You can also deliberately remove them through Activity → Delete completed activities. Unconfirmed activities do not expire automatically and are not deleted by that action. Local deletion does not change server data.

Unconfirmed activities must be checked outside the app before marking them as externally resolved. An increased counter alone is not reliable proof when several devices are in use. If the log is damaged or inaccessible, the app blocks further changes and does not silently overwrite it.

The app has no delete-all button for stored credentials. Uninstalling does not reliably remove Keychain items or source import files, and does not resolve pending server bookings. Contact your device administrator before handing over a device. Manage and delete original import files separately.

7. Advertising, diagnostics, App Store and contact

EntryCheck Mobile contains no advertising, tracking, analytics or embedded crash-reporting SDKs, and no AI feature. No automatic usage reports are sent to AmoSystems. Apple may process system or App Store diagnostics you choose to share according to your Apple settings.

When obtaining the app through the App Store, Apple processes download, account and payment data under its own terms. The app has no payment processing of its own, subscription or in-app purchases. Apple privacy information: https://www.apple.com/legal/privacy/.

Web and email links open the system service you use. Our general privacy information additionally covers amosystems.org and voluntary support enquiries: https://amosystems.org/en/privacy/. Please do not send passwords, configuration files or complete ticket lists to support.

8. Your rights

Subject to the legal conditions, you have rights of access, rectification, erasure, restriction, portability and objection. You can withdraw consent for the future and complain to a data-protection authority. For processing by AmoSystems, contact info@fabianamos.com; for ticket operations, contact the responsible organisation.

The general website privacy information explains how contact enquiries are handled. These app notices do not determine a legal basis or server-side retention period for a third-party ticket operator.

Related information

EntryCheck Mobile · Support · Legal notice · Website privacy

Last updated: 11 November 2026