1. Who this agreement is between, and when it applies
1.1 This agreement is between:
- You: the organisation that has created a GapProof account and accepted our Terms and Conditions (the "Agreement").
- Us: Elastic Bean Software Limited, registered in Ireland (company number 814004), registered office Ballinastoe, Roundwood, Co. Wicklow, A98 YV67, Ireland ("GapProof", "we").
1.2 You use GapProof to prepare, calculate, publish and keep your gender pay gap report. To do that, we handle personal data about your employees on your behalf. This agreement sets the terms for that, as Article 28 of the GDPR requires.
1.3 This agreement is Schedule 1 of the Agreement and forms part of it. You accept it when you create your account, and it applies from the moment you first upload any personal data, including while you prepare your report before paying.
1.4 You do not need to sign it for it to apply. If you would like a copy signed by us, email support@gapproof.ie.
2. Words we use
- GDPR: Regulation (EU) 2016/679. Data protection law: the GDPR, the Irish Data Protection Acts 1988 to 2018, and any other law on personal data that applies to the processing.
- Controller, processor, data subject, personal data, processing and supervisory authority have the meanings given in the GDPR.
- Employee Data: personal data that you, your Users or your adviser upload to or create in GapProof, as described in Annex 1.
- Sub-processor: another company we use that processes Employee Data.
- Employer: a reporting entity set up inside your account. Most accounts have one; a group or an adviser may have several.
- The Guide: the AI assistant built into GapProof.
- Users: the people you allow to use GapProof under your account.
3. Who is responsible for what
3.1 You are the controller and we are the processor of Employee Data. You decide why it is processed: to meet your duties under the Gender Pay Gap Information Act 2021 and the regulations made under it.
3.2 Where we are the controller. For the names, work email addresses and sign-in records of your Users, and for billing details, we decide how they are used, and only to run your account, bill you and give support. Our Privacy Policy explains this; this agreement does not cover it.
3.3 Advisers. Where an accountancy, payroll or HR firm (an "adviser") uses GapProof to prepare reports for employers it serves:
- each employer is the controller, the adviser is its processor, and we are the adviser's sub-processor;
- the adviser is "you" under this agreement, and confirms it has a written contract with each employer that meets Article 28 of the GDPR and allows it to use GapProof;
- we keep each employer's data separate from every other employer's, including other clients of the same adviser.
3.4 What you confirm. You have a lawful basis to process Employee Data and to give it to us, and you have told your employees about the processing as data protection law requires. Your instructions to us will comply with data protection law.
4. What we commit to
4.1 Only on your instructions. We process Employee Data only on your documented instructions, including for any transfer outside the EU. The Agreement, this agreement and what your Users do in GapProof (uploading, fixing, calculating, publishing, deleting) are your complete instructions. If EU or Irish law requires other processing, we will tell you first, unless that law forbids it.
4.2 Unlawful instructions. We will tell you promptly if we think an instruction breaks data protection law.
4.3 No other use. We will not sell Employee Data or use it for our own purposes. We will never use it to train or improve AI models, to benchmark or to market anything, and we will never combine one customer's data with another's.
4.4 Confidentiality. Only our staff and contractors who need access to provide GapProof may access Employee Data, and all of them are bound by confidentiality. Support access is granted by you, for one Employer at a time. It is time-limited and read-only, it is shown to you, you can end it at any time, and it is recorded under the name of the member of staff who opened it.
4.5 Security. We take the technical and organisational measures Article 32 of the GDPR requires, including at least those in Annex 2. We may improve them over time but will not reduce the overall level of protection.
5. Sub-processors
5.1 General approval. You give general written approval for us to use the sub-processors listed in Annex 3.
5.2 The same protection passed on. We have a written contract with each sub-processor that gives Employee Data at least the protection of this agreement, and we remain fully responsible to you for each sub-processor's work.
5.3 Changes. Annex 3 is always the current list. At least 30 days before adding or replacing a sub-processor that handles Employee Data, we will email your account's owners.
5.4 Objecting. You may object on reasonable data protection grounds within those 30 days. We will then try to find a reasonable alternative. If we cannot, you may end the affected part of the service and receive a pro-rata refund of fees paid in advance for the unused period.
6. Where the data is kept
6.1 We store and process Employee Data only in the European Economic Area, in Microsoft Azure data centres in the European Union. The Guide uses an Azure OpenAI deployment in the EU.
6.2 We will not move Employee Data outside the European Economic Area unless we have told you under clause 5.3 and the move is covered by a valid safeguard under Chapter V of the GDPR, such as an EU adequacy decision or the EU Standard Contractual Clauses (Commission Decision 2021/914).
6.3 A sub-processor may occasionally need remote access from outside the European Economic Area, for example to give technical support. Where this happens, it is covered by that sub-processor's own Chapter V safeguards, listed in Annex 3.
7. Helping you
7.1 Employees' requests. We will help you answer employees who use their GDPR rights, such as asking for a copy of their data or asking for it to be corrected or deleted. Where you need one person's records found, exported, corrected or deleted, ask us and we will do it with you. If an employee contacts us directly, we will pass the request to you within 5 working days and will not answer it ourselves unless you ask us to.
7.2 A frozen snapshot is never changed. A correction is made by preparing a new version of the report, and the frozen copy is kept for the period in clause 10, because the law asks for each published report to stay public.
7.3 Assessments and the regulator. We will give reasonable help with your data protection impact assessments and any consultation with the Data Protection Commission, using the information we have.
7.4 Security incidents. If we become aware of a security incident affecting Employee Data within the meaning of Article 4(12) of the GDPR, we will:
- tell you without undue delay, and in any case within 48 hours, so you can meet your own 72-hour deadline to tell the Data Protection Commission;
- say what happened, which data and roughly how many people are affected, the likely consequences, what we have done and will do next, and who to contact;
- give further details as soon as we know them, in stages if needed;
- take reasonable steps to contain the incident and limit the harm.
7.5 Telling you about an incident does not mean we accept fault or liability for it.
7.6 Help under this clause is free of charge, unless a request is clearly excessive. If it is, we will agree any cost with you first.
8. The AI assistant
8.1 The Guide helps you match columns, spot problems in your data, explain figures and draft text. It processes Employee Data only to do the task you are working on at the time.
8.2 Limits on the Guide:
- It suggests only. A person in your organisation must accept a suggestion before it changes any data, and the acceptance is recorded under their name.
- It never calculates the statutory figures. A fixed, versioned calculation engine produces them.
- It makes no decisions about individual employees, and you must not use it to do so.
- It receives only the data of the Employer being worked on, and keeps no memory shared between customers.
8.3 The AI provider. The Guide runs on Microsoft's Azure OpenAI service in the EU (Annex 3). Under Microsoft's terms, prompts and outputs are not used to train models and are not shared with OpenAI.
8.4 Conversations. Each person's conversation with the Guide is kept inside your account. A question and its answer are deleted after 7 days unless pinned, and anyone can remove their own messages at any time. Suggestions that changed your data stay with your report's evidence (clause 10).
9. Audits and information
9.1 We will give you the information needed to show that we meet this agreement. On request, we will provide our security summary, our answers to a standard security questionnaire and a summary of our most recent independent penetration test.
9.2 If that is not enough, or a supervisory authority requires it, you (or an independent auditor bound by confidentiality) may audit us, on these terms:
- at least 30 days' written notice, unless the audit follows a security incident affecting Employee Data or a regulator requires it;
- no more than once a year, unless there has been such an incident;
- during business hours, without disrupting the service, and without access to other customers' data;
- at your cost, unless the audit finds that we have materially broken this agreement.
10. How long data is kept, and deletion
10.1 We keep Employee Data for these periods:
| Data | How long |
|---|---|
| Uploaded files and data never frozen into a report | 90 days after the upload, then deleted. While it is still the file your report is being prepared from, 90 days after that year's publish-by date instead, if that is later |
| Frozen snapshots, figures, the evidence trail and the Preparation Record | Four years from the publish-by date (the three years the law asks your report to stay public, plus one), then deleted, with a record of the deletion. Closing your account does not shorten this |
| Published report pages and their PDFs | At least three years from publication, even if your subscription ends, as section 10 of the Terms explains. They show group figures and your statement, never an individual employee's records |
| Conversations with the Guide | Each question and its answer: 7 days, unless pinned (clause 8.4) |
10.2 When your account closes. Closing ends every sign-in at once, so download your reports, PDF packs and Preparation Records first. We keep a closed account for 30 days and can reopen it in that time if you ask. After that we delete the Employee Data that was never frozen, unless EU or Irish law requires us to keep it. Frozen data, the evidence trail and published pages are kept for the periods in clause 10.1, then deleted.
10.3 Backups. Deleted data leaves our backups within a further 35 days. Until then, backups stay protected by this agreement and are never restored for any other purpose.
10.4 On request, we will confirm a deletion in writing.
10.5 Taking a public page down. You may ask us to take a published page down, as section 10 of the Terms explains. If you do, keeping your report public elsewhere becomes your responsibility.
11. General terms
11.1 Liability. Each party's liability under this agreement follows the limits in section 18 of the Terms, unless data protection law does not allow those limits.
11.2 Which document wins. If this agreement and the rest of the Agreement disagree about protecting personal data, this agreement applies.
11.3 Changes. We may change this agreement only to comply with the law or to add protection. We will email your account's owners at least 30 days before a change takes effect. If a change reduces your protection, you may refuse it and end the Agreement, with a pro-rata refund of fees paid in advance. A change is never made just by updating this page.
11.4 How long it lasts. This agreement lasts as long as we hold any Employee Data, including after the Agreement ends.
11.5 Law and courts. The laws of Ireland govern this agreement, and the Irish courts have exclusive jurisdiction.
11.6 Contact. Data protection questions: support@gapproof.ie.
Annex 1 — Description of the processing
| Purpose | To prepare, check, calculate, publish and keep your gender pay gap report under the Gender Pay Gap Information Act 2021 and its regulations, and to keep the evidence of how each figure was produced |
|---|---|
| What is done with the data | Storing uploaded files; matching columns; finding and fixing problems in the data; calculating the statutory figures; producing reports, PDFs and a public report page; keeping an evidence trail; AI-assisted suggestions and explanations (clause 8) |
| Whose data | Your current and former employees in the reporting period. Also colleagues your Users invite to answer a question about the data (their email address only) |
| Types of data | Payroll or employee number; name (if uploaded); gender; the year's pay (basic pay or an hourly rate, allowances, overtime, shift premium and piece-work pay), bonus and benefits in kind (such as a company car); hours worked and contracted hours; permanent or temporary contract; start and leaving dates; department, where uploaded. Columns GapProof does not use are ignored, and go when the upload is deleted |
| Special category data | None is needed, and you must not upload any, such as health details, ethnicity or trade union membership. Gender as recorded on payroll is not special category data under the GDPR |
| How often | Continuously while your account is open, with most activity around each year's snapshot date and publish-by date |
| How long | As set out in clause 10 |
| Where | The European Economic Area only (clause 6) |
Annex 2 — Security measures
| Area | Measure |
|---|---|
| Separating customers | The database itself keeps each customer's and each Employer's data apart (PostgreSQL row-level security, which the application cannot get around). The application adds a second filter on every query. If a customer cannot be identified, no data is returned. Automated tests on every software change try to read and write across customers and must be refused |
| Who the user is | The customer and Employer are taken only from the signed sign-in token, never from anything the browser sends. A request for another customer's data gets "not found" |
| Encryption | TLS 1.2 or higher in transit. AES-256 at rest for the database, file storage and backups |
| Keys and secrets | Held in Azure Key Vault and reached through managed identities. Never stored in code |
| Files | Each customer has its own private storage container. Uploads go straight to it through a short-lived link made for that one upload, and are scanned for malware before they are read |
| Sign-in | Single sign-on with Microsoft on plans that include it. Roles limit what each User can do, and freezing, publishing and billing are for owners only. Resetting a password ends every earlier session |
| Staff access | Least privilege for all our staff. Support access to your data needs your grant, for one Employer at a time and for a limited time. It is opened only by a named member of staff signed in to our own staff system with multi-factor authentication, is read-only, and is recorded under their name |
| Showing less data | No screen or API lists a whole workforce. Individual people appear only on request, a page at a time, within a single finding |
| Evidence and integrity | Every change to report data is recorded in an append-only, tamper-evident record, each entry linked by a hash to the one before. Frozen snapshots and published reports cannot be edited; corrections create a new version |
| Logs and monitoring | Logs and monitoring never contain employee-level data. Security events are monitored and alerted on |
| Backups | Automatic, encrypted database backups with point-in-time restore for 35 days, kept in the EU. A restore is tested at least once a year |
| Testing | Automated security and separation tests on every software change. An independent penetration test at least once a year, with separation between customers as an explicit target |
| Development | Code review before release. Dependencies kept on supported versions and patched. Production changes go through a controlled pipeline with approvals |
| AI | Each request to the Guide carries only the current Employer's data. No training on customer data. Data stays in the EU |
| Incidents | A written incident response plan, including the 48-hour notice in clause 7.4 |
| People | Confidentiality agreements and data protection training for everyone with access |
Annex 3 — Sub-processors
These are all the companies we use to run GapProof. The first three handle Employee Data and are the sub-processors you approve under clause 5. The other three never receive Employee Data: they handle only your Users' details and your billing details, which we are responsible for ourselves (clause 3.2). We list them here so you can see everyone involved in one place.
| Sub-processor | What it does | Employee Data it handles | Where | Transfer safeguard |
|---|---|---|---|---|
| Microsoft Ireland Operations Limited (Microsoft Azure) | Hosting, database, file storage, key management, backups | All Employee Data | EU | EU Data Boundary; Microsoft's data protection addendum with the EU Standard Contractual Clauses for any support access from outside the European Economic Area |
| Microsoft Ireland Operations Limited (Azure OpenAI) | Runs the AI model behind the Guide | Only the data needed for the task in hand | EU | As above; no training on inputs |
| Microsoft Ireland Operations Limited (Azure Communication Services) | Email provider: sends sign-in codes, account and reminder emails | Your Users' and invited colleagues' email addresses only; never pay data | EU | As above |
| Microsoft Ireland Operations Limited (Microsoft Entra) | Signs your Users in (Microsoft Entra External ID), and single sign-on with Microsoft where your plan includes it | None. Your Users' names, email addresses and sign-in records only | EU | As above |
| Microsoft Ireland Operations Limited (Azure Monitor and Application Insights) | Monitoring: the service's health, performance and security events | None. Logs carry account identifiers and technical details such as IP addresses, never employee-level data | EU | As above |
| Stripe Payments Europe, Ltd | Payment provider: takes card payments and runs subscriptions | None. The payer's email, the employer's name, the billing address and any tax number | EU | Stripe may transfer these details to the United States under the EU–US Data Privacy Framework and the EU Standard Contractual Clauses |
Stripe also acts as a separate controller of card details for its own legal duties, such as preventing fraud; our Privacy Policy explains what it holds.