Senduras

Data Processing Agreement

Last updated: November 21, 2026

Draft — pending legal review. This document has not yet been reviewed by legal counsel and may change before it takes effect. Passages marked [TO COMPLETE] are still to be filled in.

This Data Processing Agreement ('DPA') forms part of the Terms of Service between the Customer and Senduras ('Terms'). It sets out the terms required by Article 28 of Regulation (EU) 2016/679 ('GDPR') for the personal data that Senduras processes on the Customer's behalf when providing the Service. It applies automatically from the moment the Customer accepts the Terms; no separate signature is needed. A countersigned copy is available on request from privacy@senduras.io.

Terms defined in the Terms have the same meaning here. 'Personal data', 'processing', 'controller', 'processor', 'data subject', 'personal data breach', and 'supervisory authority' have the meaning given in the GDPR.

Table of contents

  1. Parties and roles
  2. Subject matter, nature, purpose, and duration
  3. Categories of personal data and data subjects
  4. Customer instructions and Customer obligations
  5. Obligations of Senduras
  6. Sub-processors
  7. International transfers
  8. Security measures
  9. Personal data breaches
  10. Assistance to the Customer
  11. Information and audits
  12. Return and deletion
  13. Liability and general provisions
  14. Annex 1: Sub-processors
  15. Annex 2: Technical and organisational measures

1. Parties and roles

The processor is Track42 ([TO COMPLETE: legal form and full registered company name]), doing business as Senduras, Boulevard Poincaré 31, 1070 Brussels, Belgium, enterprise number [TO COMPLETE: enterprise number (KBO/BCE)] ('Senduras'). The other party is the Customer identified in the Account.

For the personal data described in section 3, the Customer is the controller and Senduras is the processor. Where the Customer uses the Service for its End Clients (for example as an MSP), the Customer acts as processor for those End Clients and Senduras acts as its sub-processor. In that case the Customer confirms that its End Clients have authorised it to engage Senduras and to give the instructions in this DPA, and the Customer remains the sole point of contact for Senduras.

Senduras is a controller, not a processor, for the personal data it processes for its own purposes, such as managing the customer relationship, billing, securing the Service, and meeting its legal obligations. That processing is described in the Privacy Policy and is outside the scope of this DPA.

2. Subject matter, nature, purpose, and duration

  • Subject matter. Provision of the Senduras email-authentication monitoring Service to the Customer under the Terms.
  • Nature of the processing. Receiving, parsing, storing, analysing, aggregating, and displaying email-authentication reports and DNS check results for the Customer's Monitored Domains; sending alerts and notifications to recipients chosen by the Customer; hosting, backing up, and deleting the data; and providing support.
  • Purpose. To let the Customer monitor and improve the email authentication (SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, DNSSEC) of its Monitored Domains, and for no other purpose.
  • Duration. For the term of the Customer's Account, and afterwards until the data has been deleted in accordance with section 12.

3. Categories of personal data and data subjects

3.1 Email-authentication report data

DMARC aggregate reports and SMTP TLS reports are sent by mailbox providers and other mail receivers to the Customer's Senduras reporting addresses. They describe mail flows; they do not contain the content, subject line, or individual recipient addresses of email messages. They may contain:

  • IP addresses of servers that sent mail using the Customer's domains;
  • sending domains and other email-header and envelope metadata, such as the header-from domain, envelope-from (return-path) domain, DKIM signing domains and selectors, and SPF domains;
  • message counts, the date range of the report, and SPF, DKIM, and DMARC evaluation results;
  • the name and contact email address of the organisation that produced the report, and its report identifier;
  • for TLS reports: sending and receiving mail-server IP addresses and hostnames, the policies applied, and failure details.

Most of this data relates to mail infrastructure rather than to people. It is personal data to the extent that an IP address, domain name, or contact address can be linked to an identifiable individual, for example a sole trader's domain or a mail server operated by one person.

3.2 Account data managed by the Customer

  • Names, email addresses, roles, and authentication data (password hashes, multi-factor authentication secrets) of the Users the Customer invites to its Account, including users of its End Clients;
  • names of End Clients and the domains assigned to them;
  • recipients of alerts and notifications configured by the Customer, such as email addresses and webhook or chat-channel addresses;
  • records of User activity in the Account, such as login times and changes made, which may include IP addresses.

3.3 Data subjects

  • the Customer's Users, and Users of its End Clients;
  • individuals who operate or can be identified through the mail-sending or mail-receiving infrastructure that appears in reports;
  • contact persons at organisations that produce reports;
  • individuals the Customer designates as alert recipients.

3.4 Special categories

The Service is not designed to process special categories of personal data (Article 9 GDPR) or personal data relating to criminal convictions and offences (Article 10 GDPR). The Customer will not submit such data to the Service.

4. Customer instructions and Customer obligations

Senduras processes the personal data only on the Customer's documented instructions. The Terms, this DPA, and the Customer's use and configuration of the Service are the Customer's complete instructions. Further instructions must be given in writing and must be consistent with the Terms; if they require changes to the Service, the parties will agree on feasibility and cost first.

