Version 1.1, effective 29 October 2026
This agreement applies when Gitoro ApS processes personal data for a customer. A workspace owner accepts it for their company in workspace settings, Legal, and can then download a copy signed by both parties.
Need it on your own template, or with changed terms? Write to contact@gitoro.com.
| Subject matter | Providing the Service to the Customer under the Main Agreement. |
|---|---|
| Nature and purpose | Hosting, storing, transmitting and displaying the Customer’s repositories and workspace content; running CI/CD pipelines; sending service emails; running AI features the Customer uses, such as AI code review; securing the Service and preventing abuse; support. |
| Categories of data subjects | The Customer’s users (employees, contractors, managed users and service accounts), and any person whose data appears in content the Customer stores, such as commit authors. |
| Types of personal data | Names, usernames, email addresses, profile pictures; authentication data (hashed passwords, passkey and two-factor data, access tokens); Git commit metadata (author names and emails, timestamps); issues, comments, reviews and pull requests; audit log entries and IP addresses; any personal data the Customer chooses to include in repositories, uploads, pipeline logs or artifacts. |
| Special categories | None intended. The Customer should not store special categories of personal data (Article 9 GDPR) in the Service unless agreed in writing. |
| Duration | For the term of the Main Agreement, plus the deletion period in section 10. |
| Location | European Union. |
| Hosting | All production systems run on OVHcloud data centres in the EU. Gitoro is a Danish company and not subject to the US CLOUD Act. |
|---|---|
| Encryption | All traffic to the Service uses TLS (HTTPS and SSH). Git repositories are stored on storage encrypted at rest. |
| Access control | Role-based access control for workspaces and repositories; two-factor authentication and passkeys; scoped, revocable access tokens; branch protection. |
| Internal access | Production access is limited to named personnel who need it, using individual accounts and strong authentication. |
| Logging | An audit log records security-relevant actions in each workspace and is available to the Customer’s administrators. Entries are kept for 12 months unless the Customer’s administrators choose another period, and are deleted together with the workspace. |
| Availability | Repository data is stored as replicas on more than one server in the EU. |
| Secure development | Code review on every change, automated tests, and dependency and secret scanning. |
| AI features | AI models run in the EU, and Customer data is never used to train models. |
| Data minimisation | Customers can export and delete their data at any time. |
| Sub-processor | Purpose | Location |
|---|---|---|
| OVH SAS (OVHcloud) | Infrastructure hosting and storage; AI model hosting (AI Endpoints) | EU (France, Germany) |
| HostYourAI B.V. | AI model hosting for AI features | EU (Netherlands) |
| Mistral AI SAS | AI model hosting for AI features | EU (France) |
| Sendinblue SAS (Brevo) | Sending service emails | EU (France) |
| Mollie B.V. | Payment processing for paid plans | EU (Netherlands) |