Data Processing Agreement
Version 1.1 · Effective November 5, 2026This Data Processing Agreement ("DPA") applies whenever Appelium GmbH processes personal data on behalf of a customer while providing the Appelium Dashboard, APIs and SDKs (the "Services"). The customer is the controller and Appelium GmbH is the processor. The DPA is concluded when the customer registers for the Services and forms part of the agreement for the Services, which consists of our Terms of Service or an individually signed agreement. Customers who need a countersigned copy can request one.
1. Structure
This DPA consists of:
- these terms;
- the standard contractual clauses between controllers and processors adopted by the European Commission in Implementing Decision (EU) 2021/915 (the "Clauses"), which are incorporated into this DPA by reference and apply without modification;
- the Swiss addendum in section 4; and
- Annexes I to IV below, which complete the Clauses.
In case of a contradiction, the Clauses prevail over these terms and over any other agreement between the parties (Clause 4).
2. Options selected in the Clauses
- Clause 1(a): Option 1, Article 28(3) and (4) of the GDPR. References to Regulation (EU) 2018/1725 do not apply.
- Clause 5 (docking clause): not used.
- Clause 7.7(a): Option 2, general written authorisation. The agreed list of sub-processors is Annex IV. Appelium informs the customer of any intended addition or replacement of a sub-processor at least 30 days in advance, by email to the customer's workspace administrators and on the Security & Trust page. The customer may object in writing within that period on reasonable data protection grounds. If the parties cannot resolve the objection, the customer may terminate the affected Services.
- Clauses 8(c)(4), 9.1(b), 9.1(c) and 9.2: Option 1, referring to the GDPR.
3. Additional commitments
The following terms complement the Clauses and do not limit them.
- Instructions: the agreement for the Services and the customer's configuration of the SDKs and the Dashboard, including the features it enables, the data retention of its plan and the deletions it makes, are the customer's documented instructions.
- Personal data breaches: Appelium notifies the customer under Clause 9.2 without undue delay and at the latest within 48 hours after becoming aware of a breach, by email to the customer's workspace administrators.
- Data subject requests: Appelium forwards requests it receives about the customer's data to the customer without undue delay and does not answer them itself unless the customer authorises it. Annex III describes how Appelium assists.
- Audits: Appelium first answers the customer's information requests and security questionnaires. Where these are not sufficient, the customer may carry out an audit once per calendar year, and additionally after a personal data breach, where there are indications of non-compliance or where a supervisory authority requires it. Audits are announced at least 30 days in advance, except after a breach, are carried out during business hours under confidentiality, and are at the customer's cost.
- Sensitive data: the Services are not designed to process sensitive data within the meaning of Article 9 GDPR or Article 5 letter c FADP. The customer does not configure the SDKs to send such data and uses the available filters and its own app design to keep it out of screenshots, screen recordings, logs and attachments.
- Location: Appelium stores the customer's personal data in Switzerland, in the AWS Zurich region, except as described for the sub-processors in Annex IV.
- End of the agreement: under Clause 10(d), the customer can ask Appelium to delete its personal data or to return it. During the term, the customer can retrieve its data at any time through the Dashboard and the APIs. On request, Appelium returns the personal data in a common machine-readable format of its choice, such as CSV or JSON, together with the screenshots, screen recordings, activity logs and attachments of the customer's reports and test runs. Aggregated statistics that do not relate to an identifiable person are not personal data and are not part of the return. Without an instruction within 30 days after the end of the agreement, Appelium deletes the customer's personal data and confirms the deletion on request. Deleted data disappears from backups within two days, when the nightly backups are replaced.
- Governing law: this DPA is governed by Swiss law. The place of jurisdiction is Zurich, Switzerland, subject to mandatory provisions of the GDPR on remedies and jurisdiction.
4. Swiss addendum
Where the processing is subject to the Swiss Federal Act on Data Protection (FADP):
- references to the GDPR in the Clauses are to be read as references to the corresponding provisions of the FADP, in particular Article 9 (processing by processors) and Article 24 (reporting of data security breaches);
- the competent supervisory authority includes the Federal Data Protection and Information Commissioner (FDPIC);
- "Union or Member State law" includes Swiss law; and
- the Clauses also protect the personal data of persons in Switzerland.
5. International transfers
Appelium is established in Switzerland and processes the customer's data in Switzerland. The European Commission recognises that Switzerland provides an adequate level of data protection (Decision 2000/518/EC), so customers in the EU and EEA can transfer personal data to Appelium without additional transfer safeguards. Transfers to sub-processors in other countries follow Clause 7.8, using the European Commission's standard contractual clauses for international transfers and, for data subject to the FADP, their adaptation recognised by the FDPIC.
Annex I: List of parties
Controller
The customer, as identified by the company name and address in its Appelium account and billing details, or in the countersigned copy of this DPA. Contact: the customer's workspace administrators. Accession date: the date of registration for the Services or of the countersignature.
Processor
Appelium GmbH, Würzwies 10, 8064 Zürich, Switzerland (UID CHE-378.199.509). Contact for data protection: support@appelium.com.
Annex II: Description of the processing
Categories of data subjects
- Users of the customer's apps.
- The customer's employees, testers and contractors who report bugs, run UI tests or are invited to distribution groups.
- Other persons whose data appears in content the customer chooses to send, such as screenshots, screen recordings, logs or attachments.
Categories of personal data
Every SDK feature is off by default, so only the data of the features the customer enables is processed:
- Identifiers: random identifiers generated by the SDK (never advertising identifiers) and a user identifier, if the customer's app sets one.
- Device and app details: device model, operating system, locale, language and app version.
- Crash and error reports: stack traces, error messages, console and network logs, and attachments.
- Bug reports: the description written by the reporter, an optional email address entered by the reporter, the current screen name, screenshots, screen recordings, console and network logs, and attachments.
- Network monitoring: request URL paths without query parameters, timings, status and error codes, and connection type. Request headers and payloads are included in bug and crash logs only if the customer enables them.
- Sessions and performance: session start and duration, and performance trace names, durations and custom attributes.
- UI test recordings: videos and screenshots of test runs, and test, console and network logs.
- Builds distribution: email addresses of invited testers, uploaded builds and symbol files.
IP addresses of app users are not stored with any of this data.
Sensitive data
None intended; see section 3. The safeguards in Annex III apply to any data that reaches the Services.
Nature of the processing
Collection through the SDKs and APIs, storage, symbolication, grouping of similar reports, statistical aggregation, AI summaries generated by language models that Appelium runs on its own infrastructure in Zurich, display in the Dashboard and through the APIs (including the MCP server that the customer's own AI agents can use), notifications to integrations the customer configures, and deletion.
Purposes
Providing the Services to the customer: crash, error and bug reporting; UI test recording and analysis; network, performance, session and release monitoring; builds distribution; and the related support.
Duration
For the term of the agreement. Data is deleted automatically at the end of the data retention period of the customer's plan, and at the end of the agreement as described in section 3.
Processing by sub-processors
See Annex IV.
Annex III: Technical and organisational measures
Encryption and pseudonymisation
- All connections to the Services are encrypted with TLS, and HTTP Strict Transport Security (HSTS) is enabled.
- Uploaded files, such as screenshots, screen recordings, attachments, builds and symbol files, are stored in Amazon S3 in the AWS Zurich region with server-side encryption (AES-256). Public access to the storage is blocked, and the Dashboard delivers files through signed links that expire.
- Passwords are stored only as bcrypt hashes. Two-factor authentication secrets are encrypted with AES-256-GCM.
- Sessions and active devices are counted with random identifiers generated by the SDK instead of advertising identifiers.
Confidentiality, integrity, availability and resilience
- The Services run on dedicated infrastructure in the AWS Zurich region (eu-central-2). A firewall admits only web traffic (HTTP and HTTPS) and key-authenticated SSH, and the database is not reachable from the internet.
- IP addresses that send repeated invalid requests are blocked temporarily.
- Automated health checks run every five minutes and alert the operations team about database, disk space and data processing problems. Service availability is published on the status page.
Restoring availability
- The database and application volumes are backed up every night as snapshots that AWS stores in the Zurich region, independently of the servers.
Testing and evaluation
- The API, Dashboard and SDKs have automated test suites.
- Appelium reviews these measures at least once a year and after every security incident.
Identification and authorisation
- Dashboard users sign in with a password and optional two-factor authentication (TOTP), which workspace administrators can enforce for the whole workspace.
- Roles (admin, member, tester and agent) limit what each user can do, and requests for workspace data are checked against the signed-in user's workspace, so users can only access their own workspace's data.
- Users can review and end their sign-in sessions in their account activity.
- Access to production systems is limited to Appelium personnel who need it, through personal SSH keys. Diagnostic database access uses a read-only role with enforced statement timeouts.
Physical security
- Servers and storage are located in AWS data centres in the Zurich region. AWS is responsible for their physical security under its certified security programme, including ISO/IEC 27001.
Logging
- Application and web server logs are kept for diagnostics and are rotated automatically.
- Sign-in sessions record the time, browser and approximate location, so users can spot sign-ins they do not recognise.
Data minimisation, default configuration and limited retention
- Every SDK feature is off by default, and each feature collects only what it needs. Network monitoring stores URL paths without query parameters, and network logs support custom filters and obfuscation.
- Data is deleted automatically at the end of the retention period of the customer's plan. Expired sign-in sessions and workspaces that were never activated are deleted automatically.
Accountability and governance
- The management of Appelium GmbH is responsible for data protection and security. Appelium keeps a record of processing activities, a documented incident response procedure and a log of all personal data breaches.
- Personnel with access to personal data are bound to confidentiality.
Assistance to the controller
- In the Dashboard, the customer can delete bug reports, test executions, distribution-group testers, team members and whole applications with all their data.
- On request, Appelium locates, exports or deletes other data, for example all data linked to a user identifier, within 30 days.
- Appelium provides the information the customer needs for data protection impact assessments, consultations with supervisory authorities and breach notifications.
Annex IV: List of sub-processors
The customer authorises the following sub-processors. Each is bound by a data processing agreement with obligations that are, in substance, the same as those in this DPA.
| Sub-processor | Processing | Location |
|---|---|---|
| Amazon Web Services | Application servers, database and file storage | Zurich, Switzerland |
| Amazon Web Services (SES) | Transactional email, such as invitations and alerts | Frankfurt, Germany |
| Amazon Web Services (CloudFront) | Delivery of uploaded files to the Dashboard | Global edge network |
| Infomaniak | Email hosting of our support inbox, including demo requests | Switzerland |

