Skip to content

Arkiviva Data Processing Agreement

Version: 1.0. Effective date: 16 November 2026.

1. About this DPA

1.1 This data processing agreement (the "DPA") is between Arkiviva Limited ("Arkiviva", "we", "us", or "our") and you, our customer under our Terms of Service (the "Terms"). Arkiviva is registered in Ireland under CRO number 822797. Our registered office is Unit 2, 2 Bridge Street, Athlone, Co. Westmeath, N37 F1W4, Ireland, and our email address is legal@arkiviva.com.

1.2 This DPA forms part of your contract with us and applies whenever we process personal data on your behalf. The version that applies to you is the one sent with your confirmation email, as changed under section 17.

1.3 In this DPA:

a. "GDPR" means Regulation (EU) 2016/679. Words that the GDPR defines have the same meaning here.

b. "Customer personal data" means personal data we process on your behalf under this DPA.

c. Other words that the Terms define have the same meaning here.

d. A section or annex number refers to this DPA, unless it says "of the Terms".

1.4 If the UK GDPR or Swiss data protection law applies to your processing, references to the GDPR include the matching provisions of that law.

2. Roles

2.1 You are the controller of customer personal data, or you are a processor acting for another controller. We are your processor, or your subprocessor if you are a processor.

2.2 If you are a processor:

a. you must make sure your controller has authorised your instructions, our appointment, our subprocessors, and the uses in section 5, and that this DPA meets the requirements of your contract with your controller;

b. we deal only with you, not with your controller; and

c. you must pass on to your controller any information and notices we give you under this DPA.

2.3 If your own processing of personal data falls outside the GDPR, we still process that data only on your instructions and as this DPA describes.

2.4 For an Organization, the customer is its Sponsor or, if the Sponsor acts for a company or other organisation, that organisation (section 3 of the Terms). That customer gives the instructions for the Organization's customer personal data. If an Organization has no Sponsor, its owners give them. We may treat anything an owner of the Organization does in the service as that customer's instruction.

2.5 Notices. We may give you notices under this DPA by email to your most recently supplied contact details (section 19 of the Terms) or, unless this DPA requires email, by any other method we choose. For an Organization that has no Sponsor, we give notices to its owners. You must monitor the contact details you give us.

3. Your duties

3.1 You must:

a. decide whether the service, this DPA, and the measures in Annex 2 are right for the personal data you put in it, and carry out any data protection impact assessment and prior consultation the law requires; and

b. tell us promptly at legal@arkiviva.com if you learn of a personal data breach that affects the service, or of any failure to comply with this DPA that affects the service, and give us the information you have that we need to investigate and deal with it.

3.2 Subject to section 3.3, you must not put special categories of personal data, personal data about criminal convictions and offences, or children's personal data in the service unless you have decided that our measures are right for that data. We do not have to find out what customer personal data contains. If you put such data in the service, you are responsible for any further safeguards that the law requires you to take for it.

3.3 Restricted data. Without our prior written consent, you must not put in the service:

a. protected health information under the US Health Insurance Portability and Accountability Act;

b. criminal justice information under the US Criminal Justice Information Services Security Policy;

c. education records under the US Family Educational Rights and Privacy Act or similar laws;

d. personal data from clinical trials or other research involving human subjects; or

e. biometric data.

3.4 Your review. If you are a business customer, you confirm that before accepting this DPA you reviewed it, its annexes, and our subprocessor list, and decided that they give sufficient guarantees for your processing.

4. Your instructions

4.1 We process customer personal data only on your documented instructions. Your instructions are:

a. the Terms, your Offer, and this DPA;

b. how you, your authorised users, and anyone using your account or credentials set up and use the service, including the integrations and runners you enable (section 9 of the Terms); and

c. any other instruction we agree to in writing.

4.2 These instructions cover the processing described in Annex 1 for the features you use, including applying the plan, storage, and usage limits in your Offer, and securing, maintaining, updating, and troubleshooting the service.

4.3 Your instructions include restoring backups to separate, isolated systems to check recovery and to test updates before we apply them.

