Data processing agreement
Version 2026-11-13
This agreement is made between the customer as controller and Wavy AS, org. no. 928 635 015, Herman Foss' gate 21, 0171 Oslo as processor. The customer is the controller of the personal data in the testers' reports and in the code, and reproo processes it as a processor, only on the customer's instructions and to provide the service. The agreement is part of the terms of service, is accepted when a project is ordered or activated, and meets the requirements of GDPR Article 28 and the Norwegian Personal Data Act.
1. Roles
The customer is the controller of the personal data in the testers' reports, in the app data and in the code of the repositories the customer connects. We are the processor and process it only to provide the service to the customer.
For the dashboard's user accounts, the billing details and operational security we are the controller ourselves; this is described in the privacy statement.
2. Purpose, nature and duration
- Purpose: to receive problems reported by testers, investigate them with data from the app and the code in connected repositories, ask the tester follow-up questions, write reports for the customer's team, search the customer's issue tracker for duplicates and – when a person in the team decides so – send the reports there.
- Nature: collection, storage, structuring, analysis (including with AI), combination with code and with issues in the customer's issue tracker, disclosure to the customer's issue tracker and erasure.
- Duration: as long as the customer uses the service, and after that until the data has been deleted or returned under "Deletion and return".
3. Data subjects and data
Data subjects: the customer's testers and users of the app under test, the customer's dashboard users, and people who appear in source code or screenshots.
Data:
- what the tester writes and answers and – when the project asks for it – name and e-mail; user id and role when the app provides them
- technical app data: screen or page and route, device, operating system, browser, language, time zone, app version, feature flags and the custom context the customer allows, recent actions, summaries of network requests without bodies and console messages, the network connection and the time the report was written
- screenshots – attached automatically in the iOS and Android apps, where the tester can remove them, and on the web only when the tester attaches them – and other attachments
- crash data from the iOS and Android apps when the project has crash capture turned on (the default)
- excerpts of source code from connected repositories (the code index)
- issues and comments the team makes from the reports
The service is not designed for special categories of personal data (Article 9) or data about criminal convictions (Article 10). The customer shall not ask testers for such data or send it in the app data. If it nevertheless appears in text or screenshots, it is processed like the rest of the report.
4. The customer's instructions
We process the personal data only on the customer's documented instructions: this agreement, the terms of service and the settings the customer chooses in the service – for example whether name and e-mail are asked for, retention, crash capture, allowed context keys and websites, connected repositories and issue trackers.
We do not process the data for our own purposes, and it is not used to train AI models. If the law requires us to process it otherwise, we inform the customer first unless the law prohibits it. If we believe an instruction infringes data protection law, we say so at once.
5. Confidentiality and access
Everyone with access to the personal data at our end is bound by confidentiality under contract or law. Access is given only to those who need it to operate the service, fix faults or answer the customer's requests, and only as far as needed.
6. Security
We have these measures under Article 32:
- All traffic is encrypted (HTTPS), and the database and file storage are encrypted at rest by the provider.
- Access is controlled per organization and project, also in the database (row-level security). Code and technical details are shown only to users with technical access, and testers never see code.
- Repositories are read through a GitHub App with least privilege: read access to contents and metadata, and access to issues – reading to search for duplicates and show their status, and writing only when a person in the team sends an issue to GitHub Issues or links a report to an issue there.
- Access tokens for issue trackers are stored encrypted (AES-256-GCM), and the testers' access keys are stored only as hashes.
- Sensitive fields (Authorization, cookies, passwords, API keys) are removed from app data, request bodies are not stored, secrets are removed from the code index, and e-mail addresses, phone numbers, national identity numbers, card numbers, account numbers and secrets are removed from text before it is sent to the AI.
- Rate limits and daily caps protect against abuse; the counters are deleted once they are more than a day old. The application logs contain no tester text, AI requests or access keys, and errors sent to error tracking are scrubbed of personal data first.
- The database is backed up daily. The platform team's own dashboard in the service requires that the person is both listed and granted access separately, and only those who operate the service have access to the providers' consoles.
- On the phone, reports waiting for a connection are stored in the app's private area, outside backups.
7. Sub-processors
The customer gives general prior authorization for us to use these sub-processors. Each of them is bound by a data processing agreement with at least the same obligations as this one, and we are responsible to the customer for their compliance.
| Provider | Service | Data | Where | Transfer basis |
|---|---|---|---|---|
| Supabase | Database, sign-in (Supabase Auth) and file storage for screenshots and attachments. | Everything the service stores: user accounts, organizations and projects, reports, conversations, app data, screenshots, crash data, the code index, billing details and e-mails waiting to be sent again. | EU – Frankfurt, Germany (AWS eu-central-1). | Data is stored in the EU. Supabase Inc. is a US company: access from the US for operations and support is covered by the EU standard contractual clauses (SCCs). |
| Vercel | Hosting of the application: the server functions, the web pages, the report form and the scheduled jobs, delivered through Vercel's global network (CDN). | Every request to the service with its content, and operational logs (IP address, time, address and status code). | The server functions run in the EU – Frankfurt (fra1). Requests pass through Vercel's edge network nearest the user, which may be outside the EEA. | Vercel Inc. (US): the EU–US Data Privacy Framework and the EU standard contractual clauses (SCCs). |
| OpenAI | The AI analysis: the follow-up questions to the tester and the report for the team (OpenAI API). | The tester's text and answers and the agent's questions, with e-mail addresses, phone numbers, national identity numbers, card numbers, account numbers (IBAN) and secrets replaced before sending. Technical app data without user id, name, e-mail and session id: environment, app version, page or screen and route, device, operating system, browser, language, the tester's role, feature flags and the custom context the customer allows, recent actions, summaries of network requests and console messages, and the network connection. Crash data (kind, time, error message, the names and messages of the exceptions in the same chain, and the app's own call-stack frames with file and line). The project's name, description, AI instructions and knowledge notes. Excerpts of code from the customer's repositories. Titles and summaries of similar reports and issues in the project and in the issue tracker the customer has connected (to find duplicates), and the conversation of an earlier report when the tester continues it. The team's reason when it dismisses a report as expected behaviour (to suggest a knowledge note). No screenshots or attachments, and no name or e-mail from the contact fields. | United States. | The EU–US Data Privacy Framework and SCCs. Requests are sent with storage turned off (store: false) and are not used to train models; OpenAI may keep them for up to 30 days to detect abuse. |
| GitHub | Access to the repositories the customer connects, through reproo's GitHub App: read access to contents and metadata, and – when GitHub Issues is the project's issue tracker – read access to issues to search for duplicates and show their status, and write access to issues, used only when a person in the team sends an issue to GitHub Issues or links a report to an issue there. | Source code and metadata from the repositories the customer connects. A few keywords from each report when GitHub Issues is searched for duplicates. What a person in the team sends to GitHub Issues through the app: issues with title, description (with the name of the person who reported the problem, when the project asks for names) and labels, and a comment when a report is linked to an issue (summary, link, environment, version, device and browser). | United States. | GitHub, Inc. (Microsoft, US): the EU–US Data Privacy Framework and SCCs. The repositories and issues are hosted by GitHub under the customer's own agreement with GitHub. |
| Resend | E-mail from the service: invitations, sign-in and confirmation links, receipts and notices about invoices and holds, e-mails to the team about new reports, to owners and admins when a project stops taking reports, to owners when a collaborator connects a repository to a project (who and which repository), and alerts to the platform team. Testers get no e-mail. | The recipient's e-mail address and any name, and the content of the e-mail: organization and project names; the name of the person who invited, and the name and e-mail address of the person who activated a project or connected a repository; amounts and due dates in billing notices and the platform team's reason for a hold; report titles; the name of a repository that was connected or removed; and links. | The e-mails are sent from the EU – Ireland (AWS eu-west-1). The API and the sending logs may be processed in the US. | Resend is a US company: the EU standard contractual clauses (SCCs). |
| Sentry | Error tracking, when it is turned on: errors in the servers and in the dashboard in the browser are reported to the platform team. Never in the report form, the hosted report page or the status page. | Error events scrubbed of personal data: the route (the address without its query, ids replaced), the error type and message (e-mail addresses, access tokens, keys, phone and card numbers removed), the stack trace, the release and the environment. No requests, cookies, headers, users or testers' text. The IP address an error from the browser is sent from is not stored. | EU – Germany (Sentry's EU region). | Data is stored in the EU. Functional Software, Inc. (Sentry) is a US company: access from the US for operations and support is covered by the EU standard contractual clauses (SCCs). |
Before we start using a new sub-processor or replace one, we notify the organization's owners and admins at least 30 days in advance, by e-mail and in a new version of this agreement. The customer may object on reasonable grounds within the notice period. If we find no solution, the customer may terminate the agreement before the change takes effect, without paying for the months after.
The customer's own Jira is not our sub-processor: when the customer connects it, the service automatically searches it for duplicates with a few keywords from each report and reads the title, description and status of the matching issues, and issues are sent there only when a person in the customer's team decides so – all with the customer's own credentials and under the customer's own agreement with that provider. Issues to GitHub Issues are sent through reproo's GitHub App and come under GitHub in the table.
8. Transfers outside the EEA
Personal data is transferred outside the EEA only to the sub-processors in the table, and only on the transfer basis stated there: the EU–US Data Privacy Framework or the EU standard contractual clauses (SCCs). We have assessed the transfers and give the customer a copy of the basis on request.
9. Assistance with data subjects' rights
The customer answers requests from data subjects. We help: at the customer's request we find, hand over, correct or delete the data about a particular tester within 30 days, and usually faster. The platform team does this by hand, following a set routine; the customer names the project and the tester's user id from the app or the e-mail address the tester gave. If a data subject contacts us about data we process for the customer, we pass the request on to the customer without undue delay.
10. Assistance with security and impact assessments
We give the customer the information it needs about the processing and the security measures to meet its obligations under Articles 32 to 36, including for a data protection impact assessment (DPIA) and any prior consultation with the Data Protection Authority. Reasonable assistance is included in the price.
11. Personal data breaches
If we become aware of a personal data breach affecting the customer's data, we notify the customer without undue delay and at the latest 48 hours after becoming aware of it, by e-mail to the organization's owners. The notice describes, as far as we know: what has happened, which categories and roughly how many data subjects and records are concerned, the likely consequences, what we have done and propose, and whom the customer can contact. What we do not know yet follows later.
We document the breach and help the customer notify the Data Protection Authority and, where required, the data subjects.
12. Documentation and audits
We keep a record of the processing we carry out as processor (Article 30(2)), and give the customer all the information needed to demonstrate that this agreement and Article 28 are complied with.
The customer, or an independent auditor chosen by the customer and bound by confidentiality, may audit us with at least 30 days' written notice, at most once a year unless a breach or an authority gives reason to. Each party covers its own costs. For the sub-processors we rely on their audit reports and certifications.
13. Deletion and return
While the agreement runs, reports, conversations, screenshots and attachments are deleted after the retention period the customer has chosen for the project (365 days for new projects, unless the customer chooses otherwise), tester sessions without reports after the same retention period, and a repository's index when the repository is disconnected. Issues the team has made from the reports are kept, but the name of the person who reported the problem is removed from them the night after the report is deleted. On the phone, reports waiting for a connection are kept for at most 7 days.
When the agreement ends, the customer may within 30 days ask to receive the reports with conversations and attachments in a machine-readable format. At the latest 30 days after the end – or after the hand-over – we delete all personal data we have processed for the customer, including issues, code indexes and user accounts that belong only to the customer. The platform team does the hand-over and the deletion by hand, following a set routine. The data disappears from backups when the copies are replaced, at the latest 30 days later. Accounting records and the documentation of who accepted which agreements are kept as described in the privacy statement. We confirm the deletion in writing on request.
14. Term, changes and governing law
The agreement applies as long as we process personal data for the customer. It is changed as described in the terms of service ("Changes to the terms"), and who accepted which version is recorded.
The parties' liability follows from GDPR Article 82 and the terms of service. In case of conflict, this agreement takes precedence over the terms for the processing of personal data.
The agreement is governed by Norwegian law, with Oslo District Court as venue. Contact about privacy and breaches: lasse@wavy.no.