Skip to content

Data processing agreement

The Art. 28 GDPR agreement under which DueReason processes personal data for its customers, with the technical and organisational measures in place.

Last updated

Operator

Company
Override Technologies
Email
hello@duereason.com

This data processing agreement ("DPA") is part of the terms of service between the customer, as controller, and the operator of DueReason named at the top of this page ("we"), as processor. It applies whenever we process personal data on the customer's behalf in providing DueReason, and meets Article 28(3) of the General Data Protection Regulation (EU) 2016/679 ("GDPR"). It applies without a signature; if you need a signed copy, write to us.

1. Subject matter and duration

  1. The subject matter is the processing of the customer's personal data in providing DueReason under the terms.
  2. The DPA lasts as long as the terms, and after that until the customer's data has been deleted under section 9.

2. Nature and purpose

We host, store, structure, display, transmit, hash, sign, export and delete personal data so that the customer can, as it configures the service:

  • route approval requests from its agents and systems to the people who must answer them, record their answers, comments and evidence, and issue signed grants;
  • notify its staff and the people concerned by email, Slack, Microsoft Teams, browser notifications and webhooks;
  • keep an audit log and hash-chained ledgers of these events, and export them;
  • if the customer enables the platform-work module: record decisions about people who work through its platform, issue statements of reasons and handle requests for human review;
  • if the customer enables the DSA notice-and-action module: receive and handle notices under Art. 16 of the Digital Services Act.

3. Types of personal data

  • The customer's staff: name, email address, role, approver groups, answers, comments and evidence they submit, training attestations, and IP addresses and actions in the audit log.
  • Approval requests: title, reason and payload (which may name payees, amounts, account or invoice numbers, people or anything else the customer's systems send), the requesting agent's description and context links.
  • Evidence files: photos and documents, which may show people or contain any personal data the customer chooses to upload.
  • If the customer enables the platform-work module, also people affected by decisions (for example, platform workers): the customer's reference for them, country, contractual status, activity level, language, contact email; decisions about them with the reasons and facts; statements of reasons and when they were opened; review requests and comments; remedies.
  • If the customer enables the DSA notice-and-action module, also DSA notices: the notifier's name and email address, the location of the reported content and the explanation.

The service is not designed for special categories of personal data (Art. 9 GDPR) or data on criminal convictions (Art. 10 GDPR). Whether such data is submitted, for example in free text or evidence, is the customer's decision and responsibility.

4. Categories of data subjects

The customer's employees and contractors who use DueReason; payees, suppliers and other people named in approval requests or shown in evidence. If the customer enables the platform-work module, also people who work through its platform and other people affected by its decisions. If it enables the DSA notice-and-action module, also people who send DSA notices and people whose content is reported.

5. Our obligations

  1. Instructions. We process the personal data only on the customer's documented instructions, including on transfers to third countries, unless Union or Member State law requires otherwise; in that case we tell the customer first, unless that law forbids it. The terms, this DPA and the customer's configuration and use of the service are the customer's instructions. We tell the customer at once if we believe an instruction infringes data protection law.
  2. Confidentiality. Everyone we authorise to process the personal data is bound by confidentiality, by contract or by law.
  3. Security. We take the measures required by Art. 32 GDPR; they are listed in the annex. We may change them, but never in a way that lowers the overall level of protection.
  4. Subprocessors. The customer gives us general written authorisation to engage the subprocessors listed on the subprocessors page. We give at least 30 days' notice of a new or replacement subprocessor by email to the customer's owners and on that page; the customer may object as described there. We impose on each subprocessor, by contract, the same data protection obligations as this DPA, and we remain fully liable to the customer for its performance.
  5. Data subjects' requests. The service gives the customer the means to answer requests itself: people affected by decisions read their statements and ask for review through the worker portal; the console shows, exports and corrects the records, and can erase a worker's contact details. If a data subject contacts us directly, we pass the request to the customer without undue delay and do not answer it ourselves unless the customer instructs us to.
  6. Assistance. Taking into account the nature of the processing and the information available to us, we help the customer meet its obligations under Art. 32 to 36 GDPR: security, notification of personal data breaches, data protection impact assessments (the service includes a template at Exports, DPIA) and prior consultation.
  7. Personal data breaches. We notify the customer's owners without undue delay, and at the latest within 48 hours, after becoming aware of a personal data breach affecting the customer's data, with the information required by Art. 33(3) GDPR as far as it is available, and further information as it becomes available.
  8. Deletion and return. At the end of the service we delete the personal data, or return it by letting the customer export it, as set out in section 9, unless Union or Member State law requires us to keep it.
  9. Information and audits. We make available to the customer the information needed to demonstrate compliance with Art. 28 GDPR, and allow and contribute to audits, including inspections, by the customer or an auditor it appoints who is bound by confidentiality. Audits take place after at least 30 days' written notice, at most once a year unless a supervisory authority requires it or a personal data breach justifies it, during business hours and without access to other customers' data. Each party bears its own costs.

6. The customer's obligations

The customer is responsible for the lawfulness of the processing it instructs, including its legal basis and the information it gives data subjects; for configuring the service (retention, access, workflows) to suit its purposes; and for the personal data it submits. It informs us without delay of any error it finds in the processing.

7. Transfers

We host the customer's personal data in the European Union. Transfers outside the European Economic Area take place only through subprocessors listed on the subprocessors page, with the safeguards shown there (an adequacy decision or the European Commission's standard contractual clauses). Where the customer itself sends data elsewhere (Slack, Microsoft Teams, webhooks, browser notifications of its staff), that transfer is the customer's.