4.4 You, and the people you allow, decide what content you control contains, whether it is public, and who can see it. Apart from sections 5.1(e) and 5.1(f), we make customer personal data public only on your instructions. Removing or restricting content under section 8 of the Terms does not change this. Before you or your authorised users make content public, you must check it, including its Git history, for personal data, and make sure that publishing that data is lawful.

4.5 Legal requirements. We may process customer personal data without your instruction where EU or Member State law that applies to us requires it. Before we do, we will tell you about that legal requirement, unless that law forbids this on important grounds of public interest.

4.6 Lawfulness of instructions. You are responsible for making sure that your instructions are lawful. If you are a business customer, you alone are responsible for that and for making sure that following your instructions will not make us break the law. We do not have to check which laws apply to you or whether your instructions are lawful. We will tell you immediately if we believe an instruction breaks the GDPR or other EU or Member State data protection law. We may suspend or refuse an instruction that we believe is unlawful or insecure, or that is outside the service. If you do not change or withdraw it, we may suspend or end the affected service where section 13 of the Terms allows.

4.7 Reliance and results. We may rely on any instruction given through your account, your credentials, or your Organizations, and we do not have to check whether the person who gave it had your authority. We are not responsible to you for the results of our following your instructions, including any deletion, disclosure, transfer, or publication of customer personal data that they cause. This does not apply to the extent we did not follow your instructions or breached the Terms, this DPA, or data protection law.

5. Where we are an independent controller

5.1 We are an independent controller, not your processor, when we process personal data, including personal data in your content and in the other data listed in Annex 1, for these purposes:

a. Accounts and billing:

i. creating and administering accounts, Organizations, and Sponsor roles;

ii. authentication and account security;

iii. storage allowances and entitlements;

iv. billing and payments; and

v. communicating with you.

b. Security and abuse prevention:

i. protecting the service, Arkiviva, our users, and others;

ii. preventing, detecting, and investigating spam, malware, fraud, abuse, and security incidents; and

iii. handling reports and enforcing the Terms.

This includes automated tools that may make decisions on their own, and developing and training non-generative models that detect spam, malware, fraud, or abuse. It does not include the security measures we take for customer personal data under section 7 and Annex 2, or our handling of personal data breaches under section 11, which we carry out as your processor.

c. Legal compliance: complying with legal obligations under EU or Member State law that apply to us in our own right, and establishing, exercising, or defending legal claims. An order or request that requires us to produce or otherwise process customer personal data we hold for you falls under section 4, not under section 5.1(c).

d. Service analytics: operating, planning, and improving the service, using our own records of how the service is used and how it performs, and aggregated or de-identified statistics drawn from those records. We do not use the content you store for this purpose.

e. Demonstrating the service: using public content to demonstrate or promote public search and collaboration (section 5.2(e) of the Terms).

f. Promotion: naming a business customer as a current or former customer, using its business names and marks (section 18.2 of the Terms), and, with the consent of the person concerned, using a person's name, words, or photo in our promotion, for example in a quote.

5.2 You authorise us to use that data for these purposes. Before we start a use in section 5.1, our Privacy Notice describes it and its legal basis. Where the law requires it, your own privacy information must cover this disclosure to us.

5.3 Only sections 5 and 6 of this DPA apply to our processing as an independent controller under section 5.1. For all other processing, we act only as your processor. Our role as a controller for the processing in section 5.1 does not, by itself, make us a controller of other processing of content in the service or of its publication.

6. Limits on our use

6.1 For customer personal data, the licence in section 5 of the Terms is limited: we use customer personal data only on your instructions under section 4, or for the purposes in section 5.

7. Confidentiality and security

7.1 We will make sure that everyone we authorise to process customer personal data:

a. is bound by confidentiality, by contract or by law; and

b. processes it only on our instructions, which follow yours, unless EU or Member State law requires otherwise.

7.2 We will take the measures that Article 32 of the GDPR requires, including those in Annex 2, and we review them regularly to keep them appropriate to the risk. We may change our measures, and update Annex 2 to match, if the overall security of customer personal data is not materially reduced; section 17 does not apply to those updates. Annex 2 and this DPA set out all our security commitments for customer personal data under the GDPR.

