This Data Processing Agreement ("DPA") forms part of the agreement between Althi Digital Services B.V., established at Bargelaan 200, 2333CW Leiden and registered with the Dutch Chamber of Commerce (KvK) under number 60860448, and its customers for Althi.work, the hosted business e-mail service. It sets out how Althi Digital Services B.V. processes personal data on behalf of the Customer, as required by Article 28 of the General Data Protection Regulation (EU) 2016/679 ("GDPR"). The Customer accepts this DPA electronically together with the Terms of Service, which meets the requirement that the contract is in writing (Article 28(9) GDPR). You can save and print it, and it is always available at https://althi.work/dpa.
1. Definitions
1.1 Capitalised terms that this DPA does not define have the meaning given in the Terms of Service for Althi.work ("Terms"), published at https://althi.work/terms, such as Account, Administrator, Agreement, Customer, Customer Console, Customer Data, Customer Domain, Mailbox, Privacy Statement, Service, Supplier, User, User Mailbox and Working Day.
1.2 Controller, processor, personal data, processing, data subject, personal data breach and supervisory authority have the meaning given in Article 4 of the GDPR.
1.3 Customer Personal Data: the personal data in Customer Data that Supplier processes on behalf of the Customer.
1.4 Sub-processor: another processor that Supplier engages to carry out processing activities on Customer Personal Data on behalf of the Customer.
1.5 Data Protection Law: the GDPR, the Dutch GDPR Implementation Act (Uitvoeringswet AVG) and the other laws of the European Union and its member states on the protection of personal data and the confidentiality of communications that apply to the processing.
1.6 EEA: the European Economic Area.
2. Roles and scope
2.1 For Customer Personal Data, the Customer is the controller and Supplier is the processor. If the Customer processes the data on behalf of another controller, Supplier is the Customer's sub-processor, and the Customer guarantees that it is authorised to give the instructions in this DPA.
2.2 Annex I describes the processing: its subject-matter and duration, its nature and purpose, the categories of data subjects and of personal data, and the retention periods.
2.3 This DPA does not apply to the processing that Supplier carries out for its own purposes as a controller, which the Privacy Statement describes: the processing of data about the Customer, its contact persons and Administrators for the conclusion and administration of the Agreement, billing, VAT checks and support; and the processing of data about the use of the Service, such as logs, sign-in records and records of changes, to secure the Service, to prevent and investigate abuse, to enforce the sending limits, to count the User Mailboxes for billing and to comply with legal obligations. Supplier does not use the content of messages for these purposes (clause 4.2).
2.4 The Customer is responsible for the lawfulness of the processing, including having a legal basis and informing data subjects, among them its Users. It also assesses whether the Service and the measures in Annex II are appropriate for the personal data that it processes with the Service (see Annex I, special categories of personal data).
2.5 Supplier's contact point for this DPA is support@althi.digital. Supplier sends notices under this DPA to the contact e-mail address of the Customer and, where appropriate, to its Administrators.
3. Instructions
3.1 Supplier processes Customer Personal Data only on documented instructions from the Customer, including with regard to transfers of personal data to a third country or an international organisation, unless Union or member state law to which Supplier is subject requires it to process the data. In that case Supplier informs the Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.
3.2 The Customer's documented instructions are: the Agreement, including this DPA; the settings that Administrators choose and the actions they take in the Customer Console; the use of the Service by Users, such as sending and receiving mail and setting up rules; and further instructions that the parties agree in writing. Supplier may refuse an instruction that goes beyond the Service, or agree with the Customer on the costs of carrying it out.
3.3 Supplier informs the Customer immediately if, in its opinion, an instruction infringes Data Protection Law, and may suspend carrying out that instruction until the Customer has confirmed or changed it.
4. Confidentiality
4.1 Supplier ensures that the persons it authorises to process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and that they have access to Customer Personal Data only to the extent needed for their tasks.
4.2 The content of communications and other Customer Data is processed automatically to provide the Service, for example to deliver, filter and secure mail. No person at Supplier reads or otherwise inspects that content, except in the cases described in clause 12.2 of the Terms: at the explicit request of the Customer or of the User concerned, or where the law or a binding order of a competent authority requires it. To investigate abuse and security incidents, Supplier relies on data about messages, the signals of its automated tools and the messages that a person who reports abuse submits to it (clause 12.3 of the Terms).
5. Security
5.1 Supplier implements the technical and organisational measures described in Annex II to ensure a level of security appropriate to the risk (Article 32 GDPR), taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing, and the risks of varying likelihood and severity for the rights and freedoms of natural persons.
5.2 Supplier may change these measures, provided that the overall level of security is not reduced.
5.3 The Customer is responsible for the security of what is under its control, such as the credentials of its Users and Administrators, their devices and apps, and the settings it chooses. Mail exchanged with other providers is encrypted in transit only if the other mail server supports it (Annex II). The Customer decides whether particularly sensitive data needs additional protection, such as end-to-end encryption.
6. Sub-processors
6.1 The Customer gives Supplier general written authorisation to engage Sub-processors, on the conditions of this clause 6.
6.2 At the date of this DPA, Supplier does not engage any Sub-processors. Annex III lists the Sub-processors, if any, and explains why the operator of a data centre in which a server of Supplier is located is not a Sub-processor.
6.3 Supplier informs the Customer of any intended addition or replacement of a Sub-processor at least 30 days in advance, by e-mail to the contact e-mail address of the Customer or in the Customer Console, and updates Annex III. The notice states the name and location of the Sub-processor and the processing it will carry out.
6.4 The Customer may object to the change in writing within 30 days of the notice, on reasonable grounds relating to data protection. The parties then discuss the objection in good faith. If they do not find a solution, the Customer may terminate the Agreement under clause 15.5 of the Terms, with effect from the date on which the change takes effect; if the discussion is still going on at that date, the Customer may still terminate the Agreement within 30 days after the discussion has ended. The new Sub-processor does not process Customer Personal Data before the period for objection has ended.
6.5 Supplier imposes on each Sub-processor, by a written contract, the same data protection obligations as those in this DPA, in particular sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing meets the requirements of the GDPR. Supplier remains fully liable to the Customer for the performance of the obligations of its Sub-processors.
7. Location and international transfers
7.1 Supplier stores and processes Customer Personal Data on its own physical server (bare metal), which only Supplier manages, in a data centre in Germany (EEA). Supplier stores the backups of that server, encrypted, on another server that it manages itself, in France (EEA) (clause 12.3).
7.2 Supplier does not transfer Customer Personal Data to a country outside the EEA or to an international organisation, except:
- (a) where Users send e-mail to, or otherwise exchange data with, recipients outside the EEA, which takes place on the instructions of the Customer; and
- (b) the limited data that independent third parties receive as part of the normal operation of the Service, as described in Annex III, part B.
7.3 Every transfer of Customer Personal Data outside the EEA must meet the conditions of Chapter V of the GDPR. The Customer is responsible for this as regards the e-mail that Users send to recipients outside the EEA (clause 7.2(a)). Apart from that e-mail, the data in clause 7.2(b) are limited to what Annex III, part B, describes, such as host names and the items that are looked up or checked, and normally do not relate to a natural person. Any other transfer of Customer Personal Data outside the EEA, including through a Sub-processor, takes place only after notice under clause 6.3 and only on the basis of an adequacy decision or the standard contractual clauses adopted by the European Commission.
8. Requests from data subjects
8.1 The Service lets the Customer handle most requests of data subjects itself: Administrators can create, change and delete Users and their Mailboxes in the Customer Console, and Users can view, export and delete their own messages, calendars and contacts.
8.2 Taking into account the nature of the processing, Supplier assists the Customer by appropriate technical and organisational measures, insofar as this is possible, in fulfilling its obligation to respond to requests for exercising the rights of data subjects laid down in Chapter III of the GDPR.
8.3 If Supplier receives a request from a data subject that concerns Customer Personal Data, it forwards the request to the Customer without undue delay and does not respond to it itself, other than to refer the data subject to the Customer, unless the Customer instructs otherwise.
8.4 Supplier may charge reasonable costs for assistance that takes substantial time and goes beyond the functions of the Service, after informing the Customer of the estimated costs in advance.
9. Assistance with security, impact assessments and prior consultation
9.1 Taking into account the nature of the processing and the information available to it, Supplier assists the Customer in ensuring compliance with the obligations of Articles 32 to 36 of the GDPR: the security of processing, the notification of personal data breaches to the supervisory authority and their communication to data subjects, data protection impact assessments and prior consultation of the supervisory authority. For this purpose, Supplier provides the information in Annexes I and II and answers reasonable additional questions.
10. Personal data breaches
10.1 Supplier notifies the Customer of a personal data breach concerning Customer Personal Data without undue delay, and in any case within 48 hours after becoming aware of it, by e-mail to the contact e-mail address of the Customer and, where appropriate, to its Administrators.
10.2 The notification contains, to the extent available, the information that the Customer needs under Article 33(3) of the GDPR:
- (a) the nature of the breach, including, where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
- (b) the name and contact details of the contact point at Supplier where more information can be obtained;
- (c) the likely consequences of the breach; and
- (d) the measures taken or proposed by Supplier to address the breach, including, where appropriate, measures to mitigate its possible adverse effects.
Where it is not possible to provide all information at the same time, Supplier provides it in phases without undue further delay.
10.3 Supplier takes the measures that can reasonably be expected of it to contain the breach and to limit its consequences, keeps the Customer informed and documents the breach. Supplier does not notify the supervisory authority or data subjects of a breach concerning Customer Personal Data on behalf of the Customer, unless the Customer instructs it to. Where the law requires Supplier itself to notify a breach or incident, in particular as a provider of a publicly available electronic communications service (article 11.3a of the Dutch Telecommunications Act), Supplier does so and informs the Customer of the notification, where possible in advance.
10.4 A notification is not an acknowledgement of fault or liability.
11. Information and audits
11.1 Supplier makes available to the Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR, including this DPA, the description of the measures in Annex II and answers to reasonable questions.
11.2 Supplier allows for and contributes to audits, including inspections, conducted by the Customer or by an independent auditor mandated by the Customer, on the following conditions:
- (a) the Customer gives at least 30 days' written notice, unless the audit follows a personal data breach or a request of a supervisory authority;
- (b) an audit takes place at most once every 12 months, except in the cases mentioned in (a);
- (c) the auditor is bound by confidentiality and is not a competitor of Supplier;
- (d) the audit takes place on Working Days during office hours, without unreasonably disrupting Supplier's operations, and gives no access to data of other customers or to information whose disclosure would endanger the security of the Service; and
- (e) the Customer bears its own costs and reimburses Supplier's reasonable costs, unless the audit shows that Supplier has materially breached this DPA.
Supplier remedies the shortcomings found within a reasonable period.
11.3 Supplier cooperates with audits and inspections of a competent supervisory authority.
11.4 Supplier keeps a record of the processing activities it carries out on behalf of the Customer (Article 30(2) GDPR).
12. Return and deletion
12.1 While the Account is active, the Customer can export Customer Data itself, as described in clause 17 of the Terms. While the Account is suspended, including after the end of the Agreement, Supplier restores access to the Mailboxes free of charge at the Customer's request, for at least 30 calendar days, so that the Customer can retrieve its data (clause 17.3 of the Terms).
12.2 When the Agreement ends, Supplier suspends the Account, and it deletes the Account, its Mailboxes and the Customer Personal Data 183 days (about six months) after the start of the suspension, or later where clause 17.3 of the Terms requires it, as described in clauses 16 and 17.3 of the Terms. By accepting this DPA, the Customer instructs Supplier to keep Customer Personal Data during that period, so that the Customer can resume the Service or retrieve its data. At the Customer's request, Supplier deletes the data earlier, within 30 days of the request. Copies in backups are deleted as described in clause 12.3.
12.3 Supplier makes regular backups of its server, which also contain Customer Personal Data, and stores them, encrypted, on another server that it manages itself, in France (EEA). Each backup is kept for 365 days and is then overwritten or deleted, so Customer Personal Data that has been deleted from the Service can remain in backup copies for at most 365 days after its deletion. During that time, the data is put beyond use: Supplier uses backups only to restore the Service after an incident (disaster recovery), never for any other purpose. If Supplier restores a backup, it deletes again the Customer Personal Data that had been deleted.
12.4 Supplier deletes the data listed in Annex I within the periods stated there, also where such a period ends after the deletion of the Account.
12.5 This clause 12 does not apply to data that Supplier processes as a controller (clause 2.3) or must keep under Union or member state law. At the Customer's request, Supplier confirms the deletion in writing.
13. Requests from authorities
13.1 Supplier discloses Customer Personal Data to an authority only if Union or member state law requires it to do so. Supplier checks whether the request is lawful, challenges a request that it considers unlawful where there are reasonable grounds to do so, and discloses no more data than the request requires.
13.2 Supplier informs the Customer of a request without delay, unless the law prohibits this. Where possible, Supplier refers the authority to the Customer.
13.3 Supplier does not comply with a request of an authority of a country outside the EEA, unless the request is recognised or made enforceable under an international agreement, such as a mutual legal assistance treaty, or under Union or member state law.
13.4 Supplier also applies this clause 13 to Customer Data that is not personal data.
14. Liability
14.1 The liability of the parties under this DPA is subject to clause 19 of the Terms. The limits of clause 19 of the Terms apply to the Terms and this DPA together.
14.2 This does not affect the liability of the parties towards data subjects under Article 82 of the GDPR. A party that has paid compensation to a data subject for damage for which the other party is responsible may claim back from the other party the part of the compensation that corresponds to that responsibility (Article 82(5) GDPR), within the limits of clause 19 of the Terms insofar as the law allows.
14.3 Fines imposed by a supervisory authority are borne by the party on which they are imposed.
15. Term, precedence and changes
15.1 This DPA applies for as long as the Agreement applies and, after its end, for as long as Supplier processes Customer Personal Data.
15.2 In case of conflict, this DPA prevails over the Terms as regards the processing of personal data. In all other respects the Terms apply, including the provisions on governing law and the competent court (clause 24 of the Terms).
15.3 Supplier may change this DPA under clause 22 of the Terms, and only in accordance with the GDPR.
Annex I – Description of the processing
Subject-matter and duration
The hosting of business e-mail, calendars, contacts and tasks for the Customer's organisation, and the related services described in clause 6 of the Terms. The processing lasts for the duration of the Agreement and until the deletion described in clause 12.
Nature and purpose
Supplier processes Customer Personal Data only to provide the Service to the Customer. This includes:
- storing Mailboxes and making them available to Users through the supported apps and webmail;
- receiving incoming mail, filtering it for spam and other unwanted mail, and delivering it to Mailboxes;
- sending outgoing mail on the instructions of Users, including the delayed-sending period, footers, DKIM signatures and the sending limits;
- managing Users, Mailboxes, Customer Domains and settings through the Customer Console;
- obtaining TLS certificates for the autodiscover and autoconfig host names of Customer Domains;
- keeping technical logs to operate and secure the Service;
- making backups, used only to restore the Service after an incident (disaster recovery);
- support at the Customer's request; and
- deleting data in accordance with this DPA.
Categories of data subjects
- Users, such as the Customer's employees and other persons to whom the Customer gives a Mailbox or access to the Customer Console;
- persons who exchange e-mail or calendar items with Users; and
- persons whose details are stored in Mailboxes, address books and calendars, or who are mentioned in messages and attachments.
Categories of personal data
- Account and directory data of Users: name, e-mail addresses and aliases, user name, password (stored by the mailbox software), job title, company, telephone numbers, type of Mailbox, settings and rules.
- Content: messages and attachments, calendar items, contacts, tasks and notes.
- Data about messages: sender and recipients, subject, date and time, size, message identifiers, delivery status, and the IP addresses of the mail servers that deliver mail to the Service.
- Connection data: the IP addresses of Users' devices, the host names and paths they request, and information about devices that connect through Exchange ActiveSync, such as a device identifier and device type.
- Records of messages in the delayed-sending period, including which Administrator cancelled or released a message.
- Reports from other mail providers about mail sent in the name of the Customer Domains (DMARC aggregate reports), if the Customer publishes the DMARC record with the reporting address that Supplier suggests.
Special categories of personal data
The Service is not designed for a specific type of data; the Customer decides what Users store and send. Messages and attachments may therefore contain special categories of personal data (Article 9 GDPR) or personal data relating to criminal convictions and offences (Article 10 GDPR). Supplier applies the same measures (Annex II) to all Customer Personal Data. The Customer assesses whether these measures are appropriate for the data that it processes with the Service.
Retention
| Data | Retention |
|---|---|
| Mailbox content and settings, and Users' account and directory data in the mailbox software | Until Users or Administrators delete them, and at the latest when the Account is deleted (clause 12) |
| Copies of outgoing messages during the delayed-sending period | Until the message has been sent, or cancelled and returned to its sender with a notice: the period set by the Customer (60 seconds by default, at most 24 hours), plus up to 24 hours of retries if delivery fails temporarily; in any case at most 30 days |
| Copies of outgoing messages that could not be delivered, or whose cancellation notice could not be delivered | At most 7 days, to investigate the failure |
| Records of outgoing messages (sender, recipients, subject, size, times, status and message identifier) | 30 days after the message reached its final status (sent, cancelled or failed) |
| Footer directory data (name, job title, company and telephone numbers) | Updated when the User's details change; deleted when the Account is deleted |
| Counters for the sending limits (sender address and number of recipients) | 24 hours |
| Messages in the queue of the mail transfer agent | Until delivered; a message that cannot be delivered is returned to the sender after 5 days |
| Cache of recently verified recipient addresses | Up to 31 days after the last check |
| Working data of the spam filter: greylisting records and records that recognise replies to sent messages (hashed message identifiers and addresses, and the addresses of Users who received replies), and a history of the last 200 messages checked, with their sender, recipients and subject | Greylisting and reply records, including the short list of addresses that most often received replies: at most 1 day; the history keeps only the 200 most recent checks and is removed 1 day after the last check. The spam filter is not trained on Customer Data |
| Technical logs of the components of the Service (such as the mail transfer agents, the spam filter, the web servers and the mailbox software) | Log files that are rotated by size: when a log reaches its maximum size, its oldest entries are removed automatically, so how long an entry is kept depends on the amount of traffic |
| DMARC aggregate reports | 90 days after receipt |
| Backups of Supplier's server, with the data above as it was at the time of the backup | 365 days; each backup is then overwritten or deleted. Deleted data can remain in backup copies for at most 365 days after its deletion, put beyond use (clause 12.3) |
Some of this data, such as technical logs, sign-in records and the counters for the sending limits, is also processed by Supplier as a controller for its own purposes (clause 2.3). Records that Supplier keeps as a controller, such as sign-in records, the audit log of the Customer Console and the records of errors and security events, and their retention periods, are described in the Privacy Statement.
Location
Germany (EEA), on Supplier's own server (clause 7). The backups of that server are stored on another server that Supplier manages itself, in France (EEA).
Annex II – Technical and organisational measures
These are the measures in place at the date of this DPA.
Hosting and physical security
- Customer Data is stored and processed only on Supplier's own physical server (bare metal) in a data centre in Germany (EEA), and in the backups of that server, which Supplier stores on another server that it manages itself, in France (EEA) (see Availability and recovery). Only Supplier manages these servers and the software on them.
- All data on the disks of the server in Germany is encrypted at rest (full-disk encryption), and the backups are stored encrypted. The keys are held by Supplier.
- The operator of a data centre in which a server of Supplier is located provides space, power and network connectivity. It has no access to the server and cannot read the data stored on it.
Encryption in transit
- Webmail, Outlook (MAPI over HTTP and Exchange Web Services), Exchange ActiveSync, autodiscover, the Website and the Customer Console are available only over HTTPS; plain HTTP requests are redirected to HTTPS. The Website and the Customer Console instruct browsers to use only HTTPS (HSTS).
- Mail apps can use IMAP and SMTP only with TLS from the start of the connection (ports 993 and 465).
- The TLS certificates of webmail, autodiscover, the mail apps' IMAP and SMTP host names, the Website and the Customer Console are issued by Let's Encrypt and renewed automatically. For mail from other mail servers (port 25), the Service offers TLS with a self-signed certificate, as is usual for this opportunistic encryption.
- Mail exchanged with other mail servers is encrypted with TLS whenever the other server supports it. Mail to and from servers that do not support TLS is transmitted unencrypted, as is usual on the internet.
- The components of the Service communicate over internal networks on the same server that cannot be reached from the internet. Their internal programming interfaces require a secret access token or password; the internal mail connections are accepted only from the addresses of the components that use them, and the spam filter and its database accept connections only from the internal network.
Network security
- Only the ports that the Service needs (25, 80, 443, 465 and 993) and the port for Supplier's own remote administration are open to the internet; a host firewall blocks all other incoming connections.
- Databases, internal interfaces and the spam filter cannot be reached from the internet.
- The public Website runs on a separate network that it shares only with the reverse proxy and the Customer Console; it cannot reach the databases, the mail servers, the spam filter or the component that controls the containers.
- Supplier's own administration console can be reached only from IP addresses that Supplier has approved.
- Public interfaces are protected by rate limits, such as limits on sign-in attempts, on signups and on requests per IP address.
Access control and authentication
- Administrators of the Customer Console, and Supplier's own administrators, sign in with a password and a time-based one-time code (two-factor authentication), which they must set up at their first sign-in.
- Administrators' passwords have at least 12 characters and are stored only as salted hashes (scrypt). Passwords for Mailboxes that are set in the Customer Console have at least 10 characters; the Customer Console does not store them, but passes them to the mailbox software.
- Two-factor secrets are stored encrypted (AES-256-GCM). Session tokens and e-mail verification tokens are stored only as SHA-256 hashes.
- After 5 failed sign-in attempts for an account, or 10 from one IP address, within 15 minutes, sign-in is blocked for 15 minutes.
- Sessions of the Customer Console end after 30 minutes of inactivity and at the latest after 12 hours. The session cookies of the Customer Console and the Website cannot be read by scripts and are not sent with requests from other websites. The Customer Console and the Website are protected against cross-site request forgery and use a content security policy that allows scripts only from their own address.
- Roles with limited rights are available, such as a helpdesk role that can only read and set new Mailbox passwords. In the Customer Console, every request is limited by the data layer to the data of the Customer's own Account.
- Every change made in the Customer Console and in Supplier's administration console is recorded in an audit log: who made which change, when, and from which IP address.
- The server is administered only by Supplier. Supplier's personnel have access to Customer Personal Data only to the extent needed for their tasks, and do not read the content of messages except in the cases of clause 4.2.
Separation of customers
- Each Account is a separate organisation in the mailbox software, with its own Customer Domains, Users and Administrators. Accounts share the same server and are separated logically.
- A domain can be used as a Customer Domain only after the Customer has proven control of it through DNS, and only one Account can verify the same domain.
- Users can send mail through SMTP only with sender addresses of their own Mailbox.
- Mail from the internet that uses a domain hosted in the Service as the sender address in its envelope is refused, so that it cannot be passed off as mail from an Account.
Mail security
- Incoming mail is filtered for spam with Rspamd (clause 10.2 of the Terms). Outgoing mail is not checked with outside block lists or reputation services.
- Mail for addresses that do not exist is refused during delivery, so that no bounce messages are sent to forged senders.
- The mail servers relay mail only for the components of the Service, and automated tests check that they cannot be used as an open relay.
- Outgoing mail from Customer Domains is signed with DKIM, with a separate 2,048-bit RSA key for each domain.
- Sending limits per sender address and per Account limit the damage that a compromised Mailbox can do; the Users of a suspended Account cannot send mail.
Logging, monitoring and pseudonymisation
- Errors and security-relevant events that the components report in their container logs, or send to the Customer Console, are collected centrally. Automated checks of containers, disk space, the mail queue, certificates and DNS run continuously (every minute to every hour) and alert Supplier's administrators.
- The logs of Supplier's own components and the central records of events never contain passwords, access tokens, message bodies or private keys. In the records of events, e-mail addresses are replaced by their domain and a short hash of the part before the @. These events are deleted after 90 days, and their grouped summaries 90 days after they have been resolved.
- Technical logs are kept in log files that are rotated by size (Annex I).
Availability and recovery
- The components of the Service run in containers that are monitored with health checks and are restarted automatically when they stop.
- Mail that cannot be delivered immediately is queued and retried.
- Supplier makes regular backups of the server as a whole (server-level backups) and stores them, encrypted, on another server that it manages itself, in France (EEA). Each backup is kept for 365 days and is then overwritten or deleted. Backups are used only to restore the Service after an incident (disaster recovery), never for any other purpose (clause 12.3).
Deletion
- When a Mailbox, a Customer Domain or an Account is deleted, the mailbox software is instructed to delete the related files as well.
- Annex I and clause 12 describe the retention periods and deletion.
Software and change management
- Third-party container images, the build recipe of the mailbox software and the libraries of Supplier's own components are pinned to specific versions; operating-system and mailbox-software packages are installed in the version that is current when Supplier builds an image. Supplier updates and rebuilds them deliberately.
- Supplier's own components run without administrator rights inside their containers. The public Website runs without any operating-system privileges. The component that controls the other containers can only perform a fixed list of actions with validated parameters.
- The software of the Service includes automated tests of security-relevant behaviour, such as the relay rules of the mail servers and the checks on sender addresses.
Organisation
- Persons who have access to Customer Personal Data are bound to confidentiality (clause 4).
- Supplier handles personal data breaches as described in clause 10.
Annex III – Sub-processors and other recipients
Part A – Sub-processors
At the date of this DPA, Supplier does not engage any Sub-processors. The operator of a data centre in which a server of Supplier is located is not a Sub-processor: it only provides space, power and network connectivity for that server, which only Supplier manages, and it has no access to the server and cannot read the data on it, because all of that data is encrypted with keys held by Supplier.
Supplier informs the Customer of any intended Sub-processor under clause 6 and lists it here.
Part B – Independent third parties that receive limited data
The following parties are not Sub-processors: they are independent third parties that do not process Customer Personal Data on behalf of Supplier, but receive limited data because of how e-mail and the internet work, or because the spam filter consults them about incoming mail.
| Recipient | Data | Purpose | Location |
|---|---|---|---|
| Mail servers of other providers | The messages that Users send, with their content and the data about them | Delivering mail on the instructions of Users | Worldwide, depending on the recipient |
| Operators of DNS servers | The domain names that the Service looks up, such as the domain of a recipient of an outgoing message (to find its mail server) and the domain of the sender of an incoming message (to check SPF, DKIM and DMARC). Supplier's own DNS resolver, in the same data centre, sends these lookups to the DNS servers that are responsible for each domain | Delivering mail, checking sender authentication and checking Customer Domains | Worldwide |
| Operators of the DNS-based block lists and reputation services that the spam filter consults, such as Spamhaus, SURBL, URIBL, MSBL and the Rspamd project | For incoming messages only: in clear, the IP address of the server that delivers a message and of earlier servers named in its headers, and domain names that appear in the message or its headers, such as those of links and e-mail addresses (for example to Spamhaus, SURBL and URIBL); hashed e-mail addresses and hashed links (for example to MSBL, rspamd.com and phishtank.rspamd.com); and checksums of the text and attachments of a message (to the fuzzy storage of rspamd.com). Never a readable copy of a message | Filtering incoming mail for spam and phishing | Worldwide |
| Cloudflare, Inc. (public DNS resolver), only when Supplier's own DNS resolver is unavailable or cannot resolve a name | The DNS lookups described in the two previous rows, which then pass through Cloudflare's resolver; never the content of messages | Delivering mail, checking sender authentication, filtering spam and checking Customer Domains | United States and other countries |
| Let's Encrypt (Internet Security Research Group, United States) | The host names autodiscover and autoconfig of Customer Domains and, where no wildcard certificate is used, the Customer's sign-in host name under althi.work | Issuing TLS certificates for these host names; like all publicly trusted certificates, they are published in public Certificate Transparency logs | United States |
Supplier's processing for its own purposes (clause 2.3), such as payments through Stripe and VAT checks through VIES, is described in the Privacy Statement.