Data Processing Agreement (DPA)

between

CUSTOMER LEGAL NAME, ADDRESS – hereinafter “Controller” or “Customer” –

and

F.N. Software Studios, sole proprietor Fabian Neumann, Dürener Str. 6, 52445 Titz, Germany – hereinafter “Processor” or “Provider” –

1 Subject Matter and Duration

(1) The Processor processes personal data on behalf of the Controller in the course of providing the OnSite-Soft software under the SaaS agreement concluded between the parties (the “Main Agreement”). Subject matter, nature and purpose of processing, type of data and categories of data subjects are set out in Annex 1.

(2) The term of this DPA corresponds to the term of the Main Agreement including the transition period after termination and subsequent deletion.

(3) Processing takes place exclusively in the agreed data region. For the EU region it takes place exclusively in the European Union / European Economic Area. Any relocation to a third country requires the Controller’s prior documented consent and may only take place if the requirements of Art. 44 et seq. GDPR are met.

2 Instructions

(1) The Processor processes personal data only on documented instructions from the Controller, including with regard to transfers to third countries, unless required to do so by Union or Member State law; in such a case, the Processor informs the Controller of that legal requirement before processing, unless that law prohibits such information.

(2) Instructions are given by the Main Agreement, this DPA and the Controller’s configuration of the Software (e.g. retention periods, mandatory fields, site policies, roles). The Controller issues individual instructions in text form to kontakt@onsite-soft.de.

(3) If the Processor considers that an instruction infringes data protection law, it informs the Controller without delay. It may suspend execution until the Controller confirms or changes the instruction.

(4) Instructions going beyond the contractually agreed scope of services are treated as change requests; the Processor may charge reasonable proven additional effort.

3 Confidentiality

The Processor ensures that all persons authorised to process personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality and process only on the Controller’s instructions.

4 Security of Processing

(1) The Processor takes the technical and organisational measures required under Art. 32 GDPR; they are described in Annex 2 (document “Technical and Organisational Measures”).

(2) The measures are subject to technical progress. The Processor may replace them with equivalent or better measures; the level of protection must not be reduced. Material changes are documented and communicated to the Controller upon request.

5 Sub-processors

(1) The Controller hereby grants general authorisation to engage further processors (sub-processors). The sub-processors engaged at conclusion of the DPA are listed in Annex 3 and are deemed approved.

(2) The Processor informs the Controller at least 30 days before engaging or replacing a sub-processor in text form (email to the stored privacy contact). The Controller may object within this period in text form for an important data protection reason. If the parties cannot reach agreement, either party may terminate the Main Agreement for the affected services effective at the time the new sub-processor is engaged; fees paid in advance are refunded pro rata.

(3) The Processor imposes on each sub-processor by contract the same data protection obligations as set out in this DPA, in particular sufficient guarantees for appropriate technical and organisational measures. It remains liable to the Controller for the sub-processor’s compliance.

(4) Ancillary services without access to the Controller’s personal data (e.g. telecommunications, postal services, cleaning, pure hardware maintenance) or services commissioned by the Controller itself (e.g. its identity provider for SSO, its Microsoft 365 or Slack environment for notifications, Apple for app distribution) are not sub-processing.

6 Assistance to the Controller

(1) The Processor assists the Controller by appropriate technical and organisational measures in responding to requests from data subjects (Art. 12–23 GDPR). The Software includes functions for access, export, rectification and erasure. If a data subject contacts the Processor directly, it forwards the request to the Controller without delay and does not respond itself.

(2) The Processor assists the Controller in ensuring compliance with Art. 32–36 GDPR (security, breach notification, data protection impact assessment, prior consultation), taking into account the information available to it, inter alia by providing the TOMs, the security whitepaper and the DPIA guide.

(3) For assistance going beyond the Software’s functions and the documents mentioned and not caused by a breach of the Processor, the Processor may charge reasonable remuneration on a time-and-materials basis.

7 Personal Data Breaches