7.3 You are responsible for the security of what you control, and you must take appropriate technical and organisational measures for it. That includes your credentials, tokens, keys, and secrets, your authorised users' access, your visibility and permission settings, and your integrations and self-hosted runners (sections 3, 5, 6.5, and 6.6 of the Terms). You must give people and integrations only the permissions they need, and promptly remove access and revoke credentials, tokens, and keys that are no longer needed.

7.4 Betas and previews. Annex 2 does not apply to a feature that we label in the service as a beta or preview under section 10 of the Terms, unless we tell you that it does. You must not put customer personal data in such a feature unless Annex 2 covers it. This section 7.4 does not apply to the service as a whole.

8. Subprocessors

8.1 Authorisation. You give us general written authorisation to engage subprocessors, including those on our list at https://legal.arkiviva.com/subprocessors/. The list shows each subprocessor's name, address, contact details, function, and processing locations. Annex 3 shows that list on the date of this version.

8.2 Notice of changes. When we add or replace a subprocessor, we update our list and email you. We do this before the new subprocessor starts processing customer personal data. Apart from the ending terms that section 8.3 uses, section 17 does not apply to changes to our list.

8.3 Objections. If you object to a change to our list, you may end the affected service by notice to legal@arkiviva.com within 14 days after our email. The service then ends on the terms that section 17.2 sets for ending a service after a change to this DPA, including when it ends, the absence of any charge for ending it, refunds, and your remedies. If you do not give that notice within those 14 days, you authorise the change. If you are a consumer, section 14 of the Terms and your statutory rights also apply.

8.4 Our responsibility. We will choose subprocessors that give sufficient guarantees to implement appropriate technical and organisational measures. We will bind each subprocessor by written contract to data protection obligations that are the same in substance as ours under this DPA, as far as they are relevant to its service. We remain responsible to you for how each subprocessor performs those obligations, subject to section 16 of the Terms.

9. International transfers

9.1 You instruct us to process customer personal data in the locations shown on our subprocessor list. We will transfer customer personal data to a country outside the European Economic Area (EEA) only in compliance with Chapter V of the GDPR. Adding a processing location outside the EEA counts as a change under section 8. We give the notice under section 8.2 before processing starts at that location, even if the subprocessor stays the same.

9.2 You or your authorised users may send data to destinations you choose, such as webhooks, mirrors, integrations, OAuth applications, runners, or Git clients. We send that data on your instructions. As between you and us, you are responsible for choosing those destinations, for your arrangements with them, and for making sure the transfer is lawful. Unless we operate them, or a subprocessor operates them for us, those destinations and whoever runs them are not our subprocessors, and we are not responsible for how they process that data.

9.3 Customers outside the EEA. Sections 9.4 and 9.5 apply only if you are located or established outside the EEA and no adequacy decision under Article 45 of the GDPR covers the transfer of customer personal data to you.

9.4 If you act as a processor, or your processing of that data is subject to the GDPR, you must tell us before you use the service for that data, including when section 9.4 starts to apply to you because your location, your role, or your processing changes. We will make it available to you outside the EEA only once a transfer mechanism that is valid for that transfer has been put in place in writing. Until then, you must not access or receive it from outside the EEA.

9.5 Otherwise, if you are the controller of that data and your processing of it is not subject to the GDPR, Module Four (processor to controller) of the standard contractual clauses in Commission Implementing Decision (EU) 2021/914 forms part of this DPA for customer personal data we make available to you. Your acceptance of the Terms is your acceptance of those clauses.

a. We are the data exporter and you are the data importer.

b. Clause 7 does not apply, and neither does the optional wording in Clause 11.

c. Under Clause 17, Irish law governs. If you are a consumer, this does not take away the mandatory consumer protections of the country where you habitually live.

d. Under Clause 18, the courts of Ireland have jurisdiction. If you are a consumer, you may also bring proceedings in the courts of the country where you are domiciled. This does not restrict any other court available to a consumer or data subject under mandatory law.

e. Section 1, Annex 1, and our records of your account and contract give the information for Annex I of those clauses. Our contact for those clauses is legal@arkiviva.com.

10. Help with requests and compliance

