AccessRecord

Data Processing Addendum

A summary of the terms on which we process personal data on your behalf. It is written to sit alongside our Terms of Service and forms part of them.

Last updated 11 October 2026

If you need a signed DPA on your own paper, or one incorporating the Standard Contractual Clauses with your entity details, email support@accessrecord.app and we will execute it. It will be signed by the operator personally, so allow for time zones rather than expecting a legal department to turn it around the same hour.

1. Roles

You are the controller of the personal data contained in the records you create. We are the processor. Where you are itself a processor acting for another controller, you warrant that you have authority to give us these instructions.

Where the operator is an individual, that individual is the processor, and is bound by the same confidentiality obligations as any employee would be.

2. Scope and purpose

We process personal data only to provide, secure and support the service, and only on your documented instructions — which include your configuration of the service and your use of it. We do not process it for our own purposes, we do not sell it, and we do not use it to train models.

The personal data typically consists of the names and job titles of the people who sign your conformance records, plus the account details of your users.

3. Your instructions

We will tell you if, in our opinion, an instruction infringes data protection law. We will not act on such an instruction without your written confirmation.

4. Confidentiality

Anyone we authorise to process the data is under a duty of confidentiality, whether contractual or statutory, that survives the end of their engagement. In practice this is a short list: the operator, and no one else.

5. Security measures

The technical and organisational measures we maintain include:

We are honest that a one-person operation has a resilience weakness a larger provider does not: there is no second engineer. The mitigation is that the software is dependency-free, self-hostable and exports your data in full at any time, so you are never locked in to our ability to keep running.

6. Subprocessors

We engage the subprocessors listed at /legal/subprocessors. We will give you notice before adding or replacing one, and you may object on reasonable data protection grounds. Each subprocessor is bound by terms no less protective than these.

7. International transfers

Where processing involves a transfer outside the UK or EEA we rely on the Standard Contractual Clauses, the UK International Data Transfer Addendum, or an adequacy decision, and we will provide the relevant mechanism on request.

8. Assistance to you

Taking into account the nature of the processing, we will help you respond to data subject requests and to your obligations around security, breach notification, impact assessments and prior consultation. Feature requests that make this easier are welcome.

9. Personal data breaches

We will notify you without undue delay, and in any event within 48 hours of becoming aware of a breach affecting your personal data — inside the 72-hour window you have to notify your own authority. The notification will describe what happened, the categories and volume of data affected, the likely consequences, and the measures taken or proposed.

That 48-hour figure is a commitment one person can actually keep, which is why it is stated rather than buried in a longer document.

10. Deletion and return

On termination you may export your data for 30 days. After that we delete it, including from backups as they roll off within 35 days, unless a law requires us to retain it — in which case we keep it only for that purpose and continue to protect it.

11. Audits

We will make available the information reasonably necessary to demonstrate compliance, and allow for audits, including inspections, conducted by you or an auditor you mandate. We ask that audits be scheduled in advance, be scoped to the processing under this addendum, and be subject to confidentiality — and we will provide our security documentation first, since that answers most questions faster.

Be realistic about what an audit of a one-person operation can achieve. There is no SOC 2 report and there will not be one; the cost of the audit would exceed the revenue. What is available instead is unusually direct: the source, the deployment configuration and the running system are all inspectable, and the person who built it will answer your security team's questions himself rather than routing them through a questionnaire process.