Skip to content
ReiherField

Legal

Privacy policy

Information on the processing of personal data in the ReiherField Driver app, the web application and this website.

This is an English translation for convenience. The German version is legally authoritative.

Last updated:

Scope

This policy applies to the ReiherField Driver app, the web application at app.reiher.app and the public website at reiher.app.

ReiherField is a work application for companies and their authorised drivers and employees. Accounts are invited by the company; there is no public self-registration.

Controller

The company that provides access to ReiherField is responsible for processing employee data within the employment relationship. The platform operator provides the application and processes data on behalf of the company where required for operation.

The operator is responsible for its own processing — such as the technical operation of this website, account security and handling support requests. Provider details are published in the imprint.

Digicut Rubmer GesmbH

Georgestraße 26 4222 Langenstein Österreich

office@digicut.at

What data is processed

Depending on the enabled features and role, the following categories may be processed in particular:

  • Account and identity data: name, email address, phone number, user and driver number, language, role and company.
  • Employment and profile data: employment type, agreed monthly hours, date of birth if recorded by the company, and profile picture.
  • Working-time data: clock-in and clock-out, breaks, session status, corrections, manual end-time requests and vehicle/plate assignment.
  • Planning and absence data: availability, shifts, leave, sickness notifications, holidays and attachments where enabled.
  • Receipt and document data: fuel receipt images or PDFs, amount, litres, filling station, licence plate, notes and OCR fields; documents and payslips where enabled.
  • Financial data where the payroll-data feature is enabled: bank account, IBAN, BIC and account holder.
  • Authentication, session and security data as well as audit events.
  • Support communication that you send to the operator or your company.

How data is collected

Account data is created by the company or provided via an invitation. Further data arises from your entries and actions in the app, from camera or file selection when uploading receipts and documents, and from technically required server and security logs.

The native Android app does not request location permission; the WebView location feature is disabled. A location feature is not active in this app version.

Purposes of processing

Processing serves the provision of the work features enabled by the company, sign-in and account security, working-time and receipt management, planning and absence management, report creation, compliance with statutory working-time, payroll and retention obligations, and the defence and enforcement of legal claims.

Support requests are processed to handle the respective matter.

Recipients and processors

Data is transferred only to persons and bodies that need it for the respective task. This includes in particular the authorised administrators of the employing company and technical service providers used to operate the application.

The operator does not sell personal data and does not use it for advertising.

  • DigitalOcean, LLC (Frankfurt, Deutschland (EU))

Transfers outside the EEA

The production configuration is designed for processing within the European Union. Where a service provider processes data outside the EEA, the statutory transfer mechanisms required for this are applied.

Der Produktivbetrieb wird in der EU (Frankfurt, Deutschland) gehostet. Soweit weitere Dienstleister eingesetzt werden, werden die erforderlichen Übermittlungsmechanismen zugrunde gelegt.

Retention period

Personal data is stored only as long as required for the respective purposes or as statutory retention obligations require. Working-time, payroll, sickness and receipt data may be subject to labour, payroll and tax retention obligations.

A separate retention rule applies to security and audit logs. They are not deleted together with all other data by default; no uniform deletion period is promised for all data.

Deleting account and data

Deletion is not the same as deactivating access. Deactivation blocks access, while working-time, payroll and receipt data subject to statutory retention may continue to be stored.

The page Account & data explains how to submit a request and which distinctions apply.

Your rights

Depending on applicable law, you have the right to information, correction, deletion, restriction of processing, data portability and objection. Consent given can be withdrawn with effect for the future.

Please contact your company first, as it is responsible for employee data. The operator supports the company with processing and answers requests concerning its own processing.

Security

Transmission uses HTTPS/TLS. The production configuration uses HSTS, a content security policy, role-based access and strict separation of company data. Security-relevant events may be logged to detect and trace unauthorised access.

No technical system is completely secure. Suspicious observations can be reported via the contact point named on the support page.

Cookies and local storage

The ReiherField web application uses technically required cookies and local browser storage for sign-in, session, language and interface state. This data is required for the application to function.

In its current configuration, this public website sets no cookies and uses no analytics or advertising trackers. Fonts and images are served by the website itself. On the contact page, the Cloudflare Turnstile script may be loaded when spam protection is enabled; this establishes a connection to Cloudflare.

Location data

The native Android app in this version does not request location permission and does not record location histories. The WebView location feature is disabled.

In certain company configurations, the web application may provide a one-time location check at clock-in or clock-out. The company decides whether such a feature is enabled. It is not part of the native Android app in this version.

Children

The service is aimed at employees and companies. It is not intended for children.

Changes to this policy

This privacy policy is updated when features, service providers or legal requirements change. The version published on this page is authoritative.

Contact

Your company or the operator will answer privacy questions via the contact channels named on the support page. Please do not send passwords, full identity documents or health data via a public contact form.

Privacy contact

The operator answers privacy questions via the following address. Data subjects of the application should contact their company first.

Imprint