Gabsor Data Processing Agreement
Version 1.7, effective 5 November 2026.
1. Parties and how this agreement fits
1.1 This Data Processing Agreement ("DPA") is part of the Gabsor Terms of Service (the "Terms"). It applies whenever we process personal data on your behalf. You accept it together with the Terms; no separate signature is needed, and we provide a countersigned copy on request.
1.2 The parties are you (the customer), the Representative Entity that holds your appointment (GAB COMPLIANCE LTD, Dublin for EU appointments; GAB COMPLIANCE LTD, London for the UK appointment), and Gabsor, LLC ("Gabsor"). As in section 1.2 of the Terms, each company is bound only for its own processing and is not liable for another's.
1.3 Words defined in the Terms mean the same here. "GDPR" means Regulation (EU) 2016/679 and, for the UK appointment, the UK GDPR, each with the national law that supplements it and as amended or replaced. "Personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meanings the GDPR gives them. "Your data" means the personal data described in Annex 1.
1.4 On the processing of your data, this DPA prevails over the Terms and over a role agreement. Where the transfer clauses in section 7 apply and differ from this DPA, the transfer clauses prevail.
2. Roles and scope
2.1 You are the controller of your data. If you process it for someone else, you are their processor and we are your sub-processors; you confirm that your controller allows this.
2.2 Two companies process your data, each as your processor for its own part:
| Processing | Processor | What it involves |
|---|---|---|
| Requests and documents addressed to your representative | The Representative Entity that holds the appointment | Receiving post and email, scanning, recording each item in the platform, forwarding it to you, and telling the sender it has been received and forwarded |
| The platform | Gabsor, LLC | Hosting and storing requests, your record of processing, incident reports, authority cases and documents, and running the functions you use on them |
2.3 Three things are outside this DPA:
- Your account. Gabsor is the controller of the data it needs to run your account, bill you and support you. The Privacy Policy covers it.
- The representative's own legal duties. Where a Regulation requires the Representative Entity itself to act, for example to give a supervisory authority information it asks for or to make your record of processing available, it acts under that law and not on your instructions. It tells you when it does, unless the law forbids it.
- What the representative keeps after the appointment ends. Section 11.3.
2.4 Annex 1 describes the processing in detail.
3. Instructions
3.1 We process your data only on your documented instructions. Your instructions are the Terms, this DPA, the role agreement, the settings you choose in the platform, and anything further you tell us in writing that fits within the services.
3.2 If we think an instruction breaks data protection law, we tell you at once and may pause that processing until you confirm or change it.
3.3 If the law of the EU, a member state or the UK requires us to process your data in another way, we tell you before we do so, unless that law forbids it.
3.4 You are responsible for having a legal basis for the processing, for the accuracy of what you put in the platform, and for telling data subjects what the GDPR requires, including who your representative is.
4. People and confidentiality
4.1 Only people who need your data to provide the services may access it. Each of them is bound by a duty of confidentiality, by contract or by law, that continues after they stop working for us.
4.2 We tell those people what they may and may not do with your data, and we remove their access when they no longer need it.
5. Security
5.1 We protect your data with the technical and organisational measures in Annex 2, which are chosen to match the risk as Article 32 GDPR requires. We may change the measures as technology and threats change, but we will not lower the overall level of protection.
5.2 Your part: keep your credentials secret, give access only to team members who need it, and do not put more personal data into the platform than a request or record requires.
6. Sub-processors
6.1 You give us general authorisation to use sub-processors. The current list is published at gabsor.com/subprocessors and forms part of this DPA (Annex 3). The three Gabsor companies may act as sub-processors for each other.
6.2 We bind every sub-processor by contract to data protection obligations equivalent to those in this DPA, and each of us remains responsible to you for the sub-processors it uses.
6.3 We tell you by email or in the platform at least 30 days before we add or replace a sub-processor. You may object within those 30 days on reasonable data protection grounds. If we cannot resolve the objection, you may end the affected service before the change takes effect. Fees already paid are not refunded.
6.4 If a sub-processor has to be replaced at once to keep the services running or secure, we may do so and tell you as soon as we can. Your right to object under 6.3 then runs from that notice.
7. International transfers
7.1 Principle. We send your data outside the European Economic Area or the United Kingdom only as this section describes, and only with one of the safeguards that Chapter V of the GDPR allows.
7.2 Forwarding to you. The Representative Entity is in Ireland or the United Kingdom, and you are outside both. When it forwards a request to you, it sends personal data from a processor to its controller in a third country.
- If you are in a country, or covered by a framework, that the European Commission has found adequate, forwarding from the Dublin entity relies on that decision.
- Otherwise forwarding from the Dublin entity is covered by the EU standard contractual clauses, Module Four (processor to controller), incorporated into this DPA with the selections in Annex 4. Accepting the Terms counts as signing them.
- Forwarding from the London entity needs no transfer safeguard. Under the guidance of the Information Commission (the ICO), a UK processor that sends personal data to its own controller is not making a restricted transfer. If that position changes, the UK addendum in Annex 4 applies from that date.
7.3 Between the Gabsor companies. Request content is accessible only to staff of the two Representative Entities, working from Ireland, Germany, Spain or the United Kingdom. Staff of one Representative Entity may handle requests addressed to the other; that company then acts as a sub-processor of the one that holds your appointment (Annex 3). Personal data that moves between the European Union and the United Kingdom this way is covered by the European Commission's adequacy decision for the United Kingdom and by the United Kingdom's adequacy regulations for the European Economic Area. If either stops applying, the two companies sign standard contractual clauses before the sharing continues. Where staff of the Dublin entity handle a request addressed to the London entity, the safeguards that section 7.2 sets for the Dublin entity apply to forwarding that request as well.
Gabsor, LLC provides the software and holds the hosting accounts; its staff do not access request content. To the extent that role still counts as a transfer to the United States, it is covered by the EU standard contractual clauses, Module Three (processor to processor), and the UK addendum, signed between the Gabsor companies. We give you a copy of those clauses on request.
7.4 Sub-processors. A sub-processor outside the EEA or the UK receives your data only under an adequacy decision or the standard contractual clauses and UK addendum. The list in Annex 3 states each sub-processor's location and safeguard.
7.5 Requests from public authorities outside the EEA and UK. If such an authority demands access to your data, the company that receives the demand tells you before answering unless the law forbids it, challenges a demand it considers unlawful, and discloses no more than the law requires.
7.6 If the rules change. If a safeguard we rely on is withdrawn or replaced, we move to a valid one and tell you under section 13.2.
8. Requests from data subjects and help with your obligations
8.1 Requests that reach your representative. Receiving and forwarding them is the service. The Representative Entity records each request and forwards it to you within the times in section 14.2 of the Terms. It tells the sender that the request has been received and forwarded. It does not decide on a request or answer it in substance unless you instruct it to in writing.
8.2 Requests that reach Gabsor. If a data subject writes to Gabsor about your data, for example through support, Gabsor forwards the message to you and does not answer it.
8.3 Tools. The platform lets you track each request against its deadline, record your reply and export the file.
8.4 Other help. Taking into account what we process and what we know, we help you meet your duties on security, breach notification, data protection impact assessments and consultation with a supervisory authority (Articles 32 to 36 GDPR). This help is not part of the subscription. We quote it first and provide it only after you approve the quote in writing. Out-of-pocket costs are charged as section 9.10 of the Terms provides. The breach information in section 9 and the documents in section 10.1 are part of the service and are not charged.
9. Personal data breaches
9.1 If one of us becomes aware of a personal data breach affecting your data, that company tells you without undue delay and in any case within 48 hours.
9.2 The notice says, as far as is known then: what happened, which kinds of data and roughly how many people and records are affected, the likely consequences, and what has been done or is planned. If not everything is known, the rest follows in stages.
9.3 The company concerned acts at once to contain the breach and limit its effects, and gives you the information you need for your own notifications. Whether to notify a supervisory authority or the people affected is your decision and your task. We do not notify on your behalf unless you ask us to in writing.
9.4 Telling you about a breach is not an admission of fault or liability.
10. Information and audits
10.1 On request we give you the information you need to show that Article 28 GDPR is met: this DPA and its annexes, answers to a reasonable security questionnaire, and summaries of any independent security reports we hold.
10.2 If that information does not answer a specific concern, you may audit the processing yourself or through an independent auditor who is bound by confidentiality and is not our competitor.
10.3 An audit is carried out remotely, by document review, interview and screen-share, no more than once in twelve months, on 30 days' written notice, during business hours and at your cost. An on-site audit, or a second audit in the same year, takes place only where a supervisory authority requires it or after a personal data breach affecting your data. An audit gives no access to other customers' data or to anything that would weaken security.
10.4 Each of us cooperates with a supervisory authority that inspects the processing.
11. Return, deletion and what the representative keeps
11.1 During the term you can export your data from the platform at any time.
11.2 At the end. For 30 days after the services end you can still export your data (section 11.7 of the Terms). Ninety days after that period we delete it from the platform (section 11.8 of the Terms). Copies in backups are overwritten on the backup schedule in Annex 2. On request we confirm the deletion in writing.
11.3 What the representative keeps. For three years after an appointment ends, the Representative Entity keeps the Letter of Appointment, your record of processing as it stood on the end date, and a log of correspondence: who wrote, when, about what, and when it was forwarded. The content of data-subject requests is deleted with the platform data, unless a dispute or an authority inquiry about that request is pending. The Representative Entity keeps these records so that it can show how it performed the mandate and answer an authority about that period. For them it is a controller in its own right, uses them for nothing else and deletes them when the three years end. Documentation for an AI Act appointment is kept for ten years because Articles 22 and 54 of the AI Act require it.
12. Liability
12.1 Each company is liable to you only for its own processing. The limits in section 16 of the Terms apply to all claims between you and that company, under the Terms and this DPA taken together. This DPA does not add a second limit.
12.2 Nothing in this DPA or the Terms limits what a data subject can claim under Article 82 GDPR or under the transfer clauses, or the powers of a supervisory authority.
12.3 Each side bears the fines imposed on it for its own breach. Section 16.4 of the Terms applies where a company incurs a loss because of your breach.
13. Term, changes and governing law
13.1 Term. This DPA applies for as long as we process your data, including after the services end and until the data is deleted under section 11.
13.2 Changes. We may update this DPA to reflect a change in the law, new or replaced transfer clauses, a change of sub-processor under section 6, or improved security. We give notice as section 17 of the Terms provides. A change will not reduce the protection of your data.
13.3 Governing law. Article 28 GDPR requires a processing contract under the law of the EU or a member state, and the UK GDPR requires UK law. So, for all three companies including Gabsor, LLC, this DPA is governed by the law of Ireland where the processing falls under the EU GDPR, with the courts of Ireland, and by the law of England and Wales where it falls under the UK GDPR, with the courts of England and Wales. The transfer clauses carry their own law and courts, set out in Annex 4.
13.4 Contact. Questions about this DPA go to contact@gabsor.com. Requests and documents for a representative go to eu_gdpr@gabsor.com or uk_gdpr@gabsor.com.
Annex 1: Description of the processing
| Requests (Representative Entity) | Platform (Gabsor, LLC) | |
|---|---|---|
| Subject matter | Requests and documents addressed to your representative under your appointments | The Gabsor platform in which you manage them |
| Duration | From the start of an appointment until 30 days after it ends, then section 11 | The term of your plan, then section 11 |
| Nature | Receiving by post and email, scanning, recording, forwarding, acknowledging receipt | Hosting, storing, displaying, exporting, deleting |
| Purpose | Acting as the contact point the Regulations require and performing the mandate | Providing the platform |
| Data subjects | People who write to your representative: your customers, users, employees and others whose data you process; people named in authority correspondence; contact persons at authorities | The same, and people named in your record of processing, incident reports and documents |
| Personal data | Name and contact details; what the person writes and attaches; identifiers they give so you can recognise them, such as account or order numbers; copies of identity documents if they send them; the history of the correspondence | The same as stored in the platform, with your replies and notes |
| Special categories of data | Not asked for. They may appear if a sender includes them, for example health data in an access request. | The same |
| Frequency | Each time a request or document arrives | Continuous |
| Retention | Section 11 | Section 11 |
Annex 2: Security measures
| Area | Measure |
|---|---|
| Staff access | An individual account for every person. Two-factor authentication on platform administration, the representative mailboxes, hosting and the code repository. Access limited to the people who need it and removed when they leave. Request content is accessible only to staff of the two Representative Entities, working from Ireland, Germany, Spain or the United Kingdom. |
| Customer accounts | Passwords stored hashed. Team permissions by role. Each customer's data is separated by organisation, and that separation is checked on every request. |
| Encryption | In transit with TLS. At rest by the hosting and storage providers. |
| Application and network | A web application firewall and bot protection in front of the platform. Security headers. |
| Development | Changes reviewed before release. Dependencies kept up to date. Secrets held in the hosting provider's secret store, never in the code, and rotated every 30 days and after any exposure. |
| Logging | Access to requests and changes to records are written to the audit trail. Errors are monitored. |
| Backups | Daily database backups, kept for 30 days and then overwritten. A restore is tested every week. |
| Post | Post is opened and scanned only by the mail service and by Representative Entity staff. Originals are destroyed the same day, after scanning. |
| Devices | Staff devices use disk encryption, a screen lock and current security updates. |
| Incidents | A written procedure for detecting, containing and reporting a breach within the time in section 9. |
| Suppliers | Sub-processors are chosen after a check of their security and data protection terms. |
| People | Confidentiality undertakings and written guidance on handling requests. |
Annex 3: Sub-processors
The list of our sub-processors, with each one's purpose, location and transfer safeguard, is published at gabsor.com/subprocessors. The list as it stands on the day you accept the Terms forms part of this DPA. Changes to it follow section 6.3, and we send you the list as a document on request.
Annex 4: Transfer clauses
Part A. EU standard contractual clauses, from the Dublin entity to you
| Item | Selection |
|---|---|
| Clauses | Annex to Commission Implementing Decision (EU) 2021/914, Module Four (processor to controller) only |
| Data exporter | GAB COMPLIANCE LTD, 136 Capel Street, Dublin 1, Ireland, as processor; eu_gdpr@gabsor.com |
| Data importer | You, as controller; name, address and contact person as entered in your account |
| Clause 7 (docking clause) | Not used |
| Clause 11(a) (optional independent dispute body) | Not used |
| Clause 17 (governing law) | Ireland |
| Clause 18 (courts) | Ireland |
| Annex I.B (description of the transfer) | Annex 1 of this DPA, column "Requests"; a transfer takes place each time a request is forwarded |
| Security | The exporter applies Annex 2 of this DPA |
Part B. UK addendum, from the London entity to you (fallback only, see section 7.2)
| Item | Selection |
|---|---|
| Addendum | International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, issued by the Information Commissioner |
| Table 1 (parties) | Exporter: GAB COMPLIANCE LTD, 71-75 Shelton Street, London WC2H 9JQ; uk_gdpr@gabsor.com. Importer: you, as entered in your account. Start date: the day you accept the Terms. |
| Table 2 (clauses) | The EU clauses as selected in Part A |
| Table 3 (appendix information) | Parties as in Table 1; description of the transfer as in Annex 1; security as in Annex 2; no sub-processor list applies |
| Table 4 (who may end the addendum) | The exporter |
Part C. Between the Gabsor companies
Each Representative Entity (exporter) and Gabsor, LLC (importer) have signed the EU clauses, Module Three (processor to processor), with general authorisation for sub-processors on 30 days' notice, Irish law and the Irish courts, and the Data Protection Commission as competent supervisory authority, together with the UK addendum for the London entity.