FFSO Mobile
In connection with your use of FFSO Mobile ("the App"), Falck A/S ("Falck") collects and processes certain personal data about you as data controller. In this Privacy Policy we describe our processing, use and disclosure of your personal data.
The App is an internal tool made available exclusively to Falck employees. It supports field employees in registering maintenance and prevention tasks and documenting on-site conditions during their assigned shifts. FFSO Mobile connects to the FFS-Operations web application as its back-end platform.
Please note: this Privacy Policy applies to the FFSO Mobile application only.
Company contact details can be found in section 9.
In order to provide you with access to the App and to support your operational activities as a Falck employee, Falck processes personal data about you for the following reasons:
We collect and process personal data for the following specific purposes:
Your personal data will not be sold to third parties or used for advertising or marketing purposes.
When we collect personal data from you, it is necessary in order for Falck to provide you with access to the App and to support your operational activities. You are not obligated to provide personal data to us. If you do not provide personal data necessary for authentication and core use of the App, you will not be able to use the App. If you do not grant optional permissions such as location, camera, or gallery access, the App can still be used, but the related features will not function.
Falck exclusively processes personal data about you that is necessary to fulfil the purposes described in section 1. These personal data may, to the extent relevant, include the following categories:
The App requests the following device permissions, each used solely for the purposes stated:
| Permission | Purpose |
|---|---|
| CAMERA | Taking photos of on-site situations and scanning barcodes/QR codes as part of task documentation |
| READ_EXTERNAL_STORAGE | Accessing photos from the device gallery when attaching them to task records (Android versions below API 33) |
| WRITE_EXTERNAL_STORAGE | Saving photos locally to the device before upload (Android versions below API 33) |
| READ_MEDIA_IMAGES | Accessing photos from the device gallery (Android API 33 and above) |
| ACCESS_FINE_LOCATION | Precise GPS location for on-demand location features |
| ACCESS_COARSE_LOCATION | Approximate location as a fallback where precise GPS is unavailable |
| INTERNET | Synchronising data with FFSO Mobile services |
| ACCESS_NETWORK_STATE | Detecting network connectivity to manage offline caching behaviour |
On newer Android versions (API 33+), photo and media access is handled through READ_MEDIA_IMAGES instead of READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE. The App requests only the permissions necessary for your device's Android version.
You can manage camera and location permissions at any time through your device's settings. Denying these permissions will limit certain App features but will not prevent you from using the App.
The App can determine your location (precise GPS and approximate) when you initiate a location-related feature (e.g., viewing your position on a map). Location is collected on demand only — the App does not continuously track your location in the background. The App can be used without location permission, but location-dependent features will not function. Location data is not used for employee tracking, advertising, or marketing.
Basic device information (device model, operating system version, app version, platform) is captured at the time of device binding (activation). This data is stored as part of your device registration record. Additional device telemetry (OS version, app version, device type) may also be captured by Microsoft Application Insights as part of automatic telemetry during app usage for the purposes of technical support and performance monitoring.
To protect your account and ensure system security, the App records authentication events including: successful and failed login attempts, device activation and revocation events, lockout events, and the IP address used during device activation. These logs are used for security monitoring and are not used for employee tracking or performance evaluation.
The App stores a local encrypted database (SQLite) on your device to support offline functionality. This cache contains shift and task data relevant to your current session. Images stored locally are encrypted using AES-GCM encryption, with encryption keys managed through the Android Keystore. The local cache is cleared upon session expiry, logout, or uninstallation of the App.
The App does not intentionally collect sensitive personal data. However, photos taken during task execution may in specific circumstances incidentally capture information relating to health and safety conditions or other sensitive matters on site. Such photos are processed exclusively for operational documentation purposes.
Falck prioritises the security of your personal data and implements appropriate technical and organisational measures to protect it against unauthorised access, loss, or disclosure.
To use the App, your device must first be activated using a time-limited activation code provided by your manager or an authorised system. This activation code serves as the approval mechanism for device access. Each employee may have up to 5 active device bindings simultaneously. If a sixth device is activated, the least-recently-used binding is automatically revoked to maintain the limit.
If your device is lost or stolen, report it immediately to your manager and IT support. Falck will revoke the device binding, preventing further access to App data from that device. If you have a second registered device, you may also revoke access to the lost device yourself through the App. All data stored locally on the lost device remains protected by encryption (AES-GCM with Android Keystore) and cannot be accessed without proper authentication.
When your employment with Falck ends, your App account is deactivated, preventing further login or access to the App. Local data on your device remains encrypted and will be cleared upon the next login attempt or uninstallation. Server-side data (task records, photos, device binding history) is retained in accordance with the retention periods described in section 4.
In the event of a personal data breach affecting your data, Falck will notify the relevant supervisory authority within 72 hours where required by law. If the breach is likely to result in a high risk to your rights and freedoms, Falck will inform you without undue delay, describing the nature of the breach, likely consequences, and measures taken or proposed to address it.
Before Falck is permitted to process your personal data for the purposes described in section 1, Falck must identify the legal basis for doing so, and define for how long your personal data will be stored.
In accordance with the GDPR, Falck uses the following legal bases to process your personal data:
The national legislation relied upon by Falck for the processing and storage of personal data includes:
Falck processes your personal data for as long as you are employed by Falck and for a period of up to 5 full calendar years thereafter, unless a shorter period applies as described below.
You may request deletion of your personal data by contacting krystian.gadomski@falck.com or dpo@falck.com. Deletion requests are processed within 30 days. Some data may be retained where required by law, employment obligations, or where the data constitutes employer-owned operational documentation (e.g., task photos).
Your personal data is not used for automated, individual decision-making or profiling.
Falck will, to the extent necessary, share personal data about you with other recipients in order to operate the App and fulfil the purposes described in section 1.
We do not sell your personal data to third parties. Your data is not used for advertising or marketing purposes.
Falck shares your personal data with suppliers ("data processors") who process your personal data on the basis of instructions from Falck and under strict data processing agreements. These data processors are primarily located within the EU/EEA, but transfers to countries outside the EU/EEA may occur, as Falck uses Microsoft Azure cloud services with infrastructure and support functions that may be located outside the EU/EEA, including in the USA. In such cases, transfers are governed by EU Standard Contractual Clauses.
(e.g. public authorities including police, other individuals in exceptional circumstances)
| Supplier | Service | Location | Purpose | Transfer basis |
|---|---|---|---|---|
| Microsoft | Azure Storage | EU / USA | Cloud storage for photos and files uploaded through the App | EU Standard Contractual Clauses (a) |
| Microsoft | Azure Log Analytics | EU / USA | Centralised aggregation of application log data | EU Standard Contractual Clauses (a) |
| Microsoft | Application Insights | EU / USA | Application telemetry and performance monitoring | EU Standard Contractual Clauses (a) |
| Google Maps Platform | EU / USA | Map rendering and location display within the App | EU Standard Contractual Clauses (a) | |
| Falck / HCL | On-premises VM (IIS, SQL Server) | EU | Hosts the Mobile API, Login App, and primary database | N/A (on-premises within EU) |
A full list of Microsoft's sub-processors and their locations is available at:
https://servicetrust.microsoft.com/ViewPage/TrustDocumentsV3
In connection with Falck's processing of your personal data, you have certain rights which you may exercise if you wish. You have, amongst other things, the right to:
Requests relating to your rights will be responded to within 30 days. You may exercise your rights by contacting krystian.gadomski@falck.com or dpo@falck.com.
In addition to the above, you have the right to lodge a complaint about Falck's processing of your personal data with the relevant national supervisory authority:
You have the right to receive a copy of all personal data Falck processes about you, free of charge and in a commonly used format.
You have the right to have incorrect or incomplete personal data about you corrected or completed.
You may request deletion by emailing krystian.gadomski@falck.com or dpo@falck.com. Deletion requests will be processed within 30 days. This right may be limited where Falck has a legal basis justifying continued processing, including employment obligations, legal claims, audit requirements, or where data constitutes employer-owned operational documentation. Deletion of your active App account is managed through Falck's employment and IT systems.
In certain circumstances you have the right to restrict Falck's processing of your personal data, meaning that Falck may only store — but not otherwise process — your data. This right may apply if the accuracy of the data is disputed, if you object to deletion, or if you object to processing.
You have the right to receive your personal data in a structured, commonly used and machine-readable format.
You have the right to object to Falck's processing of your personal data. Falck may only continue processing if it can demonstrate a compelling legitimate basis, for example where processing is necessary to establish or defend a legal claim.
The App is intended for use by Falck employees only and is not directed at children. We do not knowingly collect personal data from individuals under the age of 16. If you believe that personal data relating to a child under 16 has been collected through the App, please contact us immediately at krystian.gadomski@falck.com or dpo@falck.com so that we can take appropriate action.
If you have questions about the processing of your personal data, or if you wish to exercise your rights as described in section 7, please contact:
Krystian Gadomski
App Product Owner / Developer Contact
Falck Digital Technology Poland sp. z o.o. (on behalf of Falck A/S)
Email: krystian.gadomski@falck.com
We aim to respond to all enquiries within 30 days.
You may also contact Falck's Data Protection Officer at: dpo@falck.com
Falck A/S
Sydhavnsgade 18, 2450 København SV, Denmark
CVR: 16271241
This Privacy Policy is updated from time to time to reflect changes in our practices, applicable legislation, or the technical setup of the App. The "last updated" date at the top of this document reflects the most recent revision.
Updates will be communicated via the App's Google Play Store listing.
Employees will be notified of material changes via the Google Play Store listing. If you have questions or concerns about an updated Privacy Policy, please contact the Data Protection Officer at dpo@falck.com.
The following capabilities are planned for future versions of the App. This Privacy Policy will be updated (version 3.0) before these features are released:
Checklist completion and response storage — The App will support completing operational checklists as part of task execution, with responses stored on Falck's servers.
Background location collection during active shifts — The App may collect location data while running in the background during an active shift, for operational documentation purposes. This will require the ACCESS_BACKGROUND_LOCATION permission and a visible foreground notification.
Location data linked to task records — Location coordinates may be stored as part of task records on the server for operational documentation.
These features are not currently implemented and no data is currently collected for these purposes. The Google Play Data Safety declaration reflects only currently-active data collection.
| Version | Date | App version | Changes |
|---|---|---|---|
| 1.0 | May 20, 2026 | — | Privacy Policy finalized and published. |
| 2.0 | May 20, 2026 | 6.3 | Updated to reflect current implementation only. Added: authentication security logs, IP address at activation, Google Maps as sub-processor, READ_MEDIA_IMAGES permission (API 33+), participant presence data. Clarified: location is on-demand only (not background), device info captured at binding time, activation code serves as device approval mechanism, employment termination prevents login (automatic revocation of bindings pending implementation). Removed active claims for: checklist responses, background location, location linked to tasks (moved to Planned Features section 12). |
| 3.0 | TBD | 6.4+ | Will incorporate planned features from Section 12 once implemented. Reference: FFS_Operations_Privacy_Policy_FINAL.md |