App Privacy Policy
For the Taskey mobile application (Android and iOS)
Google Play Data Safety
App privacy policy under the GDPR and Google Play Data Safety
This document describes which data the Taskey app collects, the purposes for which it is processed, the recipients to whom it is transmitted and how users can exercise their rights. It complements the privacy policy for the taskeyapp.com website and is the authoritative document for the Google Play Store review.
This document is a translation for convenience. The legally binding version is the German original.
1. Controller
The controller responsible for data processing in the Taskey app is:
Fynn-Luca Schulz
Schulz & Stosse GbR
In der Acht 44
66333 Völklingen, Germany
Email: info@taskeyapp.com
Phone: +49 151 68488999
Contact for privacy requests and account deletion: info@taskeyapp.com
2. Scope
This privacy policy applies to the Android and iOS versions of the Taskey mobile application (hereinafter the app), distributed via the Google Play Store, the Apple App Store and additional channels. Differences between the versions are marked. The iOS version additionally embeds Firebase Analytics for Apps (Google Analytics for Firebase, SDK GoogleAppMeasurement) and Google Ads On-Device Conversion Measurement (see section 5). The processing of personal data during a visit to the taskeyapp.com website is governed by the separate website privacy policy available at taskeyapp.com/datenschutz.
3. What data the app collects
The app collects and processes the following categories of personal data. The list is exhaustive.
3.1 Account data
When signing in to an existing Taskey account, the following data is processed: first and last name, business email address, password (stored solely as a cryptographic hash), role within the organisation, association with the contracting company. Account data is stored on the Taskey backend, which is operated by Schulz & Stosse GbR within the European Union.
3.2 Location data (approximate and precise location)
For on-site verification during digital time tracking and to display nearby job sites, the app accesses the device's approximate and precise location (Android permissions ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION). Location access happens exclusively as part of an active user action (clock in or out, map view, trip documentation) and only after the user has granted the system permission. Location coordinates are transmitted to the Taskey backend together with the time or action entry and stored with that entry. No permanent background tracking takes place.
3.3 Camera
The app uses camera access (CAMERA permission) exclusively to scan QR codes at job sites and on work orders. Image processing takes place entirely on the device (Google ML Kit Barcode Scanning, on-device). Camera images are neither stored nor transmitted to the Taskey backend or to third parties. Only the character strings decoded from the QR code (such as object or work-order identifiers) are further processed.
3.4 NFC
The app uses the NFC interface to read the NFC tags installed at work sites. The tags are used for clocking in and out as part of digital time tracking. The identifier read from the tag is transmitted to the Taskey backend together with the timestamp and associated with the time entry. In technical diagnostic logs (section 3.7) the tag identifier is not stored in plain text, only as a shortened hash value.
3.5 Push notifications
The app uses Firebase Cloud Messaging (FCM) provided by Google Ireland Limited to deliver functional push notifications (work-order assignments, schedule changes, approvals, chat messages). On first launch, FCM issues a pseudonymous registration token for the device. This token is transmitted to the Taskey backend and associated with the user account solely for delivering notifications. The POST_NOTIFICATIONS system permission can be revoked in the device settings at any time.
3.6 In-app activity, work-order and time data
During use of the app, the following functional data is processed and stored on the Taskey backend: time entries (start, end, break, job site, NFC tag identifier if used), work-order and task data (title, description, status, assignment, attachments), customer, object and vehicle data from the respective company's records, chat messages between members of the same organisation, and files uploaded by the user such as documentation photos, evidence of completion and signatures.
3.7 Device, diagnostic and error information
For operational security, troubleshooting and technical support, the app processes the following technical data: (a) Server logs: for every request to the Taskey backend, the IP address, timestamp, API endpoint called, HTTP status code, app version, operating system version and device model are stored temporarily and deleted after 30 days. (b) Device report: after sign-in, the app reports information about the device in use to the Taskey backend so that Taskey support can trace problems (for example when an NFC scan does not work). Transmitted are: an installation identifier randomly generated by the app, platform, manufacturer, device model, device name, operating system version, app version, app language, time zone, push token, network type (Wi-Fi, mobile or no connection), free storage space and the status of app permissions and device settings (NFC available or switched on, precise, approximate and background location, location services, camera, notifications, battery saver, data saver; on Android additionally battery optimisation, on iOS additionally background app refresh and Live Activities). Changes to these settings are logged with a timestamp. The report is sent on launch, when returning to the app and on changes, otherwise at most every 30 minutes. Location coordinates are not part of the device report. (c) Diagnostic logs and crash reports via PostHog: the app sends technical event logs to PostHog (EU Cloud), for example: NFC read started, tag recognised or unknown, timeout or read error; result of check-in and check-out requests with HTTP status and duration; status of offline synchronisation and photo uploads; successful or failed sign-in (without user name); network errors with the path called, without identifiers; screen changes within the app; permission changes and crash reports with stack trace. The events are linked to the internal Taskey user ID, the role, the company identifier and the app language. Names, e-mail addresses, passwords, contents of notes, messages or photos and location coordinates are not collected; IP addresses are anonymised by PostHog. No screen recording (session replay) takes place. (d) Crash and error reports via Sentry: in addition, app crashes with stack trace and technical metadata are sent to a Sentry instance that we operate ourselves on servers in Germany. The data under (b) to (d) is used exclusively for error analysis and technical support. It is only accessible to the support team of Schulz & Stosse GbR and is not evaluated to monitor the performance or behaviour of employees, nor passed on to the commissioning company for that purpose.
3.8 Payment data
The app itself does not process any payment data. Paid use is agreed exclusively on the basis of a contract between the contracting company and Schulz & Stosse GbR, outside the app. No credit-card, bank-account or invoicing information is collected within the app.
4. Purposes and legal bases
Processing takes place for the following purposes and on the following GDPR legal bases.
- Provision of the user account and app functions: Art. 6(1)(b) GDPR (contract with the contracting company and the users)
- Digital time tracking, work-order and object documentation: Art. 6(1)(b) GDPR (performance of a contract) and Art. 6(1)(f) GDPR (legitimate interest of the employer in a verifiable record of work)
- Verification of the job site via location, NFC and QR code: Art. 6(1)(b) GDPR in conjunction with the user's employment relationship with the contracting company
- Push notifications via Firebase Cloud Messaging: Art. 6(1)(b) GDPR (performance of a contract)
- Server logs for operational security and error analysis: Art. 6(1)(f) GDPR (legitimate interest in secure operation)
- Device report, diagnostic logs and crash reports for error analysis and technical support (PostHog, Sentry): Art. 6(1)(f) GDPR (legitimate interest in a functional, error-free app and effective support)
- Storage of the sign-in token in encrypted device storage: Art. 6(1)(b) GDPR in conjunction with Art. 32 GDPR
5. Recipients and integrated services (SDKs)
The app integrates the following services and libraries. No further recipients of personal data are envisaged.
Google Ireland Limited (Firebase Cloud Messaging)
Receives the device's FCM registration token and delivers push notifications. Data transmitted: FCM token, instance ID, timestamp of delivery.
Google Ireland Limited (Google Play Services Location)
Provides the device location determined by the operating system via the system interface when the app actively uses a location-based feature.
Google Ireland Limited (Google ML Kit Barcode Scanning)
Processes camera images for QR-code recognition entirely on the device (on-device). No images or recognised content are transmitted to Google.
OpenStreetMap Foundation (via the OSMDroid library)
Delivers map tiles to display job sites. When map tiles are loaded, the device's IP address is transmitted to the OpenStreetMap tile servers.
Apple Inc. — Apple Push Notification service (iOS only)
Receives the APNs device token of the iOS device and delivers push messages to the device. The token is passed on to Firebase Cloud Messaging.
PostHog Inc. — diagnostic logs and error tracking (EU Cloud)
Processes the diagnostic logs and crash reports described in section 3.7 (c) on behalf of Schulz & Stosse GbR. The data is stored in the PostHog EU Cloud with servers in Frankfurt am Main. IP addresses are anonymised and screen recordings are disabled. Access by the US parent company cannot be ruled out; Standard Contractual Clauses of the European Commission are in place for this.
Sentry (self-hosted) — crash reports
Captures app crashes and errors with stack trace and technical metadata. The Sentry instance is operated by us on servers of IONOS SE in Germany; no data is transferred to the company that makes Sentry.
Google Ireland Limited — Firebase Analytics for Apps (iOS only)
Collects usage events (screen views, app opens, interactions) with a pseudonymous instance ID. This SDK is under review with regard to its necessity in an employment context.
Google Ireland Limited — Google Ads On-Device Conversion Measurement (iOS only)
Attribution of app installs to marketing campaigns (conversion attribution). This SDK is under review with regard to its necessity in an employment context.
Taskey backend (Schulz & Stosse GbR)
Stores account, time tracking, work order, site and chat data as well as the device report under section 3.7 (b). The servers are operated in Germany (IONOS SE). No processing outside the EEA takes place here.
Personal data is neither sold nor used for advertising, and there is no cross-app tracking (tracking within the meaning of App Tracking Transparency). Both app versions use PostHog exclusively for diagnostic logs and error tracking. The iOS version additionally embeds two Google SDKs, called out separately in the recipient list above: Firebase Analytics for Apps (GoogleAppMeasurement) and Google Ads On-Device Conversion Measurement. These SDKs are currently under review with regard to their necessity in an employment context; where no solid legal basis exists in the employer/employee relationship, the features are to be deactivated or removed. The full processor list is available at taskeyapp.com/legal/avv.html.
6. Data security
Communication between the app and the backend takes place exclusively over TLS-encrypted HTTPS connections. Passwords are stored on the backend solely as a cryptographic hash. On the device, the app uses encrypted Android security storage (AndroidX Security EncryptedSharedPreferences) to store the sign-in token. Access to the backend is protected by role- and tenant-based permissions.
7. Storage period
Account data as well as work order, site and time data are stored as long as the user account and the related contract of the commissioning company are active. Server logs are deleted automatically after 30 days. Device reports are deleted 90 days after the device last reported, logged permission changes after 90 days. Diagnostic logs and crash reports are deleted as soon as they are no longer required for error analysis, and on request. After an account is deleted, personal data is removed from production systems within 30 days. Data subject to statutory retention obligations (for example under the German Commercial Code and Fiscal Code) is excepted; such data is blocked and deleted once the retention period has expired.
8. Account deletion and data deletion
Users can request the deletion of their account and the associated personal data at any time.
- Send an email with the subject line "Taskey account deletion" to info@taskeyapp.com.
- The request must contain the email address associated with the account so that the request can be matched.
- After confirmation, deletion is completed within 30 days. Completion is confirmed by email.
- Data subject to statutory retention obligations is first blocked and then deleted once the retention period has expired.
Public URL for account deletion (for use in the Google Play Store listing): https://www.taskeyapp.com/en/datenschutz-app#account-deletion
9. Rights of data subjects
Under the GDPR, data subjects have the following rights. Requests can be sent to info@taskeyapp.com at any time.
- Access to the processed data (Art. 15 GDPR)
- Rectification of inaccurate data (Art. 16 GDPR)
- Erasure of data (Art. 17 GDPR)
- Restriction of processing (Art. 18 GDPR)
- Data portability (Art. 20 GDPR)
- Objection to processing (Art. 21 GDPR)
- Complaint to a supervisory authority (Art. 77 GDPR)
10. Children
The app is aimed exclusively at professional users within an employment or service relationship and is not intended for persons under the age of 16. No knowing processing of children's data takes place.
11. International data transfers
User data in the Taskey backend is stored in Germany. Diagnostic logs are stored in the PostHog EU Cloud (Frankfurt am Main); as PostHog Inc. is a US company, access from the USA cannot be ruled out. Firebase Cloud Messaging and Google Play Services are provided by Google Ireland Limited; Google processes operational data globally. For transfers to third countries, PostHog and Google rely on the Standard Contractual Clauses of the European Commission or the EU-US Data Privacy Framework.
12. Automated decisions
The app does not make any automated decisions within the meaning of Art. 22 GDPR. No profiling of users takes place.
13. Summary of the Google Play Data Safety declaration
The following overview mirrors the declaration made in the Google Play Data Safety form.
- Data types collected: personal info (name, e-mail), location (approximate and precise), app activity (user interactions in the app), app info and performance (crash logs, diagnostics), device or other IDs (installation ID, FCM registration token), files and docs (proof documents uploaded by the user).
- Data usage: app functionality, account management, digital time tracking, messaging, error analysis and technical support. No advertising, no sale, no cross-app tracking.
- Data sharing with third parties: Google (Firebase Cloud Messaging, Play Services Location) and the OpenStreetMap Foundation (map tiles). PostHog processes diagnostic data as a processor. No sale, no advertising.
- Security practices: transmission exclusively via TLS, passwords stored as hashes, sign-in token stored encrypted on the device.
- Data deletion: account and data deletion on request by e-mail to info@taskeyapp.com within 30 days.
14. Changes to this app privacy policy
This policy will be updated whenever the technical implementation of the app, the services used or the applicable legal requirements change. The current version is available at taskeyapp.com/datenschutz-app.
As of: October 25, 2026