Data processing agreement
Standard Contractual Clauses for the purposes of Article 28(3) of Regulation 2016/679 (the GDPR), between the customer as data controller and NFI ApS as data processor.
Last updated: 18 November 2026.
These clauses follow the English version of the Danish Data Protection Agency's standard contractual clauses. Clauses 1 to 14 are the template text word for word; only the template's own fields are filled in. Appendices A to D describe how Senderward processes personal data.
Parties
Data controller: the business that has a Senderward account and has accepted the terms of service, as identified by its account.
Data processor: NFI ApS, CVR 45583112, Langfreddal 3, 8471 Sabro, Denmark.
These clauses are accepted together with the terms of service when the account is created. On request, the data processor provides a signed copy.
Table of contents
- Preamble
- The rights and obligations of the data controller
- The data processor acts according to instructions
- Confidentiality
- Security of processing
- Use of sub-processors
- Transfer of data to third countries or international organisations
- Assistance to the data controller
- Notification of personal data breach
- Erasure and return of data
- Audit and inspection
- The parties' agreement on other terms
- Commencement and termination
- Data controller and data processor contacts/contact points
Appendices: A: Information about the processing · B: Authorised sub-processors · C: Instruction pertaining to the use of personal data · D: The parties' terms of agreement on other subjects
1. Preamble
1.1. These Contractual Clauses (the Clauses) set out the rights and obligations of the data controller and the data processor, when processing personal data on behalf of the data controller.
1.2. The Clauses have been designed to ensure the parties’ compliance with Article 28(3) of Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data and repealing Directive 95/46/EC (General Data Protection Regulation).
1.3. In the context of the provision of Senderward, the data processor will process personal data on behalf of the data controller in accordance with the Clauses.
1.4. The Clauses shall take priority over any similar provisions contained in other agreements between the parties.
1.5. Four appendices are attached to the Clauses and form an integral part of the Clauses.
1.6. Appendix A contains details about the processing of personal data, including the purpose and nature of the processing, type of personal data, categories of data subject and duration of the processing.
1.7. Appendix B contains the data controller’s conditions for the data processor’s use of sub-processors and a list of sub-processors authorised by the data controller.
1.8. Appendix C contains the data controller’s instructions with regards to the processing of personal data, the minimum security measures to be implemented by the data processor and how audits of the data processor and any sub-processors are to be performed.
1.9. Appendix D contains provisions for other activities which are not covered by the Clauses.
1.10. The Clauses along with appendices shall be retained in writing, including electronically, by both parties.
1.11. The Clauses shall not exempt the data processor from obligations to which the data processor is subject pursuant to the General Data Protection Regulation (the GDPR) or other legislation.
2. The rights and obligations of the data controller
2.1. The data controller is responsible for ensuring that the processing of personal data takes place in compliance with the GDPR (see Article 24 GDPR), the applicable EU or Member State data protection provisions and the Clauses.
2.2. The data controller has the right and obligation to make decisions about the purposes and means of the processing of personal data.
2.3. The data controller shall be responsible, among other, for ensuring that the processing of personal data, which the data processor is instructed to perform, has a legal basis.
3. The data processor acts according to instructions
3.1. The data processor shall process personal data only on documented instructions from the data controller, unless required to do so by Union or Member State law to which the processor is subject. Such instructions shall be specified in appendices A and C. Subsequent instructions can also be given by the data controller throughout the duration of the processing of personal data, but such instructions shall always be documented and kept in writing, including electronically, in connection with the Clauses.
3.2. The data processor shall immediately inform the data controller if instructions given by the data controller, in the opinion of the data processor, contravene the GDPR or the applicable EU or Member State data protection provisions.
4. Confidentiality
4.1. The data processor shall only grant access to the personal data being processed on behalf of the data controller to persons under the data processor’s authority who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality and only on a need to know basis. The list of persons to whom access has been granted shall be kept under periodic review. On the basis of this review, such access to personal data can be withdrawn, if access is no longer necessary, and personal data shall consequently not be accessible anymore to those persons.
4.2. The data processor shall at the request of the data controller demonstrate that the concerned persons under the data processor’s authority are subject to the abovementioned confidentiality.
5. Security of processing
5.1. Article 32 GDPR stipulates that, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the data controller and data processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.
The data controller shall evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. Depending on their relevance, the measures may include the following:
- Pseudonymisation and encryption of personal data;
- the ability to ensure ongoing confidentiality, integrity, availability and resilience of processing systems and services;
- the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident;
- a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.
5.2. According to Article 32 GDPR, the data processor shall also – independently from the data controller – evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. To this effect, the data controller shall provide the data processor with all information necessary to identify and evaluate such risks.
5.3. Furthermore, the data processor shall assist the data controller in ensuring compliance with the data controller’s obligations pursuant to Articles 32 GDPR, by inter alia providing the data controller with information concerning the technical and organisational measures already implemented by the data processor pursuant to Article 32 GDPR along with all other information necessary for the data controller to comply with the data controller’s obligation under Article 32 GDPR.
If subsequently – in the assessment of the data controller – mitigation of the identified risks require further measures to be implemented by the data processor, than those already implemented by the data processor pursuant to Article 32 GDPR, the data controller shall specify these additional measures to be implemented in Appendix C.
6. Use of sub-processors
6.1. The data processor shall meet the requirements specified in Article 28(2) and (4) GDPR in order to engage another processor (a sub-processor).
6.2. The data processor shall therefore not engage another processor (sub-processor) for the fulfilment of the Clauses without the prior general written authorisation of the data controller.
6.3. The data processor has the data controller’s general authorisation for the engagement of sub-processors. The data processor shall inform in writing the data controller of any intended changes concerning the addition or replacement of sub-processors at least 30 days in advance, thereby giving the data controller the opportunity to object to such changes prior to the engagement of the concerned sub-processor(s). Longer time periods of prior notice for specific sub-processing services can be provided in Appendix B. The list of sub-processors already authorised by the data controller can be found in Appendix B.
6.4. Where the data processor engages a sub-processor for carrying out specific processing activities on behalf of the data controller, the same data protection obligations as set out in the Clauses shall be imposed on that sub-processor by way of a contract or other legal act under EU or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the Clauses and the GDPR.
The data processor shall therefore be responsible for requiring that the sub-processor at least complies with the obligations to which the data processor is subject pursuant to the Clauses and the GDPR.
6.5. A copy of such a sub-processor agreement and subsequent amendments shall – at the data controller’s request – be submitted to the data controller, thereby giving the data controller the opportunity to ensure that the same data protection obligations as set out in the Clauses are imposed on the sub-processor. Clauses on business related issues that do not affect the legal data protection content of the sub-processor agreement, shall not require submission to the data controller.
6.6. The data processor shall agree a third-party beneficiary clause with the sub-processor where – in the event of bankruptcy of the data processor – the data controller shall be a third-party beneficiary to the sub-processor agreement and shall have the right to enforce the agreement against the sub-processor engaged by the data processor, e.g. enabling the data controller to instruct the sub-processor to delete or return the personal data.
6.7. If the sub-processor does not fulfil his data protection obligations, the data processor shall remain fully liable to the data controller as regards the fulfilment of the obligations of the sub-processor. This does not affect the rights of the data subjects under the GDPR – in particular those foreseen in Articles 79 and 82 GDPR – against the data controller and the data processor, including the sub-processor.
7. Transfer of data to third countries or international organisations
7.1. Any transfer of personal data to third countries or international organisations by the data processor shall only occur on the basis of documented instructions from the data controller and shall always take place in compliance with Chapter V GDPR.
7.2. In case transfers to third countries or international organisations, which the data processor has not been instructed to perform by the data controller, is required under EU or Member State law to which the data processor is subject, the data processor shall inform the data controller of that legal requirement prior to processing unless that law prohibits such information on important grounds of public interest.
7.3. Without documented instructions from the data controller, the data processor therefore cannot within the framework of the Clauses:
- transfer personal data to a data controller or a data processor in a third country or in an international organization
- transfer the processing of personal data to a sub-processor in a third country
- have the personal data processed in by the data processor in a third country
7.4. The data controller’s instructions regarding the transfer of personal data to a third country including, if applicable, the transfer tool under Chapter V GDPR on which they are based, shall be set out in Appendix C.6.
7.5. The Clauses shall not be confused with standard data protection clauses within the meaning of Article 46(2)(c) and (d) GDPR, and the Clauses cannot be relied upon by the parties as a transfer tool under Chapter V GDPR.
See Appendix C.6.
8. Assistance to the data controller
8.1. Taking into account the nature of the processing, the data processor shall assist the data controller by appropriate technical and organisational measures, insofar as this is possible, in the fulfilment of the data controller’s obligations to respond to requests for exercising the data subject’s rights laid down in Chapter III GDPR.
This entails that the data processor shall, insofar as this is possible, assist the data controller in the data controller’s compliance with:
- the right to be informed when collecting personal data from the data subject
- the right to be informed when personal data have not been obtained from the data subject
- the right of access by the data subject
- the right to rectification
- the right to erasure (‘the right to be forgotten’)
- the right to restriction of processing
- notification obligation regarding rectification or erasure of personal data or restriction of processing
- the right to data portability
- the right to object
- the right not to be subject to a decision based solely on automated processing, including profiling
8.2. In addition to the data processor’s obligation to assist the data controller pursuant to Clause 6.3., the data processor shall furthermore, taking into account the nature of the processing and the information available to the data processor, assist the data controller in ensuring compliance with:
- The data controller’s obligation to without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the competent supervisory authority, the Danish Data Protection Agency (Datatilsynet) for a data controller established in Denmark, otherwise the supervisory authority competent for the data controller, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons;
- the data controller’s obligation to without undue delay communicate the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons;
- the data controller’s obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a data protection impact assessment);
- the data controller’s obligation to consult the competent supervisory authority, the Danish Data Protection Agency (Datatilsynet) for a data controller established in Denmark, otherwise the supervisory authority competent for the data controller, prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the data controller to mitigate the risk.
8.3. The parties shall define in Appendix C the appropriate technical and organisational measures by which the data processor is required to assist the data controller as well as the scope and the extent of the assistance required. This applies to the obligations foreseen in Clause 9.1. and 9.2.
9. Notification of personal data breach
9.1. In case of any personal data breach, the data processor shall, without undue delay after having become aware of it, notify the data controller of the personal data breach.
9.2. The data processor’s notification to the data controller shall, if possible, take place within 48 hours after the data processor has become aware of the personal data breach to enable the data controller to comply with the data controller’s obligation to notify the personal data breach to the competent supervisory authority, cf. Article 33 GDPR.
9.3. In accordance with Clause 9(2)(a), the data processor shall assist the data controller in notifying the personal data breach to the competent supervisory authority, meaning that the data processor is required to assist in obtaining the information listed below which, pursuant to Article 33(3)GDPR, shall be stated in the data controller’s notification to the competent supervisory authority:
- The nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
- the likely consequences of the personal data breach;
- the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
9.4. The parties shall define in Appendix C all the elements to be provided by the data processor when assisting the data controller in the notification of a personal data breach to the competent supervisory authority.
10. Erasure and return of data
10.1. On termination of the provision of personal data processing services, the data processor shall be under obligation to delete all personal data processed on behalf of the data controller and certify to the data controller that it has done so.
See Appendix C.4.
11. Audit and inspection
11.1. The data processor shall make available to the data controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 and the Clauses and allow for and contribute to audits, including inspections, conducted by the data controller or another auditor mandated by the data controller.
11.2. Procedures applicable to the data controller’s audits, including inspections, of the data processor and sub-processors are specified in appendices C.7. and C.8.
11.3. The data processor shall be required to provide the supervisory authorities, which pursuant to applicable legislation have access to the data controller’s and data processor’s facilities, or representatives acting on behalf of such supervisory authorities, with access to the data processor’s physical facilities on presentation of appropriate identification.
See Appendix C.7 and C.8.
12. The parties’ agreement on other terms
12.1. The parties may agree other clauses concerning the provision of the personal data processing service specifying e.g. liability, as long as they do not contradict directly or indirectly the Clauses or prejudice the fundamental rights or freedoms of the data subject and the protection afforded by the GDPR.
See Appendix D.
13. Commencement and termination
13.1. The Clauses shall become effective on the date of both parties’ signature.
13.2. Both parties shall be entitled to require the Clauses renegotiated if changes to the law or inexpediency of the Clauses should give rise to such renegotiation.
13.3. The Clauses shall apply for the duration of the provision of personal data processing services. For the duration of the provision of personal data processing services, the Clauses cannot be terminated unless other Clauses governing the provision of personal data processing services have been agreed between the parties.
13.4. If the provision of personal data processing services is terminated, and the personal data is deleted or returned to the data controller pursuant to Clause 11.1. and Appendix C.4., the Clauses may be terminated by written notice by either party.
13.5. Signature
- On behalf of the data controller
- The business that holds the Senderward account. Accepted electronically together with the terms of service when the account is created.
- On behalf of the data processor
- NFI ApS, CVR 45583112. A signed copy is provided on request.
The clauses apply from when the data controller creates a Senderward account and for as long as the data processor processes personal data on its behalf, and until all personal data processed on behalf of the data controller has been deleted or returned.
14. Data controller and data processor contacts/contact points
14.1. The parties may contact each other using the following contacts/contact points:
14.2. The parties shall be under obligation continuously to inform each other of changes to contacts/contact points.
- Data controller
- The business that holds the Senderward account. E-mail: the email address of the account.
- Data processor
- NFI ApS. E-mail: [email protected]
Appendix A: Information about the processing
A.1 The purpose of the data processor's processing of personal data on behalf of the data controller
To monitor the email security records (DMARC, SPF, DKIM, MX, MTA-STS, TLS-RPT) of the domains the data controller adds, to show the results and history in the dashboard, and to email alerts, notices and a weekly status about them.
When the data controller points a domain's DMARC rua address to the data processor: to receive the DMARC aggregate reports for that domain and show the data controller who sends mail as its domain and whether that mail passes SPF, DKIM and DMARC.
A.2 The nature of the processing
- Verifying each domain by looking up a DNS TXT record (
_senderward.<domain>) at public resolvers. - Collecting the domain's public DNS records once a day through Lookproof, the data processor's own DNS checking service (an internal service of NFI ApS, not a sub-processor), storing the result, and comparing it with earlier results.
- Checking a change again before alerting, and emailing alerts and status to the account's email address through Amazon SES.
- Showing results, changes and the last 30 days in the dashboard.
- DMARC aggregate reports: receiving them at the domain's report address through Amazon SES, which stores the incoming mail in Amazon S3; reading and parsing the report; storing the report file and the rows extracted from it; looking up the host name (reverse DNS) of each sending IP address; showing the results in the dashboard and listing new senders that fail DMARC in the weekly status.
- Mail to the report address that is not a DMARC aggregate report (for example a forensic/RUF report or any other mail) is discarded without being stored. Only the time, the sender's domain, the size and the reason are recorded, and the mail is deleted from Amazon S3.
A.3 Types of personal data
- Domain names, where they identify a person (for example a sole trader's own name).
- Public DNS records of the domains, which can contain email addresses (for example DMARC report addresses).
- Check results, changes found, and which alerts were sent and when.
- The email address that receives alerts and status mail, and the content of those mails, kept in the mail queue until 90 days after sending.
No special categories of personal data (GDPR art. 9) or data about criminal offences (art. 10) are processed.
DMARC aggregate reports, when the data controller sends them to the data processor: the reporting organisation and the address it reports from; the report period and the DMARC policy it saw; for each sending source the IP address of the sending server and its host name (reverse DNS), the sender domains (header From, envelope From, and the domains in the DKIM and SPF results), the number of messages, and the SPF, DKIM and DMARC results. No message content is processed. For mail that is discarded: time, sender's domain, size and reason only.
A.4 Categories of data subject
- The data controller's employees or contact persons who use the account or receive its mail.
- Persons whose name is a monitored domain name, or whose email address appears in a monitored domain's public DNS records.
- Persons who can be identified from the IP address, host name or sender domain of a server that sends mail in a monitored domain's name, as listed in the DMARC aggregate reports.
A.5 Duration of the processing
For as long as the data controller has a Senderward account. A domain's data is processed while the domain is in the account; when it is removed, its check history is deleted at once. After the account ends: see C.4.
Appendix B: Authorised sub-processors
B.1 Approved sub-processors
On commencement of the clauses, the data controller authorises the use of the following sub-processors. Stripe is not a sub-processor: it processes billing data about the data controller as our customer (email address, company name, billing address, tax ID and payment details), for which NFI ApS and Stripe are each controllers (see the privacy policy). Stripe may process that data in the USA; Stripe states the EU-U.S. Data Privacy Framework as its transfer basis, with Standard Contractual Clauses as a fallback. Lookproof is the data processor's own internal service. There is no hosting provider: servers are operated by NFI ApS in Denmark (EU).
| Name | Address | Location of processing | Description of processing |
|---|---|---|---|
| Amazon Web Services EMEA SARL (Amazon SES, SNS and S3) | 38 Avenue John F. Kennedy, L-1855 Luxembourg | AWS region eu-north-1 (Stockholm, Sweden). AWS states it does not transfer customer data out of the region the customer selects, except as needed to provide the services or to comply with the law. | Sends alerts, notices and the weekly status (recipient address and mail content), and reports bounces and complaints back to us. No open or click tracking. Receives DMARC aggregate reports for the data controller's domains (Amazon SES receiving) and stores the incoming mail in Amazon S3 in the same region, where it is deleted after 7 days (mail that is not an aggregate report as soon as it has been read). Amazon SES also keeps its own list of addresses that bounced or complained, to protect the sending reputation; it holds the address itself and is kept until we remove the address. Transfer basis stated by AWS: certified to the EU-U.S. Data Privacy Framework (under the Amazon.com, Inc. certification), and Standard Contractual Clauses in the AWS GDPR Data Processing Addendum for transfers to third countries. |
| Cloudflare, Inc. | 101 Townsend Street, San Francisco, CA 94107, USA | Cloudflare's global network, nearest data centre to the user | CDN, reverse proxy and TLS for senderward.com: all traffic to the dashboard passes through it. Turnstile bot protection on sign-up and sign-in. Public DNS resolver 1.1.1.1 for verification lookups (domain names only). Reverse DNS lookups of sending IP addresses from DMARC aggregate reports also go here (IP addresses only). Transfer basis stated by Cloudflare in its Customer DPA: the EU-U.S. Data Privacy Framework, and Standard Contractual Clauses if that certification lapses or for other restricted transfers. |
| Google LLC (Google Public DNS) | 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA | Google's global network | Public DNS resolver 8.8.8.8 for verification lookups (domain names only). Reverse DNS lookups of sending IP addresses from DMARC aggregate reports also go here (IP addresses only). Transfer basis stated by Google: Google LLC is certified to the EU-U.S. Data Privacy Framework. Google Public DNS is used without a contract and follows the Google Privacy Policy. |
| Heinlein Hosting GmbH (mailbox.org) | Schwedter Straße 8/9A, 10119 Berlin, Germany | Germany (EU) | Hosts the data processor's own mailboxes: support@ and privacy@ (the controller's emails to us) and the operational alerts the service sends to the data processor. Not used for mail the service sends to customers. |
| Hetzner Online GmbH (Storage Box) | Industriestr. 25, 91710 Gunzenhausen, Germany | Data centre Falkenstein, Germany (EU) | Off-site storage of encrypted backups. Backups are encrypted (AES-256) on the data processor's servers before upload; Hetzner does not have the keys. |
B.2 Prior notice for the authorisation of sub-processors
The data processor has the data controller's general prior authorisation to engage sub-processors. The data processor informs the data controller in writing, by email to the account address, of any intended addition or replacement of a sub-processor at least 30 days in advance, so that the data controller can object before the sub-processor is engaged.
Appendix C: Instruction pertaining to the use of personal data
C.1 The subject of/instruction for the processing
The data processor processes personal data on behalf of the data controller only to provide the service described in A.1 and A.2, as set up by the data controller in its account (the domains added, the weekly status on or off).
C.2 Security of processing
Encryption in transit
- senderward.com is served over HTTPS only. Data is encrypted in transit (TLS) between users, our CDN and our servers, and our servers only accept connections from the CDN that authenticate with a client certificate.
- Calls to Amazon SES and Stripe go over HTTPS.
Access for users
- No passwords. Users sign in with a link sent to their email address. A link works once and for 15 minutes.
- Only SHA-256 hashes of sign-in links and session tokens are stored. The session cookie is HttpOnly, Secure and SameSite=Lax, and lasts 30 days or until sign-out.
- Forms for signed-in users carry a CSRF token tied to the session, and every form is protected by a same-origin check.
- Sign-up and sign-in are rate limited per IP address, network and email address, and protected by Cloudflare Turnstile.
- An account only sees its own domains. A domain can be verified in one account at a time, and only by a DNS record the domain's owner adds.
- Card data is entered at Stripe and never reaches our servers.
Access for the data processor's staff: administrative access is restricted to authorised personnel. Account deletion, data export and removal of a domain by the data processor are logged in an audit log (time, account ID and a fixed note, no email address or domain name), which is deleted after 3 years.
Infrastructure
- Servers are operated by NFI ApS in Denmark (EU).
- The database cannot be reached from the internet; only the application connects to it.
- Secrets (database password, API keys) are kept in a secret store, not in code or images. The Stripe key is a restricted key.
- Webhooks from Amazon SNS and Stripe are only accepted with a valid signature.
- Pages are sent with a strict Content-Security-Policy and Referrer-Policy "no-referrer".
Logging
- The app's logs contain no IP addresses and no email addresses: only internal IDs and, where an address must be referred to, a short keyed hash. Our proxy's access log is switched off.
- Rate limits store only a keyed hash with a daily key, deleted after at most 24 hours.
- Server logs are rotated automatically, and the oldest lines are deleted. There is no fixed time limit, so how far back the logs reach depends on how much is logged.
Backup: The database is backed up daily. Backups are encrypted (AES-256) before they leave our servers and stored in the EU, with an off-site copy in Germany (31 daily and 12 monthly versions, plus 10 daily snapshots). The off-site provider does not have the keys. Deleted data is gone from all backups after about 13 months.
Email: sent without tracking pixels or link rewriting. Addresses that hard-bounce or complain are suppressed and never mailed again.
A detailed description of our technical and organisational security measures is available to customers on request, under confidentiality.
C.3 Assistance to the data controller
The data processor assists by email to [email protected] with data subject requests and, where relevant, with data protection impact assessments. Reasonable assistance is free of charge. Manifestly unfounded, excessive or repeated requests may be charged at a price agreed in advance.
C.4 Storage period/erasure procedures
- When the data controller removes a domain, its check history, changes, alert state and DMARC reports are deleted at once.
- DMARC aggregate reports: the incoming mail in Amazon S3 is deleted after 7 days, and mail that is not an aggregate report as soon as it has been read. The report file is kept for 30 days and the rows extracted from it for 12 months. The record of a discarded mail (time, sender's domain, size, reason) is kept for 30 days. Deleted DMARC data is gone from all backups after about 13 months.
- Data is otherwise kept while the account exists.
- On request, the data processor deletes the account with all its domains, check history, changes, alert state, sessions, sign-in links and all mail to its address.
- An account with no plan and no sign-in for 12 months gets a warning email and is deleted in the same way 30 days later, unless it is signed in to before then.
- Sessions are deleted 30 days after they expire, sign-in links 24 hours after they were used or expired, and sent or failed mail 90 days after it was sent or failed.
- The suppression list is kept without a time limit, so that addresses that hard-bounced or complained are never mailed again. It holds only a keyed hash (HMAC with a dedicated secret key) of each address, never the address. Amazon SES keeps its own list of addresses that bounced or complained (see Appendix B).
- The audit log of deletions, exports and domain removals by the data processor (time, account ID and a fixed note) is deleted after 3 years.
- Logs: rotated automatically, and the oldest lines are deleted. There is no fixed time limit, so how far back the logs reach depends on how much is logged.
- Backups: monthly versions are kept for 12 months (the longest retention, at Hetzner), so deleted data is gone from all backups after about 13 months.
- Return of data: on request before deletion, the data processor provides the controller's domains, check history and DMARC reports (with the rows extracted from them) as JSON or CSV within 30 days.
C.5 Processing location
The app and database: servers operated by NFI ApS in Denmark (EU). Sub-processors: as in Appendix B.
C.6 Instruction on the transfer of personal data to third countries
Cloudflare and Google may process data in the USA, and AWS and Cloudflare have US parent companies. The transfer basis each provider states is in Appendix B: AWS (EU-U.S. Data Privacy Framework and Standard Contractual Clauses; data stays in eu-north-1), Cloudflare (EU-U.S. Data Privacy Framework, and Standard Contractual Clauses as a fallback) and Google (EU-U.S. Data Privacy Framework). mailbox.org and Hetzner process data in Germany only.
C.7 Procedures for the data controller's audits, including inspections
On request, once a year, the data processor provides a written statement on its compliance with these clauses, free of charge. On-site inspections only by prior agreement, with at least 30 days' notice, under confidentiality and at the data controller's cost.
C.8 Procedures for audits, including inspections, of the processing of personal data being performed by sub-processors
The data processor relies on its sub-processors' own audit reports and certifications (for example ISO 27001 or SOC 2) and their data processing agreements.
Appendix D: The parties' terms of agreement on other subjects
- Notification of a personal data breach: without undue delay, as in clause 9.
- Liability under these clauses follows the limitation in the terms of service, section 11.
- Assistance beyond the normal service is charged only by prior agreement.
Source of clauses 1 to 14: the Danish Data Protection Agency (Datatilsynet), Standard Contractual Clauses for the purposes of Article 28(3) of Regulation 2016/679 (GDPR), English version of January 2020, version 1.1 (corrected cross-references in Clauses 9.2 and 10.4), as published by the European Data Protection Board: dk_sa_standard_contractual_clauses_january_2020_en.docx (SHA-256 9bd1a42b42bb7d66370739e8b2cab0e6403a938372634858f9f523707dca3591).