10.1 Data subject requests. You are responsible for responding to requests from data subjects. You must use the service's self-service tools for seeing, exporting, correcting, and deleting customer personal data, and for changing who can see it, to respond to any request those tools can handle. If we receive a request about customer personal data and can identify you from it, we will either tell the person to contact you or forward the request to you. We will not answer it for you unless the law requires us to.

10.2 This does not apply to a request you make about your own personal data. You can exercise your rights as a data subject with us, and section 15 does not apply to that request.

10.3 Other help. We will give you the help the GDPR requires, taking into account the nature of the processing and the information available to us:

a. with data subject requests that the self-service tools cannot handle; and

b. with your duties on security, personal data breaches, data protection impact assessments, and prior consultation (Articles 32 to 36 of the GDPR).

10.4 If you need information we hold to meet your duties under Articles 32 to 36 of the GDPR, and it is not available to you through Annex 2, section 11, or section 12, we will give it to you on request. Section 15 applies to charges.

11. Personal data breaches

11.1 We will notify you without undue delay after we become aware of a personal data breach affecting customer personal data. Our contact point for breaches is legal@arkiviva.com.

11.2 Our notice will describe the following, as far as we have the information:

a. what kind of breach it is, including the categories and approximate number of data subjects and records concerned;

b. its likely consequences; and

c. the measures we have taken or propose to take.

11.3 We may give this information in stages as we learn it.

11.4 This section does not cover:

a. unsuccessful attempts or activities that do not compromise the security of customer personal data, such as failed sign-ins, pings, and port scans; or

b. incidents that happen only in systems you control, such as your devices, integrations, and self-hosted runners. You are responsible for detecting and dealing with those incidents.

11.5 If we become aware that your credentials, or your authorised users' credentials, were misused to access customer personal data in the service, we will notify you under this section. Section 15 applies to any further help.

11.6 You decide whether to notify supervisory authorities and data subjects, and you make those notifications. Neither our notice nor our help is an admission of fault or liability.

12. Information and audits

12.1 Information. We will make available the information needed to show that we comply with Article 28 of the GDPR. That information is:

a. this DPA and its annexes;

b. our subprocessor list;

c. certificates and reports that our subprocessors make available and that we are allowed to share; and

d. any other information needed to show that we comply with Article 28 of the GDPR.

12.2 Audits and inspections. You may audit our compliance with this DPA, including by inspection, if a supervisory authority requires an audit. You may also audit if you first ask us in writing for the information you consider missing under section 12.1(d), and you still reasonably consider that the information under section 12.1 is not enough to show our compliance after we provide it or after a reasonable time for us to do so. Unless a supervisory authority requires more, that audit covers only what remains unresolved. You may do this yourself or through an independent auditor you choose. These conditions apply:

a. you must give us at least 60 days' written notice to legal@arkiviva.com, with the proposed scope;

b. we will agree the scope, timing, and method with you in advance, acting reasonably;

c. the audit takes place during business hours in Ireland. It is done remotely unless you reasonably decide that a site visit is necessary, and it must not unreasonably disrupt the service;

d. the audit covers only the systems that process your customer personal data, and our records about that processing. It does not give access to:

i. other customers' data;

ii. our internal accounting or financial information;

iii. our trade secrets;

iv. information whose disclosure we reasonably consider could compromise the security of our systems or premises, or breach our data protection, security, or confidentiality duties to you or others; or

v. information you or your auditor seek for any purpose other than meeting your obligations under data protection law in good faith;

e. you and your auditor must first accept reasonable confidentiality and security conditions that do not prevent the audit. We may object in writing to an auditor who, in our reasonable opinion, is not suitably qualified or independent, is our competitor, or is otherwise clearly unsuitable. You must then choose another auditor or carry out the audit yourself. You are responsible for your auditor's compliance with those conditions and for what it does during the audit;

f. you may audit once in any 12 months. You may also audit after a personal data breach affecting your customer personal data, where there are signs that we are not complying with this DPA, or where a supervisory authority requires it; and

g. you must give us a free copy of the audit report.

12.3 If an inspection of a subprocessor's facilities is needed, we will use our audit rights under our contract with that subprocessor for you, or arrange for you or your auditor to inspect under its audit terms.

12.4 Costs. You pay your own audit costs. You also pay our reasonable costs under section 15, whatever the audit finds.

13. Requests from authorities

