Skip to content
FFrieda HR
Features Security Pricing Calculators FAQ
DeutschDE Sign in Start for free

Data processing agreement (DPA)

This English version is provided for convenience; the German version is binding.

Last updated: 5 October 2026

between the customer as controller (“customer”) and Durn Studio UG (haftungsbeschränkt), Kienitzer Str. 5, 12053 Berlin, Germany, as processor (“we”). The agreement is part of the terms and is concluded with the contract for the use of Frieda HR. It meets the requirements of Art. 28 GDPR.

  1. § 1 Subject and term
  2. § 2 Instructions
  3. § 3 Confidentiality
  4. § 4 Security of processing
  5. § 5 Sub-processors
  6. § 6 Transfers to third countries
  7. § 7 Assisting the customer
  8. § 8 Personal data breaches
  9. § 9 Deletion and return
  10. § 10 Evidence and audits
  11. § 11 Liability
  12. § 12 Final provisions

§ 1 Subject and term

  1. We process personal data on behalf of the customer in order to provide Frieda HR under the terms. The nature and purpose of the processing, the types of data and the categories of data subjects are described in Annex 1.
  2. The agreement applies as long as we process the customer's data, at least for the term of the contract for Frieda HR.

§ 2 Instructions

  1. We process the data only on documented instructions from the customer, unless EU or German law requires us to do so. In that case we inform the customer beforehand, unless the law prohibits this.
  2. Instructions are this agreement, the terms, and the customer's settings and actions in Frieda HR. The customer gives further instructions in text form to hi@friedahr.com.
  3. If we consider an instruction unlawful, we tell the customer without delay. We may suspend it until the customer confirms or changes it.

§ 3 Confidentiality

  1. Anyone at our company with access to the data is bound to confidentiality or subject to a statutory duty of secrecy, and accesses data only as far as needed for the service.
  2. We see employees' data in support only when the customer grants access in Frieda HR. The access is time-limited, the customer can end it at any time, and every access is logged.

§ 4 Security of processing

  1. We take the technical and organisational measures under Art. 32 GDPR described in Annex 2.
  2. We may develop the measures further as long as the level of protection does not drop.

§ 5 Sub-processors

  1. The customer authorises us to use the service providers in the list of sub-processors as sub-processors.
  2. We announce new or changed sub-processors by e-mail at least four weeks in advance. The customer may object within this period for an important reason relating to data protection. If we do not find a solution, the customer may terminate the contract as of the date of the change.
  3. We bind every sub-processor by contract to the same data protection obligations and remain responsible to the customer for it.
  4. If the customer connects Frieda HR to their own accounts with other providers (such as Google Workspace, Microsoft or Slack), we transfer data there on the customer's instruction; these providers are the customer's own service providers. We use the AI assistant only while the customer has switched it on.

§ 6 Transfers to third countries

We store the data in the EU. If a sub-processor is based or processes data outside the European Economic Area, we ensure the requirements of Art. 44 et seq. GDPR are met, for example through an adequacy decision (EU-US Data Privacy Framework) or the EU standard contractual clauses. The list of sub-processors names the basis for each provider.

§ 7 Assisting the customer

  1. Frieda HR includes features with which the customer answers requests from data subjects: access and export, rectification and erasure. If a data subject contacts us directly, we forward the request to the customer without delay.
  2. We assist the customer with the information available to us in meeting their obligations under Art. 32 to 36 GDPR (security, notifications, data protection impact assessment, prior consultation).

§ 8 Personal data breaches

  1. If we become aware of a breach affecting the customer's personal data, we notify the customer's owners and HR admins by e-mail without undue delay, where possible within 24 hours.
  2. The notification contains, as far as known, the information under Art. 33(3) GDPR; we provide anything missing as soon as we have it. We take immediate measures to contain the breach and mitigate its consequences.

§ 9 Deletion and return

  1. Until the contract ends, the customer can export their data; on request they receive a copy in a common, machine-readable format.
  2. After the contract ends, we delete the data within 30 days unless EU or German law requires us to keep it. Backups are overwritten within a further 30 days at the latest; once the company's keys are deleted, its encrypted content can no longer be read even before that. On request we confirm the deletion in text form.

§ 10 Evidence and audits

  1. We provide the customer with the information needed to demonstrate compliance with this agreement, in particular this page with its annexes and the list of sub-processors.
  2. The customer, or an auditor bound to confidentiality and appointed by the customer, may audit compliance at most once a year, announced 30 days in advance and during normal business hours, or more often if there are specific indications of a breach. The audit must not disrupt operations or the confidentiality of other customers' data. The customer bears the costs unless the audit reveals a material breach.
  3. Instead of an on-site audit, suitable evidence may suffice, such as certificates or audit reports of our data centre providers.