Senduras will inform the Customer if, in its opinion, an instruction infringes the GDPR or other EU or Member State data protection law, and may suspend carrying out that instruction until the Customer confirms or changes it.

Where EU or Member State law requires Senduras to process the personal data otherwise, Senduras will inform the Customer of that legal requirement before processing, unless that law prohibits this on important grounds of public interest.

The Customer is responsible for having a legal basis for the processing, for informing data subjects where required, and for only adding domains and directing reports that it is authorised to manage.

5. Obligations of Senduras

Senduras will:

  • process the personal data only as described in section 4;
  • ensure that the persons it authorises to process the personal data are bound by a duty of confidentiality and have access only to the extent they need it to do their work;
  • implement the security measures described in section 8;
  • engage sub-processors only in accordance with section 6;
  • assist the Customer as described in section 10;
  • delete or return the personal data as described in section 12;
  • make available the information needed to demonstrate compliance, and allow for audits, as described in section 11;
  • not sell the personal data, and not use it for its own purposes or for advertising.

6. Sub-processors

The Customer gives Senduras general authorisation to engage sub-processors. The sub-processors engaged at the date of this DPA are listed in Annex 1.

Senduras will inform the Customer of any intended addition or replacement of a sub-processor at least 30 days in advance, by email to the Account owner and by updating Annex 1. The Customer may object on reasonable data-protection grounds within that period. The parties will then discuss the objection in good faith. If no solution is found, the Customer may terminate the affected Service before the change takes effect and receive a refund of the fees prepaid for the period after termination.

Senduras imposes on each sub-processor, by written contract, data protection obligations that offer at least the same level of protection as this DPA, and remains fully liable to the Customer for the performance of its sub-processors.

7. International transfers

Senduras is established in Belgium and aims to process the personal data within the European Economic Area ('EEA'). Some sub-processors listed in Annex 1 are established, or have parent companies established, outside the EEA, in particular in the United States.

Senduras will only transfer the personal data outside the EEA, or allow a sub-processor to do so, where Chapter V of the GDPR is complied with, namely on the basis of:

  • an adequacy decision of the European Commission, including the EU-US Data Privacy Framework for recipients certified under it; or
  • the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914, together with supplementary measures where a transfer assessment shows they are needed.

The transfer mechanism that applies to each sub-processor is stated in Annex 1. On request, Senduras will provide a copy of the relevant safeguards, with commercial terms removed.

If the Customer is established outside the EEA in a country without an adequacy decision, and the GDPR applies to the processing, the standard contractual clauses (Module Four, processor to controller) are incorporated into this DPA by reference to the extent required, with Senduras as data exporter and the Customer as data importer, and with Belgian law and the Belgian courts as the governing law and forum.

8. Security measures

Taking into account the state of the art, the costs of implementation, the nature, scope, context, and purposes of the processing, and the risks for data subjects, Senduras implements appropriate technical and organisational measures to protect the personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure, or access (Article 32 GDPR). The measures in place at the date of this DPA are described in Annex 2. Senduras may update them as technology develops, provided the overall level of protection is not reduced.

The Customer is responsible for the secure use of the Service on its side, including choosing strong passwords, enabling multi-factor authentication, assigning appropriate roles to its Users, and removing access that is no longer needed.

9. Personal data breaches

Senduras will notify the Customer without undue delay after becoming aware of a personal data breach affecting the Customer's personal data, by email to the Account owner. The notification will describe, as far as the information is available at that time:

  • the nature of the breach, including the categories and approximate number of data subjects and records concerned;
  • the likely consequences;
  • the measures taken or proposed to address the breach and limit its effects;
  • a contact point for further information.

Where not all information is available at once, Senduras will provide it in phases without further undue delay. Senduras will take reasonable steps to contain and remedy the breach and will cooperate with the Customer so that the Customer can meet its own notification obligations under Articles 33 and 34 GDPR. Notification of a breach is not an admission of fault or liability.

10. Assistance to the Customer

Data subject requests. If Senduras receives a request from a data subject that relates to the Customer's personal data, it will forward the request to the Customer without undue delay and will not answer it itself, other than to say that it has been forwarded. Taking into account the nature of the processing, Senduras will assist the Customer with appropriate technical and organisational measures, in so far as possible, in responding to requests from data subjects exercising their rights under Chapter III of the GDPR.

Other assistance. Taking into account the nature of the processing and the information available to it, Senduras will assist the Customer in ensuring compliance with Articles 32 to 36 GDPR (security, breach notification, data protection impact assessments, and prior consultation of the supervisory authority).

Assistance that goes beyond what the Service already offers and requires substantial effort may be charged at a reasonable rate agreed in advance.

11. Information and audits

On written request, Senduras will make available to the Customer the information reasonably needed to demonstrate compliance with Article 28 GDPR and this DPA, such as a description of its security measures and answers to reasonable security questionnaires.