13.1 We disclose customer personal data to an authority or other third party only on your instructions, where section 4 allows it, or for the purposes in section 5.1(b) and (c).

14. Return and deletion

14.1 Return. You choose whether we return or delete customer personal data when the affected service ends. You get it back yourself using the service's download, Git, and API facilities. If those facilities do not cover some customer personal data, such as secrets and credentials you supplied, we will make it available to you on request by a secure method we choose. Send the request to legal@arkiviva.com before the affected service ends. Ending your access does not cancel a request you have already made.

14.2 If we close your account or Organization without giving you a reasonable chance to get your customer personal data, you may ask us for it within 30 days after closure. We will then make it available to you in a commonly used format that we choose.

14.3 We do not return data that EU or Member State law forbids us to return. After return, we delete the remaining copies under the deletion rules below.

14.4 Deletion. If you delete an item using the service's delete functions, such as a repository, branch, issue, comment, or package, or close your account or Organization, that is your instruction to delete the customer personal data in it. If the affected service ends in any other way, including when we close your account or Organization under section 13 of the Terms, its end is your instruction to delete. To delete copies of commits that pull requests, tags, or other references still hold, you must delete the repository.

a. We will delete the customer personal data from our active systems within 90 days after the deletion, closure, or end. If you have a period to get your data after that, under this section or section 15 of the Terms, the 90 days start when that period ends.

b. Copies in our backups, and copies restored from them for testing, are deleted within 13 months after deletion from our active systems.

c. Until then, we keep backups secure and use them only to restore and test the service, or where section 4 or section 5.1(c) allows it. We do not have to restore from our backups items that you or your authorised users deleted or changed, unless the deletion or change happened because we breached the Terms, this DPA, or data protection law.

d. If we restore a backup to the live service, we will take reasonable steps to delete again any customer personal data you had already deleted.

14.5 Exceptions. We may keep customer personal data that EU or Member State law requires us to keep. Deletion under this section does not cover copies of public content that others have made, such as forks and clones in other accounts.

15. Charges

15.1 For help under this DPA other than through the service's self-service tools, we may charge a reasonable fee in proportion to the work, plus reasonable out-of-pocket costs. Before chargeable work starts, we will tell you the fee, or how we will work it out. We do not delay or withhold help, information, or audit cooperation that this DPA or data protection law requires until you accept or pay a fee; any dispute about the fee is dealt with separately. Other work starts only once you accept its fee. Chargeable help includes:

a. manual help with data subject requests;

b. help with impact assessments, prior consultations, and questions from authorities;

c. providing additional information under section 12;

d. audits and inspections; and

e. carrying out instructions that go beyond the standard service.

15.2 We do not charge:

a. if you are a consumer, where you need the help because we breached this DPA or data protection law, except for audits and inspections;

b. for notifying you of a personal data breach; or

c. where the law does not allow a charge, including for switching under section 15 of the Terms.

16. Liability, law and precedence

16.1 Section 16 of the Terms governs all liability arising from or relating to this DPA, including our responsibility for subprocessors. The rest of the Terms also applies to this DPA, except where this DPA says otherwise.

16.2 If this DPA and the Terms conflict about customer personal data, this DPA prevails. It does not, however, override sections 16, 17, or 19 of the Terms, or reduce any right you have as a consumer under the Terms or the law.

16.3 Where the standard contractual clauses in section 9 apply, they prevail over this DPA and the Terms. Section 16 of the Terms limits or excludes liability under those clauses only as far as those clauses allow.

16.4 Business customers. Before you end your contract for a breach of this DPA, or bring a claim for one, you must give us written notice of the breach. Where the breach can be put right, you must then give us 30 days to do so. This period runs at the same time as the 30-day period before court proceedings in section 17 of the Terms, and the exceptions in that section also apply.

17. Changes to this DPA

17.1 We may change this DPA:

a. to comply with the law, or with guidance or decisions of a supervisory authority or court; or

b. in any other way that does not materially reduce the protection of customer personal data.