(1) The Processor notifies the Controller of a personal data breach without undue delay, at the latest within 24 hours after becoming aware of it, to the stored privacy contact and additionally by phone where a phone number is stored.

(2) The notification contains, as far as known, the information under Art. 33 (3) GDPR (nature of the breach, categories and approximate number of data subjects and records, likely consequences, measures taken or proposed, contact point). Information not yet available is provided without undue delay.

(3) The Processor takes the necessary measures to contain and remedy the breach without delay and documents it. Notifications to supervisory authorities and data subjects are made by the Controller; the Processor assists.

8 Deletion and Return

(1) After the end of the provision of processing services, the Processor deletes or, at the Controller’s choice, returns all personal data of the Controller, unless Union or Member State law requires storage.

(2) The Controller can export the data itself during the term and during a transition period of 30 days after termination. Thereafter the Processor deletes the data from production systems within 30 days. Backups are not purged selectively; they are encrypted, accessible only for restoration and automatically deleted after expiry of the backup cycle (maximum 12 months). If a backup is restored during this time, the Controller’s data is deleted again without delay.

(3) The Processor confirms deletion in text form upon request.

(4) During the term the Software deletes data automatically according to the retention periods configured by the Controller (defaults: visit data 90 days, attendance data 180 days, visitor photos 30 days). Details are set out in the deletion and retention concept.

9 Evidence and Audits

(1) The Processor makes available to the Controller all information necessary to demonstrate compliance with Art. 28 GDPR. Evidence includes in particular the TOMs, the security whitepaper, certifications of sub-processors (e.g. ISO/IEC 27001 of the data centre operator) and responses to security questionnaires.

(2) The Controller or an auditor mandated by it, bound to confidentiality and not a competitor of the Processor, may conduct audits including inspections. On-site audits must be announced at least 30 days in advance, take place during business hours without disrupting operations and at most once per calendar year, unless a specific reason (e.g. personal data breach, order of a supervisory authority) justifies a further audit. Audits of sub-processors’ data centres are carried out by presenting their evidence.

(3) Each party bears its own costs. If the Processor’s effort for an audit without specific reason exceeds one working day, it may charge reasonable remuneration for the additional effort.

10 Official Requests

If the Processor is requested by a supervisory or law enforcement authority, a court or a third party to hand over Controller data, it informs the Controller without delay where legally permitted and hands over data only after examining the lawfulness and to the extent necessary.

11 Liability

Liability towards third parties is governed by Art. 82 GDPR. Between the parties, the liability provisions of the Main Agreement apply unless Art. 82 GDPR mandatorily provides otherwise.

12 Final Provisions

(1) In case of conflict between this DPA and the Main Agreement, this DPA prevails with regard to data protection.

(2) Amendments require text form. Should a provision be invalid, the remainder remains valid. German law applies; place of jurisdiction as in the Main Agreement. In case of discrepancies between language versions, the German version prevails.

Annex 1 – Description of Processing

Nature and purpose

Provision, operation, maintenance, support and backup of the OnSite-Soft software for visitor, attendance, contractor, security and emergency management. Processing operations: collection (via web portal, kiosk, API), storage, organisation, display, matching, transmission to authorised users of the Controller (e.g. host notification by email), badge printing, export, erasure.

Categories of data subjects

Categories of personal data

Special categories under Art. 9 GDPR are not intended. The Controller ensures that free-text fields and records do not contain such data unless it has assessed this separately (e.g. occupational health certificates for contractors). A photo serves only visual verification and is not processed biometrically.

Place of processing

Data region: EU. EU region: Germany (IONOS SE data centre), backup in Frankfurt am Main. Remote access for administration and support by the Processor from Germany.

Annex 2 – Technical and Organisational Measures

The document “Technical and Organisational Measures (TOMs) OnSite-Soft” in the version of 18 November 2026, attached to this DPA, applies.

Annex 3 – Sub-processors

The current list is published by the Processor on onsite-soft.de and in the document “Sub-processor List”.

Legal & privacy