§ 11 Liability

Liability towards data subjects is governed by Art. 82 GDPR. Between the customer and us, the rules of the terms apply.

§ 12 Final provisions

  1. On data protection matters, this agreement takes precedence over the terms.
  2. Changes to this agreement follow § 14 of the terms.
  3. German law applies. The place of jurisdiction is Berlin, where legally permitted.

Annex 1 – Subject of the processing

Nature and purpose

Providing HR software: personnel files and contracts, vacation and absences, sick leave, time tracking and shift planning, payroll estimates and export to the tax advisor (DATEV), documents and payslips, applications, and notifications by e-mail, in the app and as push notifications. The processing covers storing, organising, displaying, calculating, transferring to recipients chosen by the customer, and deleting.

Types of data

  • Master data: name, contact details, address, date of birth, nationality, personnel number, department, position, manager
  • Contract data: start and end, probation, working hours and days, vacation entitlement, pay and allowances
  • Absences: vacation, sick leave (without diagnosis), parental leave and other absences
  • Working time and shifts
  • Payroll data: tax class, tax ID, social security number, health insurer, church tax status, child allowances, bank details (IBAN)
  • Documents: contracts, certificates, sick notes, residence permits, payslips
  • Applications (if the customer uses recruiting): contact details, CV, cover letter, ratings, interview dates
  • Account and log data: e-mail address, sign-ins, IP addresses, devices for push notifications, change and access logs

Special categories (Art. 9 GDPR)

Health data in the form of sick leave and sick notes (without diagnosis); religious affiliation as far as it follows from the church tax status.

Data subjects

Employees and former employees, trainees, applicants, the customer's users (for example HR and managers) and the customer's contact persons.

Annex 2 – Technical and organisational measures

1. Confidentiality

  • Physical access: no servers of our own; our providers' data centres in the EU are audited under ISO 27001 or SOC 2.
  • System access: sign-in by e-mail link or company login (SSO); two-factor sign-in for owners, HR and our operations team; sessions end after twelve hours at most and after one hour without activity; HR and the customer's identity provider (SCIM) can block accounts immediately.
  • Data access: roles per company; for every request the database checks with row-level rules which data the person may see; only HR and the person see sick notes; our operations team sees no employee data, in support only with the customer's approval and logged.
  • Separation: tenant separation in the database that technically rules out references between companies; test and staging systems hold no real data.
  • Encryption: transfer only over TLS (HSTS); encrypted disks (AES-256); tax ID, social security number, IBAN and all documents additionally encrypted with each company's own keys (AES-256-GCM), protected outside the database.

2. Integrity

  • Input control: a log of every change to business data (who, when, what) that users cannot alter; logs of document downloads and of revealing sensitive fields.
  • Transfer control: encrypted transfer only; uploaded files are checked (file type, virus scan, removal of active content) and delivered only as attachments; limits and alerts for unusually many downloads.

3. Availability and resilience

  • Daily database backups.
  • Protection against attacks and overload (web application firewall, DDoS protection), request limits, database time limits.
  • Monitoring with alerts to the operations team and the customer's HR.

4. Regular review

  • Automated tests on every change, including the database's access rules.
  • Checks of the software libraries used for known vulnerabilities.
  • Changes reach production only after tests in a staging environment and an approval.
  • An incident plan for data breaches; review of these measures at least once a year.

5. Deletion

  • Retention periods for documents and applications with automatic deletion.
  • Deleting a company's keys makes its encrypted data unreadable, also in backups.

Annex 3 – Sub-processors

The service providers we use are in the list of sub-processors.

← Back to the home page

FFrieda HR

HR software for small teams in Germany. Made in Berlin.

Product

  • Features
  • Security
  • Pricing
  • Calculators
  • Mobile app

Account

  • Sign in
  • Create a company

Legal

  • Legal notice
  • Privacy
  • Terms
  • Data processing (DPA)
  • Sub-processors
© 2026 Frieda HR Deutsch · English

May Meta measure your visit?

We'd like to see whether our ads on Facebook and Instagram work. For that, the Meta Pixel sets cookies and sends usage data to Meta, including to the USA. This only happens if you agree, and you can withdraw at any time under “Cookie settings” at the bottom of the page. More in the privacy policy.