17.2 We will email you about these changes before they apply. If you do not want a change, you may end the affected service by notice to legal@arkiviva.com within 14 days after our email. A paid service ends at the end of the current paid period, or on an earlier date your notice gives. A free service ends when we receive your notice. We will not charge you any early-termination amount or other charge for ending it; this overrides sections 11 and 15.3 of the Terms. Except where the law requires a refund, we do not refund any part of the current paid period. Apart from your rights as a consumer, ending the affected service is your only remedy. If you do not give that notice within those 14 days, you accept the change. Any other change applies to you only if you accept it. If you do not accept it, the current version continues to apply to you, but we may end the affected service where section 13 of the Terms allows.

17.3 If you are a consumer, we change this DPA only for a reason listed in section 14 of the Terms. Instead of the notice in section 17.2, we give you the reasonable advance notice that section 14 of the Terms requires, and you have the rights that section gives you.

17.4 If you are a business customer, section 14 of the Terms does not apply to this DPA. If a change to a section of the Terms that this DPA refers to affects how we process customer personal data, we will also email you before it applies, and you may end the affected service as section 8.3 describes.

Annex 1: Processing details

Subject matter: hosting and operating the Arkiviva service (managed Forgejo Git hosting) for your accounts and Organizations.

Categories of data subjects:

a. account holders and their authorised users, including people who operate machine accounts;

b. Organization owners, administrators, members, outside collaborators, and invitees;

c. Sponsors;

d. contributors, including commit authors and committers whose names and email addresses appear in Git history, including history that others pushed;

e. reviewers, commenters, and people who react to issues and pull requests;

f. people named in, or discussed in, your content, such as issues, comments, wiki pages, code, attachments, packages, and logs;

g. people whose personal data appears in Actions workflows, logs, variables, or secrets, and people who operate your self-hosted runners;

h. people who receive invitations and other email sent on your behalf; and

i. visitors to your Pages sites.

Categories of personal data:

a. profile and identity data:

i. usernames, display names, email addresses, avatars, and profile fields;

ii. account and Organization IDs;

iii. public SSH and GPG keys, and deploy keys;

b. Git content and history, including author and committer names, email addresses, timestamps, and signatures;

c. collaboration content:

i. issues, pull requests, reviews, comments, reactions, labels, and milestones;

ii. project boards and time tracking;

iii. wikis, releases, and attachments;

iv. packages and their metadata, and Git LFS objects;

d. Organization data: memberships, teams, roles, permissions, and invitations;

e. Actions data:

i. workflow files, and run, job, and attempt history;

ii. logs;

iii. variables and secrets you supply;

iv. runner registrations and labels;

f. webhook and mirror settings and stored credentials, webhook delivery records (requests and responses), and commit statuses and checks;

g. integration setup: registered OAuth applications and customer-supplied Git hooks;

h. lifecycle records: name redirects and records of deleted items;

i. activity data: notifications, stars, watches, follows, blocked-user records, activity feeds, and contribution records;

j. requests from visitors to your Pages sites, including their IP addresses, while we serve them; and

k. any other personal data in content stored in your accounts, Organizations, and repositories.

Not customer personal data: we process the following as an independent controller under section 5:

a. authentication and account-security records, such as password hashes, two-factor records, session data, OAuth authorisations, linked external accounts, and access-token names and scopes;

b. billing, payment, allowance, entitlement, and Sponsor records;

c. service logs and telemetry, such as IP addresses, user agents, and request data, other than the requests we serve for your Pages sites, and records of email we send, such as the recipient, the subject, and the delivery status; and

d. abuse, security, and legal case records.

Sensitive data: special categories of personal data, criminal-offence data, and children's data, only where you, your authorised users, or other people who contribute to your content put them there (sections 3.2 and 3.3). Safeguards: the measures in Annex 2 and the access and visibility controls you set.

Nature of the processing:

a. storing, hosting, backing up, and restoring;

b. transmitting, indexing, and searching;

c. displaying and serving content, including Pages sites, and validating custom domains and obtaining and renewing their certificates (section 6.2 of the Terms);

d. sending email;

e. running Actions jobs on runners you register, or on Arkiviva-hosted runners when you use them: authenticating runners, queuing, starting, stopping, cancelling, and retrying jobs, sending code, instructions, and secrets to the runners, and receiving status, logs, and diagnostics from them (sections 6.6 and 6.7 of the Terms);