8. Retention during the service

The customer sets a retention period between 24 and 120 months (72 by default) under Settings, Organization. A daily job then deletes, once the period has passed: closed decisions and approval requests with their answers and evidence (in whole verified sections of the ledger, so what remains still verifies), the contact details of workers with no remaining decisions and no updates in the period, and the records of sent emails and finished webhook deliveries. Messages for Slack, Teams and browser notifications are deleted 30 days after they were created, once sent or given up. The audit log is kept for as long as the organization exists.

9. Deletion at the end

  1. The customer can export its data at any time under Exports in the console.
  2. An owner can delete the organization under Settings, Organization. Deletion takes place 30 days after the request unless an owner cancels it; owners are emailed when it is scheduled, seven days before, and when it is done.
  3. Deletion removes all of the organization's personal data, including its ledgers, audit log and evidence files in every storage location. Database backups that still contain it expire within 17 days (14 days on our servers and in the point-in-time archive; the off-site copy is locked for 14 days and removed after that). We keep only a record that the organization existed (its identifier, its address in the service and the dates), with no personal data.
  4. If the terms end without the customer deleting its organization, we keep the data available for export for 30 days and then delete it in the same way.

10. Liability and precedence

Liability under this DPA follows the terms of service, without prejudice to Art. 82 GDPR. In case of conflict on the protection of personal data, this DPA takes precedence over the terms.

Annex: technical and organisational measures

Hosting and network

  • The service, its database and its backups run on servers of Contabo GmbH in Germany. Evidence files and an encrypted copy of the backups are stored with Backblaze in Amsterdam (eu-central-003); the backup copies are locked against deletion for 14 days.
  • Every connection to the service uses HTTPS, with HTTP Strict Transport Security for one year.
  • Inside the cluster, network policies admit only the ingress proxy to the application.
  • Every page carries a Content Security Policy with a fresh nonce, and security headers.

Access by the customer's people

  • Accounts with a password of at least 12 characters, stored only as a salted hash; all sessions are revoked when the password is reset.
  • Two-factor authentication with an authenticator app (TOTP) and single-use backup codes, available to everyone; an organization can require it of all its members.
  • Five wrong passwords for one account within 15 minutes lock sign-in for that account for 15 minutes; five wrong codes lock the second factor for 15 minutes. Authentication routes are also rate-limited per IP address, with limits stored in the database so they hold across servers.
  • Roles (owner, admin, reviewer, auditor) with fixed permissions, checked on the server for every request; membership and role are re-read on every request, so removing a person takes effect at once. Invitations expire after seven days.
  • API keys are shown once and stored only as a SHA-256 hash, carry limited scopes and are rate-limited.
  • Separation of duties in approvals: a requester cannot approve their own request, a person counts once per request, and eligibility is checked at the moment of answering.

Access by our people

  • Administrative access to servers, the cluster and the database is limited to our named administrators.
  • Credentials are kept as encrypted secrets in the deployment configuration, never in source code, and are checked at start-up without being printed.

Integrity and accountability

  • Approval requests and decisions are recorded on per-organization hash chains (ledgers), verified every six hours and by every restore drill. A part of a chain that does not verify is never deleted.
  • Approved requests produce grants signed with an Ed25519 key per organization, bound to the hash of the approved payload and usable once. The private keys are stored encrypted with AES-256-GCM.
  • The audit log and the authentication events are append-only: the database refuses changes to them, and deletes outside retention and organization deletion.
  • Webhooks are signed with a secret per endpoint; worker portal links are signed and can be revoked.

Evidence files

  • File types are decided by the content of the file, not its name; at most five files of 10 MB per answer.
  • Where malware scanning is enabled, every file is scanned on our own servers (ClamAV) before it is stored, and an answer with an infected file is refused.
  • Files are downloaded as attachments with a restrictive content policy. Each file's SHA-256 is recorded on the ledger.
  • In object storage, every file is encrypted at rest (AES-256).

Availability and recovery

  • Hourly database backups, checked after each run, kept 48 hours and one a day kept 14 days, with an encrypted off-site copy that nobody, including us, can delete for 14 days.
  • A continuous point-in-time archive of the database (every change and a daily base backup) in Contabo Object Storage in the EU, kept 14 days.
  • A weekly restore drill restores the latest backup and re-verifies every ledger.
  • The production web application runs as two instances.

Data minimisation and deletion

  • Retention set by the customer and applied daily; organization deletion as in section 9.
  • Public forms keep only a keyed hash of the sender's IP address, for ten minutes.
  • Error logs exclude database query values and email content.

Development

  • Dependencies are scanned for known vulnerabilities on every build, and a build with a high or critical finding fails. The code history is scanned for secrets.
  • Changes are deployed only from builds that passed the automated checks, and every deployment is recorded.