Data Processing Agreement for onda
Version 2026-11
concluded between the customer who has registered for the software onda, with the company details provided at registration or stored in the Workspace, hereinafter also referred to as the "Controller", and
emergo technologies GmbH, FN 576060 y, Rans 10c, A-6071 Aldrans, Austria, hereinafter also referred to as the "Processor",
as follows:
1. Preamble
1.1 The parties have concluded a contract for the use of the software onda under the Terms of Service for onda (the "Main Contract").
1.2 Under this contract, the Processor processes personal data on behalf of the Controller. To comply with data protection law, the parties conclude this agreement.
1.3 This agreement is concluded electronically (Art 28(9) GDPR): the Controller accepts it when registering for onda. The Processor stores the version accepted, the time of acceptance and the IP address from which it was declared.
2. Definitions
2.1 "Data Protection Law" means Regulation (EU) 2016/679 (the "General Data Protection Regulation", GDPR) and the Austrian Data Protection Act (Federal Law Gazette I No 165/1999), as amended.
2.2 "Personal Data" means any information relating to an identified or identifiable natural person (hereinafter the "Data Subject"); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;
2.3 "Controller" means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data;
2.4 "Processor" means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the Controller;
2.5 "Processing" means any operation or set of operations which is performed on personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.
2.6 "Workspace" means the Controller's workspace in onda at the address name.getonda.io.
3. Description of the Processing
3.1 The subject matter of the commission is the operation of the software onda for the Controller, as described in Annex 3.
3.2 The Processor may process the personal data transmitted by the Controller solely for the purpose of providing the services in accordance with the Main Contract. Any processing beyond this is prohibited.
3.3 The contractually agreed data processing is carried out within the European Union; the software and the databases are operated in data centres of Hetzner Online GmbH in Germany. A sub-processor based in the United States of America is used for sending emails (Annex 2).
3.4 The processing of personal data in a third country is permitted if the requirements of Chapter V GDPR are met. The Processor will verify that these specific requirements are met.
4. Term and Termination
4.1 This agreement applies for as long as the Processor processes personal data on the basis of the Main Contract, including a free trial period and the time until the data is deleted in accordance with clause 7.7.
4.2 This agreement may be terminated in accordance with the provisions of the Main Contract. A declaration concerning the renewal or termination of the Main Contract also applies to this data processing. This also applies if the termination provisions of the Main Contract are changed, so that the Main Contract and this agreement always remain aligned.
4.3 The right to extraordinary termination for good cause remains unaffected. Good cause exists, for example, if a party breaches the data protection provisions of this agreement or of the GDPR.
5. Type of Personal Data
5.1 The Processor will process the data specified in Annex 3.
5.2 This agreement also covers the processing of special categories of personal data under Art 9 GDPR, in particular health data in the form of sick leave that the Controller records as absences. Insofar as the Controller provides the Processor with such categories of data, the Controller guarantees that a corresponding legal basis for the processing under Art 9(2) GDPR (such as point (b), obligations under employment law) is met. The Controller will record in onda only the information required for its purposes (for example the absence as such, not its medical reason).
6. Rights and Obligations of the Controller
6.1 The Controller is solely responsible for assessing the lawfulness of the processing under Art 6, 9 and 10 GDPR (the "Legal Bases") and for safeguarding the rights of Data Subjects under Chapter III GDPR (the "Rights of Data Subjects").
6.2 If the Controller detects irregularities when reviewing the results of the commission or the processing of personal data, it shall inform the Processor without delay.
6.3 All knowledge of the Processor's trade and business secrets, know-how and data security measures obtained in the course of the contractual relationship shall be treated as confidential by the Controller; this obligation survives the termination of this agreement.
6.4 The Controller gives instructions through its use and settings of the software and in text form to support@getonda.io. The Controller shall document all instructions electronically if they are not given in an electronically documented manner. The Controller instructs the Processor to carry out the processing that is necessary or useful for performing the Main Contract.
6.5 The Controller may regularly satisfy itself, in an appropriate manner, of the Processor's compliance with the technical and organisational measures it has taken and with the obligations set out in this agreement.
7. Rights and Obligations of the Processor
7.1 The Processor will process personal data only on the instructions of the Controller. This also applies to transfers of personal data to a third country. Insofar as the list of sub-processors includes companies based in a third country, these are deemed approved by the Controller.
7.2 The Processor ensures the security of processing by complying with, and regularly evaluating and assessing, the measures set out in Annex 1 to this agreement.
7.3 The Processor will charge services provided under this agreement, such as in particular supporting the Controller in fulfilling Data Subject rights or cooperating in inspections, according to the actual effort on an hourly basis at a reasonable rate.
7.4 The Processor is obliged to maintain confidentiality with regard to all personal data disclosed to it by the Controller. The Processor ensures that only employees who need the Controller's personal data to perform this agreement have access to it. These employees are contractually bound to confidentiality and may transfer data only on the express instruction of the Processor. This obligation continues after the end of their employment.
7.5 The Processor will appropriately support the Controller in responding to requests from Data Subjects exercising their rights under Chapter III GDPR. If requests from Data Subjects are received by the Processor in error, it shall forward them to the Controller immediately. The Processor will provide the Controller with all data, documents and information available to the Processor insofar as the Controller needs them to respond to the request.
7.6 The Processor will inform the Controller of a personal data breach ("Data Breach") without undue delay, and no later than 48 hours after becoming aware of it, by email to the Workspace's administrators, so that the Controller can meet its reporting obligations towards the supervisory authority.
7.7 At the Controller's choice, the Processor is obliged either to delete or to return all personal data after the end of this agreement, unless the Processor is obliged to store it under European or national law. If the Controller does not request the return of the data within three months of the end of the contract, this constitutes an instruction to delete the data. By way of exception, Workspaces for which no subscription was taken out after the trial period are deleted 14 days after the end of the trial period in accordance with the Main Contract.
7.8 The Processor is entitled to retain copies of the personal data insofar as they were stored automatically for technical reasons and the copies are encrypted or kept separately. This applies in particular to the encrypted backups under Annex 1 clause 5: deleted data may remain in them for up to 12 months and is then finally deleted as the backups expire. Data from backups is used only to restore operations.
7.9 At the Controller's request, the Processor shall provide all documents and information that the Controller needs to verify the Processor's compliance with its obligations under data protection law.
7.10 The Controller is entitled, with reasonable advance notice, to carry out an inspection at the Processor's premises during normal business hours to satisfy itself that the Processor complies with data protection law.
7.11 The Processor's employees access the Controller's Workspace only insofar as this is necessary to handle a request from the Controller, to remedy faults or to avert security threats. Such access takes place through a dedicated, logged function; every change made in the process is recorded.
8. Sub-processors
8.1 The Processor is granted general authorisation to engage sub-processors to provide the services. The sub-processors listed in Annex 2 are deemed approved. The current list is published at getonda.io/trust/subprocessors/, where planned changes are also announced.
8.2 If the Processor intends to engage an additional sub-processor or to replace an existing one, the Processor will inform the Controller 30 days in advance by email to the Workspace's administrators and announce the change in the published list. If the Controller does not object on objective grounds, the new sub-processor is deemed approved. If the Controller objects on objective grounds, both the Controller and the Processor have the right to terminate this agreement and the Main Contract extraordinarily, without either party being able to derive claims from this.
8.3 If the Processor engages sub-processors to provide the services, the Processor concludes corresponding agreements under Art 28(4) GDPR. These agreements impose on the sub-processors the same data protection obligations to which the Processor is subject.
8.4 Third-party services that the Controller itself connects to its Workspace (such as Toggl Track, Microsoft 365 or an AI assistant through the MCP interface) are not sub-processors of the Processor. Data is transferred to these services on the Controller's instructions.
9. Technical and Organisational Measures
9.1 The Processor takes technical and organisational measures to adequately protect the Controller's data that meet the requirements of the General Data Protection Regulation (Art 32 GDPR).
9.2 The technical and organisational measures shall ensure the ongoing confidentiality, integrity, availability and resilience of the systems and services related to the processing.
9.3 Annex 1 describes the technical and organisational measures the Processor has taken. The Controller confirms that these measures comply with Art 32 GDPR. The Processor is entitled to change these measures unilaterally provided that the level of protection achieved by Annex 1 is not reduced. On request, the Processor sends the Controller the technical and organisational measures in force at that time.
10. Liability
10.1 The Processor's liability for slight negligence is excluded. Likewise, the Processor is not liable for indirect damage, consequential damage, data loss or loss of profit.
10.2 In particular, the Processor is not liable for whether a corresponding legal basis exists in the relationship between the Controller and the Data Subject. If the Processor is held liable by third parties, the Controller shall indemnify and hold the Processor harmless.
11. Final Provisions
11.1 The parties agree that this agreement is governed by Austrian law, excluding its conflict-of-laws rules and the UN Convention on Contracts for the International Sale of Goods, and agree on the exclusive jurisdiction of the court in 6020 Innsbruck.
11.2 In the event of contradictions between this agreement and the Main Contract, the provisions of this agreement take precedence with regard to personal data.
11.3 Changes to this agreement must be made in writing; this also applies to any waiver of the written form requirement. The parties further agree that an email or other message in text form satisfies the written form requirement.
11.4 Should a provision of this agreement be or become invalid, this shall not affect the validity of the remainder of the agreement. The invalid provision shall be replaced by a valid provision that comes closest to the economic intent of the parties at the time the agreement was concluded.
11.5 This agreement is provided in German and English. In the event of any contradiction, the German version prevails.
Annexes
- Annex 1 – Technical and organisational measures
- Annex 2 – Sub-processors
- Annex 3 – Description of the processing and type of data
Annex 1 – Technical and Organisational Measures
The measures in clauses 1.1 to 1.5 apply company-wide at emergo technologies GmbH. The remaining clauses describe the operation of the software onda.
1. Confidentiality (Art 32(1)(b) GDPR)
1.1 Physical and system access control
emergo's corporate network is cloud-based, which means that all infrastructure is hosted in the cloud. Access to these systems is only possible with personal credentials.
In addition, emergo follows the "need-to-know" principle of access control, which ensures that employees are only given access to specific resources if this is necessary for their tasks or roles. This ensures that users can only access the resources relevant to them.
A single sign-on (SSO) system is provided through a directory service, with systems connected via SAML and SCIM. This ensures that only authorised persons have access to the resources.
All devices used in the company are fully encrypted. Passwords are managed exclusively through a password manager (Bitwarden), which is subject to role-based access control (RBAC) policies.
Employees receive regular training and awareness on security topics and are instructed to use FIDO2 authentication with YubiKeys.
Sensitive data is stored on employees' systems encrypted with individual PGP keys. Central systems log the use of user accounts (access logs).
1.2 Data access control
There are concepts for managing and documenting differentiated permissions, which specify how hierarchical groups and roles are to be designed and used on the platforms in use.
At emergo there is a general allocation of roles, which becomes more granular in individual areas, for example the role of a developer who receives roles on infrastructure systems that correspond to their work and are in turn linked to specific access permissions.
1.3 Clean desk policy
Devices must be configured to lock the screen automatically after 5 minutes of inactivity and to require a password or biometric access (e.g. Touch ID) to unlock.
Employees undertake to actively lock their screen when leaving their workstation.
Employees undertake to ensure that unauthorised persons cannot see their screen if sensitive data (e.g. customer data or secrets) could be visible on it. This means that certain work may not be carried out in public places, such as cafés.
1.4 Transfer control
It is ensured that personal data cannot be read, copied, altered or removed without authorisation during transmission or storage on data carriers, and that it can be verified which persons or bodies have received personal data. The following measures are in place for this: device management (see clause 1.5) and regular compliance checks.
1.5 Device management
Employees' laptops are managed centrally through Apple Business device management, where a mandatory policy requires the devices' disks to be encrypted.
1.6 Access to onda's production systems
Only named administrators have access to onda's servers, and only via SSH with hardware-bound FIDO2 keys (YubiKeys). Database administration interfaces cannot be reached from the internet, only through an SSH tunnel. The platform's internal administration interface can only be reached from approved IP addresses; platform administrators must authenticate with a second factor (TOTP) at every sign-in.
1.7 Sign-in of the Controller's users
Users sign in through an identity service operated by the Processor itself (Keycloak). Passwords must be at least 12 characters long and must not match the username or email address; they are stored only as a hash. Repeated failed sign-ins are slowed down by brute-force protection. Users can enable two-factor authentication (TOTP). Sessions expire after inactivity and after a maximum duration. Users cannot register themselves; they are invited by the Controller.
1.8 Access by the Processor's employees to Workspaces
The Processor's employees access a Workspace only in accordance with clause 7.11 of this agreement, through a dedicated function; every change made in the process is logged.
2. Integrity (Art 32(1)(b) GDPR)
Access to the production systems and the operations carried out there are recorded in the system logs of the Linux servers in use. In addition, the central systems log the use of user accounts (see clause 1.1).
In onda, sign-ins and administrative operations of the identity service are logged and kept for 30 days. Platform administration operations (such as creating, locking or changing Workspaces) are recorded in a separate audit log. Changes to time entries and tasks are stored traceably in a change history.
3. Encryption (Art 32(1)(a) GDPR)
All data transfers between users and the software take place exclusively over TLS-encrypted connections (encryption in transit). The software's services (application, database, identity service, file storage) communicate with each other within an isolated internal network on the same server; emails are sent to the email service provider encrypted.
Credentials for integrations that the Controller stores in onda (such as for Toggl or Microsoft 365) and other settings are additionally stored in the database encrypted at application level. Backups are encrypted before they leave the server (see clause 5). Employees' devices are fully encrypted (see clauses 1.1 and 1.5).
4. Separation control
The data of individual customers is logically separated (tenant separation). Every record belongs to a Workspace; the database itself enforces the separation through row-level security, so that even in the event of a programming error the application can only read or change data of the respective Workspace. The application's database user cannot bypass these rules. File attachments are stored in a separate storage area for each Workspace. The separation is checked by automated tests with every change to the software. Platform administration runs separately from the application with its own, restricted database permissions.
Test and development environments contain no customer data.
5. Availability and resilience (Art 32(1)(b) and (c) GDPR)
onda's databases and file attachments are backed up daily. The backups are encrypted with AES-256 before transfer and stored in separate storage at a different location from the server; the storage provider sees only encrypted data. The backups are protected against deletion and modification for 30 days (object lock). 7 daily, 4 weekly and 12 monthly backups are kept; the keys are held by at least two people. A full restore has been tested (restored in 22 minutes, October 2026).
6. Secure development
Changes to the software are made through pull requests and pass automated tests, including tests of tenant separation and static type checks. Dependencies are checked automatically for known vulnerabilities, and before every commit a check ensures that no credentials enter the source code. Operational secrets are managed in encrypted form. The security of the software is reviewed in internal reviews.
7. Procedure for regular testing, assessment and evaluation (Art 32(1)(d) GDPR)
The technical and organisational measures are evaluated and assessed annually and adapted to the state of the art where necessary. Restoring from backups is tested as part of this evaluation.
Annex 2 – Sub-processors
| Company | Activity | Privacy policy | Seat / place of processing |
|---|---|---|---|
| Hetzner Online GmbH | Hosting: onda's servers, databases and file storage | https://www.hetzner.com/legal/privacy-policy | Germany; data centre in Germany |
| Hetzner Online GmbH | Storage for the encrypted backups (separate from the server; encrypted data only) | https://www.hetzner.com/legal/privacy-policy | Germany; data centre in Germany, at a different location from the server |
| Twilio Inc. – SendGrid | Sending onda's emails (invitations, links to set a password, notifications about absences, tasks and time tracking) | https://www.twilio.com/en-us/privacy | USA – Twilio Inc. is certified under the EU-U.S. Data Privacy Framework (Art 45 GDPR); in addition, Standard Contractual Clauses in Twilio's Data Protection Addendum (Art 46(2)(c) GDPR) |
| Stripe Payments Europe, Limited | Payment processing and invoices; only the Controller's contact and billing details, no Workspace content | https://stripe.com/privacy | Ireland |
Annex 3 – Description of the Processing and Type of Data
Description of the processing
onda is software for agencies and service businesses. The Processor operates it for the Controller in a dedicated Workspace. The data entered by the Controller and its users is stored, displayed and evaluated: absences and balances (vacation, time off in lieu, public holidays, statutory leave), working time and time tracking, capacity and project planning, cost, revenue and cash-flow planning, and tasks with comments and file attachments. onda sends notifications by email, for example about absence requests, tasks and time tracking. The data is accessed through the web application and the mobile and desktop applications. The Processor backs up the data (Annex 1 clause 5) and provides support (clause 7.11).
If the Controller connects third-party services (such as Toggl Track or Microsoft 365), onda exchanges data with these services on its instructions (clause 8.4).
Categories of Data Subjects
- The Controller's employees, partners and freelancers (users of the software and people managed in the Workspace)
- Guests, meaning people outside the Controller's company (such as its clients) with whom projects are shared
- Contact persons at the Controller's clients and projects
- Senders and recipients of emails that the Controller turns into tasks
Type of data
- Master data: name, email address, role, team, country or location (for public holidays), period of employment, agreed working hours
- Sign-in and log data: credentials (password as a hash), two-factor authentication settings, time and IP address of sign-ins
- Working time and time tracking data: time entries, projects and activities, time balances
- Absences: vacation, time off in lieu, sick leave (health data, see clause 5.2), parental leave, vacation entitlements and balances
- Cost and financial data: salaries or hourly costs, hourly rates, fees of partners and freelancers, project budgets, revenue and costs
- Content: projects, clients, tasks, comments and file attachments created by the Controller and its users
- Data from connected services: such as time entries from Toggl or emails from Microsoft 365 that are turned into tasks, if the Controller connects these services
Retention
At the Controller's discretion: data remains stored until the Controller or its users delete it. Deleted data is removed from the system immediately and remains only in the encrypted backups for up to 12 months (clause 7.8). Sign-in logs are kept for 30 days. After the end of the contract, clause 7.7 applies; Workspaces without a subscription are deleted 14 days after the end of the trial period, and Workspaces in which nobody signs in within 7 days of registration are deleted after those 7 days.