PatrolScan for iPhone
PatrolScan privacy information
This notice explains data handling in the PatrolScan iPhone app. The website privacy notice separately covers visits to this website and correspondence with the developer.
Last updated: 18 October 2026
Developer and contact
PatrolScan is developed by Thomas Meroth, Meroth IT-Service, Eschersheimer Landstraße 42, 60322 Frankfurt am Main, Germany. For app support and privacy questions, email kontakt@fra.digital.
Operational data stored on your iPhone
During normal operation, checkpoints, routes, schedules, patrols and confirmations are stored locally inside PatrolScan’s protected app container on the device. The records may also include tasks, instructions, comments, timestamps and results entered during use.
No user account is required. PatrolScan uses no developer-operated backend service and does not transmit these operational records to Thomas Meroth or fra.digital. The developer therefore cannot retrieve your locally stored patrol records from a server.
NFC checkpoint confirmations
Compatible NFC tags are registered and assigned to checkpoints during setup. During a patrol, a scan allows the app to determine whether the required checkpoint has been confirmed. These confirmations form part of the local operational records.
Exports, encrypted backups and device backups
An administrator can explicitly create and export reports or password-protected encrypted backups, then save or share the files through another app or service. Where a file is sent or stored depends on the destination selected by the administrator. Those destinations may have their own data-handling conditions.
Backups can be inspected and imported to restore the configuration only or all backed-up app data. Whether app data is also included in an Apple device backup depends on the device’s backup settings. This is separate from data transmission by PatrolScan.
The device owner or operating organization determines how long local operational records and exported copies need to be retained for its workflow.
Optional network time verification
When NTP time verification is enabled, PatrolScan sends only a technical time request to the time server configured by the administrator. No checkpoint, route or patrol data is included in this request.
For technical reasons, the time server may process the device’s IP address and the time of the request. The selected time-server operator is responsible for its own processing. Administrators can configure time verification in the app.
Local notifications
Local notifications require the user’s permission. Their availability depends on the notification settings on the device.
Website visits and support enquiries
Opening this website or contacting the developer by email involves separate processing, such as the technical information needed to deliver a web page and the contents of a support enquiry. The website privacy notice provides further information about that processing, contact details and data-protection rights.
An organization using PatrolScan remains responsible for its operational processes and for any personal information it enters or shares through reports and backups.