f. importing repositories and pulling mirrors from sources you choose, using credentials you supply;

g. sending data to destinations you configure, such as webhooks, mirrors, and integrations;

h. exporting and deleting; and

i. maintaining, updating, testing, and troubleshooting the service.

Purpose: providing the service, and the features you enable and use, on your instructions (section 4).

Duration: for the term of your contract, and after it ends until deletion under section 14 is complete.

Frequency: continuous.

Processing by subprocessors: the functions and locations on our subprocessor list (section 8.1), for no longer than the duration above.

Annex 2: Technical and organisational measures

These are the measures we take to protect customer personal data in the production service and in the recovery and test environments described in section 4.3. We review them regularly and may change them under section 7.2.

1. Hosting and physical security

a. The service runs on servers and storage of our hosting provider (Annex 3), in data centres in the EEA. The provider is responsible for the physical security of its data centres under its data processing terms with us.

2. Access control

a. Administrative access to the production service and to the recovery and test environments is limited to Arkiviva's staff, contractors, and others acting on Arkiviva's behalf who need it for their work, under section 7.1, and to the automated tools and AI agents they operate. We take reasonable steps to prevent AI agents from accessing customer personal data, except in public content.

b. Administrative access requires strong authentication, limits repeated sign-in attempts, and is available only through restricted network access. Site administrators, and our account with our hosting provider, use multi-factor authentication.

c. Within the service, access to repositories and Organizations follows the permissions that customers set. New repositories and Organizations created in the web interface are private unless you choose otherwise, and email addresses are hidden by default.

3. System and network security

a. Our servers make only the services the platform needs reachable from the internet, and firewalls deny other inbound traffic by default.

b. The service's components run with only the privileges they need, and our systems receive security updates.

c. The service does not send customer data to external avatar, CAPTCHA, or content-delivery services.

4. Encryption

a. Data travelling over public networks is encrypted: web traffic uses TLS 1.2 or later, Git over SSH uses strong algorithms, and email to our email provider is sent over verified encrypted connections.

b. Our own backups are encrypted and authenticated before they leave our servers.

5. Availability, backup, and recovery

a. We back up the service's data every night to storage separate from our servers, which is protected against deletion. A separate recovery key for these backups is kept away from the servers.

b. We regularly test that our backups can be restored, and we check their integrity.

c. Our hosting provider also keeps snapshots of our servers for us, protected by its own security measures.

d. Before each update, we keep a recovery copy. If the service fails, we restore it from our backups.

6. Monitoring and logging

a. A monitoring service at a separate provider checks the health of the service, its backups, and its maintenance, and alerts us. It receives no customer personal data.

b. We keep system logs for operations and security, for limited periods.

7. Incident response

a. We follow a documented incident response procedure, which covers containment, preserving evidence, communication, and review, and includes notifying customers of personal data breaches under section 11.

8. Personnel and subprocessors

a. Everyone with access to customer personal data is bound by confidentiality (section 7.1).

b. Each subprocessor in Annex 3 is bound by data processing terms that meet Article 28(4) of the GDPR.

9. Recovery and test environments

a. The recovery and test environments are isolated from the production service and from the public. They serve nothing to the public and send no email, and they connect out only to fetch backups and for basic system functions, such as name lookups, time synchronisation, and software updates.

b. Administrators reach them only through restricted network access.

c. Their backups and snapshots are deleted under section 14.4(b).

Annex 3: Subprocessors on 16 November 2026

Our current subprocessor list is at https://legal.arkiviva.com/subprocessors/.

Subprocessor Address and contact Function Location Transfer safeguard
Hetzner Online GmbH Industriestr. 25, 91710 Gunzenhausen, Germany; data-protection@hetzner.com Servers and backup storage Germany and Finland None needed (EEA)
Scaleway SAS 8 rue de la Ville-l'Évêque, 75008 Paris, France; privacy@scaleway.com Sending email on your behalf, such as invitations and notifications France None needed (EEA)
Soverin B.V. Bijlmerplein 888A, 1102 MG Amsterdam, Netherlands; support@soverin.net Email for support, privacy, legal, and security correspondence that may contain customer personal data Netherlands None needed (EEA)