If that information is not sufficient to demonstrate compliance, the Customer may carry out an audit, or have one carried out by an independent auditor bound by confidentiality, subject to the following conditions: at least 30 days' written notice; no more than once in any 12-month period, unless a supervisory authority requires the audit or a personal data breach affecting the Customer has occurred; during business hours and without unreasonably disrupting Senduras's operations; and without access to data of other customers. Each party bears its own costs of an audit, unless the audit reveals a material breach of this DPA by Senduras, in which case Senduras bears the reasonable costs of the audit.

12. Return and deletion

During the term, the Customer can view and delete personal data through the Service. After the end of the Service, Senduras will, at the choice of the Customer, return the personal data by providing an export in a commonly used, machine-readable format, or delete it. If the Customer makes no choice within 30 days after the end of the Service, Senduras deletes the personal data from its production systems.

Copies held in backups are removed in the course of the normal backup rotation and in any case no later than six months after the end of the Service. Until then, they remain protected by this DPA and are not processed for any other purpose.

Senduras may retain personal data to the extent and for the period that EU or Member State law requires it to do so, and will inform the Customer of that requirement on request.

13. Liability and general provisions

  • Liability. Each party's liability under this DPA is subject to the limitations and exclusions in the Terms. Nothing in this DPA limits the rights of data subjects or the liability of either party towards them under Article 82 GDPR.
  • Precedence. If this DPA conflicts with the Terms or an Order Form as regards the processing of personal data, this DPA prevails. If standard contractual clauses apply and conflict with this DPA, the standard contractual clauses prevail.
  • Changes. Senduras may update this DPA where required by law or by a decision of a supervisory authority, or to reflect changes to the Service or its sub-processors, following the procedure for changes in the Terms. An update will not reduce the level of protection of the personal data.
  • Governing law and courts. This DPA is governed by Belgian law. The courts designated in the Terms have jurisdiction.
  • Supervisory authority. The lead supervisory authority for Senduras is the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données), Rue de la Presse 35 / Drukpersstraat 35, 1000 Brussels, Belgium.
  • Contact. Data protection questions and notices under this DPA: privacy@senduras.io.

Annex 1: Sub-processors

The following sub-processors process personal data covered by this DPA. Items still to be confirmed are marked.

Sub-processorPurposePersonal data involvedLocation and transfer mechanism
[TO COMPLETE: hosting or data-centre provider: name and contracting entity] Hosting of the application servers and the database All data described in section 3 [TO COMPLETE: data-centre country; transfer mechanism if outside the EEA]
Object storage provider [TO COMPLETE: confirm provider and contracting entity (Cloudflare R2 or Amazon S3)] Storage of raw report files and database backups All data described in section 3 [TO COMPLETE: storage region; transfer mechanism]
Mailgun [TO COMPLETE: contracting entity (Mailgun Technologies, Inc. / Sinch)] Receiving DMARC and TLS reports sent to Senduras reporting addresses and forwarding them to the platform Report data (section 3.1) [TO COMPLETE: EU or US region; transfer mechanism]
Amazon Web Services (Amazon Simple Email Service) [TO COMPLETE: contracting entity, e.g. Amazon Web Services EMEA SARL] Sending transactional email: alerts, invitations, password resets, and summaries Names and email addresses of Users and alert recipients; domain names and findings mentioned in the email [TO COMPLETE: SES region; transfer mechanism]
Sentry (Functional Software, Inc.) [TO COMPLETE: confirm entity] Error and performance monitoring of the platform Technical event data, which may include User identifiers, IP addresses, and fragments of the data being processed when an error occurred [TO COMPLETE: EU or US data region; transfer mechanism]

Stripe processes payments for subscriptions. Stripe receives billing contact and payment details of the Customer, for which Senduras is the controller (see the Privacy Policy); it does not receive report data. It is listed here for transparency: Stripe [TO COMPLETE: contracting entity, e.g. Stripe Payments Europe, Limited (Ireland)].

Annex 2: Technical and organisational measures

Access control

  • Each Customer's data is logically separated from that of other Customers; every request is scoped to the Customer's Account.
  • Role-based access control within an Account (Owner, Admin, Analyst, Viewer).
  • Passwords are stored only as salted hashes (bcrypt).
  • Multi-factor authentication (time-based one-time passwords) is available to Users; the secrets are stored encrypted.
  • Login attempts are rate limited.
  • Access by Senduras staff to production systems is limited to those who need it for operations and support. [TO COMPLETE: confirm]

Transmission and storage

  • Connections to the website and the platform are encrypted with TLS.
  • Inbound report deliveries from the mail-receiving provider are authenticated by a cryptographic signature before they are accepted.
  • Encryption of data at rest: [TO COMPLETE: describe encryption at rest of the database, object storage, and backups].

Availability and resilience

  • Automated daily database backups, stored separately from the database server.
  • Backup retention: [TO COMPLETE: daily, weekly, and monthly retention periods].
  • Automated health checks, including a check that the latest backup completed.

Monitoring and incident handling

  • Application errors are monitored centrally.
  • Security incidents are assessed and, where they affect personal data, handled in accordance with section 9.

Organisational measures

  • Staff with access to personal data are bound by confidentiality obligations. [TO COMPLETE: confirm]
  • [TO COMPLETE: any further measures to list: security policies, staff training, penetration testing, certifications]