Skip to content
work
Menu
Pricing Log in Start free trial
Home›Data Processing Agreement›Version 1.2

Data Processing Agreement

Version 1.2 · effective 23 October 2026

Previous versions

Contents

  1. 1. Definitions
  2. 2. Roles and scope
  3. 3. Instructions
  4. 4. Confidentiality
  5. 5. Security
  6. 6. Sub-processors
  7. 7. Location and international transfers
  8. 8. Requests from data subjects
  9. 9. Assistance with security, impact assessments and prior consultation
  10. 10. Personal data breaches
  11. 11. Information and audits
  12. 12. Return and deletion
  13. 13. Requests from authorities
  14. 14. Liability
  15. 15. Term, precedence and changes
  16. Annex I – Description of the processing
  17. Annex II – Technical and organisational measures
  18. Annex III – Sub-processors and other recipients

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, records of changes and records of the consent of Users to notifications, 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, such as creating Mailboxes and giving rights to them, converting Mailboxes, setting the rules for signatures and disclaimers, uploading and exporting S/MIME keys, ordering the remote wipe of a device, confirming DNS changes at the Customer's DNS provider, connecting a Microsoft 365 organisation and choosing, starting and finishing a migration from it, and the setting for the notifications of the webmail (clause 7.2(c)); the use of the Service by Users, such as sending and receiving mail, setting up rules and turning on notifications on a device; 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; to add signatures, banners, disclaimers, DKIM signatures and S/MIME signatures; to show messages, previews of attachments and search results in the webmail; to copy mail from another provider at the Customer's request; and to produce the notifications that a User turned on. 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, including apps that reach the Service through the cloud service of their maker with the User's password (clause 7.2(f)), the settings it chooses, and the access data that its Administrators create for its DNS provider, with its scope and its revocation (clause 11.8 of the Terms). 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. S/MIME with keys that the Service holds (clause 11.10 of the Terms) is not end-to-end encryption; where the Service holds a key that can decrypt, clause 13 applies to it.

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 engages one Sub-processor, Cloudflare, Inc., only to publish the public DKIM keys of Customer Domains in Supplier's own DNS zone, as described in Annex III, part A. Annex III lists the Sub-processors 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, data protection obligations that offer at least the same level of protection 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 Customer Personal Data only on its own physical server (bare metal), which only Supplier manages, in a data centre in Germany (EEA), where it also keeps the copies of each instance of the mailbox software described in clause 12.3, and in the backups of that server, which Supplier stores, encrypted, on another server that it manages itself, in France (EEA) (clause 12.3). In addition, Supplier publishes the public DKIM keys of Customer Domains in its own DNS zone at its Sub-processor (Annex III, part A). Annex III lists the parties that receive data from the Service, such as the mail servers to which Users send mail.

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;
  • (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;
  • (c) the data that the push service chosen by a User's browser receives to deliver the notifications of the webmail that the User turned on for a device, as described in Annex III, part C: the device's push address, and the time, size and permitted lifetime of each notification. The notifications are encrypted for the device before they leave Supplier's servers, so the push service cannot read them. Users can turn on these notifications only while the Customer allows them in the Customer Console, which it does unless an Administrator turns them off;
  • (d) the data that the Service exchanges, on the instructions of the Customer, with providers that the Customer has chosen itself, as described in Annex III, part D: its DNS provider, where an Administrator uses the automatic DNS setup, and Microsoft, where an Administrator copies data from Microsoft 365;
  • (e) the DKIM records that Supplier's Sub-processor publishes (Annex III, part A); and
  • (f) the data that apps which the Customer's Users choose receive through the cloud service of their maker, such as Outlook for iOS and Android and the new Outlook for Windows, which connect to the Service from Microsoft's servers with the User's password and keep copies of the mail there (clause 11.6 of the Terms; Annex III, part D).

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)), as regards its choice of the providers in clause 7.2(d) and of their location, and as regards the apps in clause 7.2(f), which the Customer decides its Users may use. 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. The data in clause 7.2(c) do relate to the User of the device; they are transferred to each push service on the basis that Annex III, part C, names for it. The DKIM records in clause 7.2(e) are transferred on the basis that Annex III, part A, names. 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, and, where the Account has the webmail of the Service (clause 6.7 of the Terms), can see and end their sessions in it.

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, including the Account's instance of its own of the mailbox software, its records of migrations and its S/MIME keys, 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, and the copies on the same server, are deleted as described in clause 12.3. The records that Annex I lists as remaining after the deletion are deleted as stated there.

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. In addition, the Service keeps, on the same server in Germany, the two most recent nightly copies of the data of each instance of the mailbox software, to restore that instance quickly after a failure; the copies of an instance that has been removed, such as the instance of its own of a deleted Account, are kept until they are 365 days old and are then deleted. Customer Personal Data that has been deleted from the Service can therefore remain in backup copies, and in these copies, for at most 365 days after its deletion. During that time, the data is put beyond use: Supplier uses the backups and these copies only to restore the Service after an incident (disaster recovery), never for any other purpose. If Supplier restores a backup or such a copy, 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.

13.5 This clause 13 also applies to a request for the S/MIME private keys that Supplier holds for the Customer's Mailboxes, or for the decryption of mail with them (clause 11.10 of the Terms).

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 the webmail; the webmail shows messages, previews of attachments and search results without keeping copies of them, apart from what a User is writing (see Retention);
  • providing an address book of the Account's Users and shared mailboxes to its Users, suggestions from the recipients that a User recently wrote to, and the free/busy times of the Account's Users to their colleagues;
  • receiving incoming mail, filtering it for spam and other unwanted mail, and delivering it to Mailboxes, or, for a Customer Domain that is not live yet (clause 6.8 of the Terms), to the mail servers that its MX records name;
  • sending outgoing mail on the instructions of Users, including the delayed-sending period, the signatures, banners and disclaimers with their images that the Customer's rules add, footers, DKIM signatures, S/MIME signatures and the sending limits;
  • holding the S/MIME certificates and private keys that Administrators upload for Mailboxes, signing outgoing mail with them, and exporting them at an Administrator's request;
  • managing Users, Mailboxes, their addresses and rights, Customer Domains and settings through the Customer Console, including the list of mobile devices of a Mailbox and their remote wipe at an Administrator's request;
  • checking the DNS records of Customer Domains at their own name servers and, at an Administrator's request, making DNS changes for Customer Domains at the Customer's DNS provider;
  • publishing the public DKIM keys of Customer Domains in Supplier's own DNS zone;
  • obtaining TLS certificates for the autodiscover and autoconfig host names of Customer Domains, once those host names point to the Service, which the Service checks at the domain's own name servers;
  • copying the Customer's mail, calendars and contacts from Microsoft 365 on the Customer's instruction, with read-only access that the Customer grants in its own organisation, and creating the Mailboxes for them and sending invitations to their Users;
  • sending notifications of new mail, reminders of appointments and tasks, and a daily overview of overdue tasks to the devices on which a User turned them on, at that User's request; the notifications are produced and encrypted automatically on the server that holds the Mailbox, and delivered by the push service of the User's browser (Annex III, part C);
  • moving the Account between instances of the mailbox software on the same server, and deleting the old copy after the move, or, if a move fails after the switch to the new instance, keeping the old copy, frozen and unused, until Supplier has resolved the failure (see Retention);
  • keeping technical logs to operate and secure the Service;
  • making backups and the copies of clause 12.3, 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;
  • persons whose details are stored in Mailboxes, address books and calendars, who are mentioned in messages and attachments, or who are shown in the images of signatures; and
  • the users and guests of a Microsoft 365 organisation that the Customer connects for copying, including those whose mailboxes are not copied.

Categories of personal data

  • Account and directory data of Users: name, e-mail addresses and aliases, user name, password (stored as a hash by the mailbox software, and held, sealed, by the webmail for the life of a webmail session: Annex II), job title, department, company, telephone numbers, website and the custom fields for signatures, type of Mailbox, rights to other Mailboxes, settings and rules, and the recently used recipients that the webmail keeps in the Mailbox's settings.
  • 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, information about devices that connect through Exchange ActiveSync, such as a device identifier, type, model, operating system and name, the times of their first and last connection and the status of a remote wipe, and, for sessions of the webmail, the browser, operating system and time zone.
  • Records of messages in the delayed-sending period, including which Administrator cancelled or released a message.
  • Data of signatures, banners and disclaimers: the templates, the rules (which can name Mailboxes, departments and domains), the groups (with the addresses of their Mailboxes), the company details, and the images, which can show a person.
  • S/MIME data: certificates (with the name and e-mail address in them, the serial number and the validity), the private keys (sealed), and the number of signatures per key and day.
  • Domain and DNS data: the names of Customer Domains, which can name a natural person; the DNS records that the Service checks or changes, with their values; and the access data for the Customer's DNS provider that an Administrator enters for a change, where it relates to a natural person.
  • Migration data: the directory data of a connected Microsoft 365 organisation (names, e-mail addresses, user principal names, account and licence status, and type of user), the names, item counts and sizes of folders, the identifiers of copied items, the mapping to Mailboxes and the invitations.
  • Notification data: for each device on which a User turned on notifications, its push address (stored encrypted), the device's public keys, the type of browser and operating system, the User's choices for that device (what it is notified of, and whether the sender and subject and the titles and places of appointments and tasks are shown), its language and time zone, and the times of its last sign-in and last notification; and, to limit how many new push addresses are served an hour, a keyed hash of the push address with the time of its last notification.
  • Reports from other mail providers about mail sent in the name of the Customer Domains (DMARC aggregate reports), if the Customer publishes, or lets the Service publish, 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). Messages and folders that Users delete for good (for example by emptying Deleted Items) remain recoverable for 30 days after the deletion and are then removed, at the latest 32 days after it; items in Deleted Items stay until a User deletes them or empties that folder; what a User deletes permanently in the webmail is removed at once
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)
Directory data for signatures and footers (name, job title, department, company, telephone numbers, website and custom fields) Updated when the User's details change; deleted when the Mailbox is deleted or its Customer Domain is removed, and at the latest when the Account is deleted
Templates, rules, groups, settings and company details of signatures, banners and disclaimers Until an Administrator changes or removes them, and at the latest when the Account is deleted
Images of signatures, banners and disclaimers 90 days after no template uses them any more, and at the latest when the Account is deleted
Statistics of signatures (counts per Account and day, without addresses) 90 days
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
Addresses removed from the Account's Mailboxes (an alias removed, a Mailbox deleted, a Customer Domain removed, the Account deleted), with the time and the Account Refused by the receiving mail server for 32 days after the removal, then forgotten
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
Sessions of the webmail: the User's address, password, name and language, sealed (Annex II), with the IP address, browser, time zone and times Until the User signs out; a session ends after 12 hours without use and at the latest after 7 days; a session that was ended by the User, an Administrator or the Service is kept 1 more day, so that the browser can show why. Not in backups
Attachments and images that a User uploads in the webmail while writing a message (the file, its name, size, type and checksum) Until the message is sent, the draft is saved and closed, the attachment is removed or the session ends, and at most 24 hours. Not in backups
Temporary copy of a message while the webmail saves or sends it While the request runs, and at most 1 hour. Not in backups
Search results of the webmail over all folders (subject, sender and preview of the hits) In memory only, until 5 minutes after the search ended
S/MIME certificates and private keys While the Mailbox has them. A replaced key that can only sign is destroyed at once; a replaced key that can also decrypt is kept so that it can be exported, until it is removed or its Mailbox or the Account is deleted. The keys of a deleted Mailbox are destroyed 30 days after the deletion, and all keys of the Account when the Account is deleted. When a key is destroyed, its certificate, the certificate chain, the e-mail address and the counts of its signatures are deleted with it; only the bare record of the destruction remains (see below)
Private DKIM keys of the Service for a Customer Domain, and the domain's entry in the list of domains that the mail server signs for While the Customer Domain exists, also a key of the domain that has been replaced. Destroyed when the Customer Domain is removed or the Account is deleted; a domain that is added again, to any Account, gets a new key
Results of the DNS checks of a Customer Domain (its name servers and their answers, the MX hosts found, and whether its mail and its autodiscover and autoconfig host names point to the Service) Until the next check, and at the latest until the Customer Domain is removed
Claims of domains that are not verified, with their verification token and the result of the last check Until an Administrator removes the claim or the Account is deleted, and at the latest 90 days after the claim was added
The MX host name of a Customer Domain As long as the Customer Domain exists
Access data for a DNS provider Not stored: used only in the requests of one setup session, for the changes that the Administrator confirms; never in logs or backups
Records of automatic DNS changes (the record values before and after, the provider, the step, the Administrator who confirmed it, and the times) 2 years after the change, and earlier when the Customer Domain or the Account is deleted. The same changes are also recorded in the audit log of the Customer Console (Privacy Statement)
Public DKIM keys of Customer Domains in Supplier's DNS zone While the Customer Domain exists; a previous key until 7 days after it was replaced; removed 7 days after the Customer Domain is deleted
Copies of items being copied from Microsoft 365, between download and import Until they are imported, and at most 24 hours. Not in backups
Lists of the users, mailboxes and folders of a connected Microsoft 365 organisation (discoveries) 30 days after the discovery finished
Details of a migration (the mapping of mailboxes, folder names, item identifiers, sizes, errors and its log) 30 days after the migration ended (finished, cancelled or failed)
Summary report of a migration (counts per mailbox and folder, folder paths and target addresses, without a list of items) 90 days after the migration ended
Plans of a migration (the mapping, addresses and rights) and its invitations 30 days after the migration ended; a plan that never ran, 30 days after its last change. Of an invitation link, only a hash is stored
Notification data of a device Until the User turns notifications off on that device, signs out on it, removes it or ends its session in the webmail's list of devices, and at the latest 90 days after the User's last sign-in on that device; deleted earlier when the push service reports the device gone, when the Mailbox or the Account is deleted, and paused when the password changes, the Mailbox is disabled or the Account is suspended
The device's entry in the Mailbox (its public keys, choices, language and time zone) It is part of the Mailbox and goes with it. The Service stops acting on it as soon as the device stops (a turn-off, a sign-out, a removal, a device the push service reports gone, or at the latest 90 days after the User's last sign-in on it), and removes it at the next change the webmail writes for that Mailbox's notifications; a Mailbox whose User never turns notifications on again keeps stale entries, without effect, until the Mailbox is deleted
The keyed hash of a push address and the time of its last notification 90 days after that notification; it names no Customer, User or address
Sender and subject, or the title and place of an appointment or task, in a notification, where the User chose to see them Only in the encrypted notification itself; shown for at most 7 days after the User's last sign-in on that device; a notification of new mail with them waits at the push service for at most 15 minutes, a reminder or the overview of overdue tasks for at most 1 hour
Technical logs of the components of the Service (such as the mail transfer agents, the spam filter, the web servers, the webmail and the mailbox software). The access log of the reverse proxy records for each request the IP address, the host name, the time and the result, not its path or query; the access log of the web server of the mailbox software records the path with its query and the user name of each request that signs in with a password, which is the address of the Mailbox; for some phones and tablets that connect through Exchange ActiveSync, the query contains that address as well 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, and at the latest after 90 days
DMARC aggregate reports 90 days after receipt
Old copy of the Account in its previous instance, after a move that failed after the switch to the new instance Frozen and unused until Supplier has resolved the failure, and deleted at the latest 30 days after the failure
Copies of each instance of the mailbox software on the same server (clause 12.3) The two most recent nightly copies of each instance; the copies of an instance that has been removed until they are 365 days old
Backups of Supplier's server, with the data above as it was at the time of the backup, except the working data of the webmail, the copies of items being copied from Microsoft 365 and the copies of clause 12.3 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)

Records that remain after a deletion. When the Mailbox, the Customer Domain or the Account they belong to is deleted, then, apart from the data whose period in the table above runs on after the deletion (such as removed addresses, which are refused for 32 days, and public DKIM keys, which stay published for 7 days) and apart from backups and the copies of clause 12.3, only the following records remain:

  • the bare record of a destroyed S/MIME key in the component that held it: the identifiers of the key, the Account and the Mailbox, the state of the key and its dates, without the certificate, the e-mail address or the private key. Supplier uses it only as evidence that the key was destroyed, and deletes it 2 years after the destruction;
  • the entry of the deletion in Supplier's journal of deletions: its time, what was deleted (an Account, the copy of an Account that remained in the shared instance after its move to an instance of its own, a Customer Domain, a Mailbox, an address or an S/MIME key) and its identifiers, and for a Mailbox or an address a keyed hash of the address, without the address itself. Supplier uses it only to delete the data again after a restore of a backup or of a copy of clause 12.3, and deletes it 366 days after the deletion;
  • for a Microsoft 365 organisation that the Account connected, the identifier that Microsoft gives the organisation and the time it was connected, without anything that identifies the Account. Supplier uses it only so that another Account can connect that organisation only after an administrator of the organisation has signed in (Annex II), and keeps it without a time limit, because Supplier cannot tell when the organisation deletes Supplier's application; and
  • the entries in the audit log and the other records that Supplier keeps as a controller (Privacy Statement), which are deleted as the Privacy Statement states.

Some of the data above, 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, the records of the consent of Users to notifications 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), including the copies of clause 12.3. The backups of that server are stored on another server that Supplier manages itself, in France (EEA). The public DKIM keys of Customer Domains are published in Supplier's DNS zone at its Sub-processor (Annex III, part A).

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 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. In addition, Supplier publishes the public DKIM keys of Customer Domains in its DNS zone at its Sub-processor (Annex III, part A). Annex III lists the parties that receive data from the Service.
  • All data on the disks of the server in Germany is encrypted at rest (full-disk encryption), including the copies of each instance of the mailbox software kept there, 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 only space, power and network connectivity. It has no access to the data on the server and cannot read it, because all of that data is encrypted.

Encryption in transit

  • The webmail, Outlook (MAPI over HTTP and Exchange Web Services), Exchange ActiveSync, autodiscover, autoconfig, the Website and the Customer Console are available only over HTTPS; plain HTTP requests are redirected to HTTPS. The Website, the Customer Console and the webmail 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 the webmail, autodiscover, autoconfig, 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 certificate from Let's Encrypt for mx.althi.work and *.mx.althi.work, the MX host names that Customer Domains publish; because it is a single wildcard certificate, the names of Customer Domains do not appear in Certificate Transparency logs through it. If that certificate cannot be renewed, a self-signed certificate is used, 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. The webmail and the component that holds the S/MIME keys are only on internal networks, without access to the internet.

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 and limits the number of simultaneous connections per address on ports 465 and 993.
  • 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. Failed sign-ins to Mailboxes of apps that connect over HTTPS, such as Outlook and phones, are counted per address, per network and per account, and over a limit refused before they reach the mailbox software; an account that signed in successfully from a place within 24 hours is not held back there by guessers elsewhere.

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. Where Supplier offers this option, which it switches on or off separately for the Customer Console and for its own administration console, an administrator can choose, when entering the code, to trust that browser for 30 days; until then, the password alone is enough to sign in from that browser. The trust is bound to the administrator's password and second factor by a keyed checksum (HMAC-SHA256), is not extended by use, and ends earlier when the password or second factor changes, when the administrator forgets the browser, or when Supplier switches the option off. A change of the MX records through the automatic DNS setup, and its undo, require a new code, also in a trusted browser.
  • 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, and those that Users set on the Website at least 12; the Customer Console does not store them, but passes them to the mailbox software, which stores them as hashes.
  • Two-factor secrets are stored encrypted (AES-256-GCM). Session tokens, the secret codes in the cookies of trusted browsers, e-mail verification tokens and the tokens of invitation links 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 to the Customer Console 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. They cannot export S/MIME private keys in Supplier's administration console. They can create Administrators of an Account and reset the password and second factor of its Administrators; these actions are recorded in the audit log of the Account, which its Administrators can see.

Webmail

  • The mailbox software offers the webmail no tokens, so the webmail uses the User's own password for every request to the Mailbox. It keeps the password for the life of the session, sealed with AES-256-GCM under a key that is derived from a random key that only the browser's session cookie holds and a secret of the server: neither a copy of the webmail's database nor that secret alone opens it. The database keeps only a hash of the session's identifier, and no address in clear.
  • The password is decrypted in memory for each request, and stays in memory only while the browser holds a live connection open, and at most 10 minutes after the last one closed.
  • Sessions end after 12 hours without use and at the latest after 7 days, and at sign-out. A change of the password, a disabled or deleted Mailbox and a suspended Account end or pause them. Users see their sessions per browser, with the browser, operating system, IP address and times, and can end one or all others.
  • The webmail's cookies are bound to its own host, cannot be read by scripts, are sent only over HTTPS and are not sent with requests from other websites. Every change must come from the webmail's own pages, and a strict content security policy applies.
  • Failed sign-ins are limited per IP address, per network and per address; a browser in which the User signed in before has a limit of its own. The sign-in log stores the address only as a keyed hash.
  • The webmail has no access to the internet. It cleans the HTML of messages on the server and again in the browser, and shows it in an isolated frame that cannot reach the webmail's data or session. Images and other content from the internet are held back until the User chooses to show them; they are then loaded by the User's browser directly from the sender's servers, never by Supplier. Images known to track the reading of a message are never loaded.
  • Previews of attachments are offered only when the first bytes of the file prove its type. PDF files are drawn in the browser by software that is shipped with the Service (pdf.js), in an isolated area that cannot fetch anything, runs no scripts of the PDF and shows no forms or links. No document viewer of a third party is used. Previews and the ZIP files of "Download all" are not stored.
  • Search terms are sent only in the body of requests and are never logged. The request logs of the webmail contain no query strings, addresses or content.
  • The working data of the webmail (sessions, uploads, its sign-in log and limits) are not included in the backups.

Separation of customers

  • Each Account is a separate organisation in the mailbox software, with its own Customer Domains, Users and Administrators. During the Trial, and until it is moved, an Account shares an instance of the mailbox software with other Accounts and is separated from them logically; an Account that has been moved to an instance of its own (clause 13.7 of the Terms) has its own instance and database. All instances run on the same server and share its disks, the network, the reverse proxy, the mail transfer agents and the spam filter, the webmail, the Customer Console and the backups.
  • On a shared instance, calendars, free/busy times and public folders are limited to each Account. A permission that a User's app grants to everyone on the instance is reduced to the User's own Account within 5 minutes. A permission that a User grants on their own folders to a User of another Account takes effect, and is reported to Supplier. A lookup of an exact address by a User of another Account on the same instance can show that the address exists, with the name and directory details that the mailbox software holds for it.
  • A domain can be used as a Customer Domain only after the Customer has proven control of it through DNS, which the Service checks at the domain's own name servers, or after Supplier has established in another way that the Customer controls it, and only one Account can verify the same domain.
  • A Microsoft 365 organisation can be connected to an Account only if one of its domains is a Customer Domain of that Account that the Account verified through its DNS record; this is checked again before every read. The organisation is bound to the Account whose consent connected it first: as long as the organisation has not deleted Supplier's application, that Account can connect it again without a new consent, and another Account, also one that has verified one of its domains in this way, only after a Global Administrator or Privileged Role Administrator of the organisation has signed in at Microsoft for that Account's connection, and not while another Account is still reading from it (clause 11.9(f) of the Terms).
  • Users can send mail through SMTP only with sender addresses of their own Mailbox and, with Send As or Send on behalf, of another Mailbox of the same Account. On every route, the Service accepts outgoing mail only with sender addresses in the Customer Domains of the sender's own Account, except mail that a User or a rule forwards. In apps that connect through MAPI over HTTP or Exchange Web Services, the sender address is therefore bound to the Account, not to the User (clause 6.3(i) of the Terms).
  • Mail from the internet that uses a live Customer Domain as the sender address in its envelope is refused, so that it cannot be passed off as mail from an Account. Mail for Mailboxes in the Service whose sender address names a domain hosted in the Service is delivered only if the Service signs it for that domain or has checked its sender itself.

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 2,048-bit RSA keys of its own for each domain. Supplier can replace a key; the previous public key then stays published for 7 days. The DKIM keys and the MX host names of Customer Domains are published in Supplier's DNS zone, which its Sub-processor hosts (Annex III, part A). The Customer Console limits its own writes to that zone to the DKIM records of Customer Domains, and only for keys that the mail server holds. The access tokens with which the Service writes to the zone are limited to that zone, in which they could change any record, and can be used only from Supplier's own IP address.
  • Templates of signatures and disclaimers are limited to an allow-list of HTML when they are saved, and their images are rebuilt without metadata and embedded in the message, so that opening a message contacts no server of Supplier.
  • 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.

Key custody (S/MIME)

  • Private keys are held only in a separate component of the Service, on two internal networks without access to the internet. The component that sends mail can only ask it to sign the hash of a message; the key component builds the signature itself, limits the number of signatures per key, and logs no addresses, hashes or key material.
  • An uploaded key and its password go only to the key component; they are never stored unsealed, logged, recorded in the audit log or included in an error.
  • Each key is sealed with AES-256-GCM under a data key of its own, which is sealed under a key per Account, which is sealed under a master key. The master key is a file outside the server-level backups, which Supplier checks. It is held in escrow offline as three shares on paper, of which any two rebuild it, kept by different persons or in different places. Supplier rotates it every year and when a holder of a share leaves, and checks the shares every year.
  • Keys can be exported only in the Customer Console, by Administrators of the Customer, not in Supplier's administration console. Supplier's personnel can create Administrators of an Account and reset their credentials (see Access control); these actions show in the Account's audit log. An export is protected with a password (PKCS #12 with PBES2 and AES-256), which is given once in a separate step; every export is recorded in the audit log and, while the Mailbox is enabled, notified to the Mailbox.
  • Every destruction of a key is recorded in a journal on the server, which is copied at least every hour to another server that Supplier manages itself, in the EEA, outside the backups. After a restore of a backup, the key component signs nothing until the destructions recorded since that backup have been carried out again.
  • These measures do not protect against a person who has full control of the running server, or against a compromised component of the Service that may call the key component: while it runs, such a person or component could use the keys.

DNS checks and changes

  • The DNS checks of Customer Domains ask only globally reachable name servers, verify DNSSEC signatures where a zone is signed, and are rate-limited per Account.
  • Access data for DNS providers is never written to storage, logs or backups, which an automated test checks. Calls to DNS providers go only to their fixed programming interfaces, over HTTPS, from Supplier's own address.
  • Before every call to a provider, a list of allowed names, record types and values for each step is checked on the server. Nothing is written unless the provider serves the zone of the Customer Domain.
  • Changes of MX records through the automatic setup require the Administrator's second factor; every change is recorded, with the records before and after, in a history whose entries carry a keyed checksum that reveals changes, and in the audit log, and is notified to the Customer's Administrators.

Copying from Microsoft 365

  • Supplier's application at Microsoft signs in with a certificate, never with a password. Its private key is held only by the component that copies, and is replaced at least every 12 months. The access tokens that Microsoft issues are kept only in memory and are never logged.
  • The application asks only for read-only permissions, and the Service changes nothing in Microsoft 365.
  • Items being copied are held on Supplier's server only between download and import, in files that only the copying component and the mailbox software that imports them can access; they are deleted once imported, and at the latest after 24 hours, and are not included in the backups. They are imported directly into the mailbox software, not sent as mail.

Notifications of the webmail

  • Notifications of the webmail are produced and encrypted (RFC 8291) on the server that holds the Mailbox, for the one device they are meant for, and padded to one size, so that the push service learns neither their content nor whether they show the sender and subject or titles. By default a notification shows only that new mail arrived or the time of an appointment or task; the sender and subject, and the titles and places of appointments and tasks, only where the User chose so on that device, for at most 7 days after the User's last sign-in there.
  • The webmail has no connection to the internet. Notifications leave only through a relay in another component of the Service, which sends only notifications that the server holding the Mailbox signed with a key of its own, which the webmail does not have, each delivered at most three times, with limits per push address, and only to the push services named in Annex III, part C.
  • Push addresses are stored encrypted (AES-256-GCM) and are never written to logs.
  • Signing out on a device, ending its session in the webmail's list of devices or removing the device stops its notifications; a new device that receives notifications is announced on the User's other devices and by a message in the User's Inbox.

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, for at most 90 days (Annex I); they are not records of events. The access log of the reverse proxy records neither the path nor the query of a request, and the routers of pages whose links carry a secret, such as invitation and verification links, are left out of it. The access log of the web server of the mailbox software records the path and query of each request as it arrives and the user name of each request that signs in with a password, which is the address of the Mailbox; for some phones and tablets the query includes that address as well.

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. In addition, the Service keeps the two most recent nightly copies of each instance of the mailbox software on the same server, to restore that instance quickly. Backups and these copies 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. The instance of its own of a deleted Account is removed, with its data. Items that Users delete for good are removed after 30 days (Annex I).
  • When an Account is deleted, the key per Account that seals its S/MIME keys is destroyed, so that its keys can no longer be opened in the running Service; they remain in the backups, sealed, until those are deleted (clause 12.3), and after a restore of a backup this destruction is carried out again before any key is used (see Key custody). When an S/MIME key is destroyed, its certificate, its chain, the address and its counts are deleted too.
  • When a Customer Domain is removed or the Account is deleted, the private DKIM keys of the Service for that domain are destroyed, and a domain that is added again gets a new key.
  • Annex I and clause 12 describe the retention periods and deletion, and the records that remain after a deletion.

Software and change management

  • Third-party container images, the build recipe of the mailbox software, every package of the mailbox software and the libraries of Supplier's own components are pinned to exact versions; other operating-system packages are installed in the version that is current when Supplier builds an image. Supplier updates and rebuilds them deliberately.
  • Supplier's own services run without administrator rights inside their containers. The public Website runs without any operating-system privileges. The component that controls the other containers has access to the container engine and can only perform a fixed list of actions with validated parameters; the programs of Supplier that it runs inside the containers of the mailbox software have the rights that the mailbox software needs.
  • The software of the Service includes automated tests of security-relevant behaviour, such as the relay rules of the mail servers, the checks on sender addresses and the separation of Accounts.

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

Sub-processor Processing Location Transfer basis
Cloudflare, Inc., United States, which hosts Supplier's DNS zone althi.work Publishing, for each Customer Domain, two DNS records under dkim.althi.work, named after the domain, with its public DKIM keys, and answering queries for them, and for the MX host names of Customer Domains under mx.althi.work, which are also named after the domain, from other mail systems. Cloudflare receives no other Customer Data United States and other countries EU-US Data Privacy Framework (adequacy decision of the European Commission of 10 July 2023), under which Cloudflare, Inc. is certified

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 cannot access 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, because the spam filter consults them about incoming mail, or because an Administrator has the Service fetch an image from them.

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. To check Customer Domains, the Customer Console also asks the domain's own name servers, and those of its parent zones, such as the registry of its top-level domain, directly from Supplier's server, for the records the Service needs (ownership, MX, SPF, DKIM, DMARC, autodiscover, autoconfig and MTA-STS); these operators see Supplier's IP address and the names asked Delivering mail, checking sender authentication, verifying control of Customer Domains, checking their records, and deciding when incoming mail is delivered to the Service and which host names get a certificate 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 domain names that some components of the Service look up, such as those of the mail servers to which mail is delivered, the addresses of the mail servers that the MX records of a Customer Domain name, and the domain in the sender address of an incoming message, which the receiving mail server checks before it accepts the message; these names then pass through Cloudflare's resolver. Never the lookups of the spam filter, never the checks of Customer Domains at their own name servers, and never the content of messages Delivering mail, checking the sender domains of incoming mail 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, only once those host names point to the Service, which the Service checks at the domain's own name servers; where no wildcard certificate is used, the Customer's sign-in host name under althi.work; and, for the certificate of the receiving mail servers, only the platform's own names mx.althi.work and *.mx.althi.work Issuing TLS certificates for these host names. Like all publicly trusted certificates, they are published in public Certificate Transparency logs, so the names of the Customer Domains in them become public, with a date; this cannot be undone United States
Operators of the websites from which an Administrator has the Service import an image for a signature Supplier's IP address and the address of the image Fetching the image once, when the template is saved Worldwide

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.

Part C – Push services chosen by Users' browsers

When a User turns on notifications of the webmail on a device, the push service of that device's browser delivers them. It is chosen by the browser, not by Supplier, and is not a Sub-processor. It receives the device's push address, the time, size and permitted lifetime of each notification, and Supplier's IP address; the notifications are encrypted for the device, so it cannot read them. Before a User turns them on, the webmail names the push service and what it receives.

Push service Operator Browsers Its addresses Location Transfer basis
Firebase Cloud Messaging Google LLC Chrome, Edge on Android, Samsung Internet, Opera and other browsers based on Chromium fcm.googleapis.com United States EU-US Data Privacy Framework, under which Google LLC is certified
Apple Push Notification service Apple Inc. Safari, and every browser on iPhone and iPad *.push.apple.com United States EU-US Data Privacy Framework, under which Apple Inc. is certified
Windows Push Notification Services Microsoft Corporation Edge on Windows *.notify.windows.com United States EU-US Data Privacy Framework, under which Microsoft Corporation is certified
Mozilla Push Service Mozilla Corporation Firefox *.push.services.mozilla.com United States EU-US Data Privacy Framework, under which Mozilla Corporation is certified

Part D – Providers chosen by the Customer

The following parties are the Customer's own providers, or the providers of apps that its Users choose, under their own contracts with the Customer or its Users. They do not process anything on behalf of Supplier and are not Sub-processors. The Service exchanges data with them only on the instructions of the Customer and its Users (clause 7.2(d) and (f)).

Recipient Data Purpose Location
The Customer's DNS provider, chosen by the Customer (at the date of this DPA, the Service can make changes at Cloudflare, Amazon Web Services Route 53, Google Cloud DNS, GoDaddy, Openprovider, TransIP and Namecheap) The access data that an Administrator created there, the name of the Customer Domain, requests to read its records (some providers return all records of the domain at once), and the changes that the Administrator confirmed; from Supplier's IP address Making the DNS changes that an Administrator confirms (clause 11.8 of the Terms) Where that provider is established: for the providers named, the United States (Cloudflare, Amazon Web Services, Google, GoDaddy and Namecheap) or the Netherlands (Openprovider and TransIP)
The host of the Customer's own MTA-STS policy Supplier's IP address and the host name mta-sts of the Customer Domain Reading that policy before the Service changes the MX records (clause 11.8(f) of the Terms) Where the Customer's provider hosts it
Microsoft, the Customer's provider of Microsoft 365 Supplier's requests for the connected organisation, signed with the certificate of Supplier's application: the identifier of the organisation, and the identifiers of its users, mailboxes, folders and items in the addresses of the requests Copying the Customer's mail, calendars and contacts into the Service on the Customer's instructions (clause 11.9 of the Terms); Microsoft sends the data, and Supplier sends it no content Where Microsoft processes the Customer's organisation, which may be outside the EEA
Microsoft, as the maker of Outlook for iOS and Android and of the new Outlook for Windows, where Users use these apps The User's address and password, with which Microsoft's servers sign in to the Service, and the mail, and with Outlook for iOS and Android also the calendars and contacts, that the app synchronises; the Service sees Microsoft's IP addresses Letting the app reach the Mailbox through Microsoft's cloud (clause 11.6 of the Terms) Where Microsoft processes the data of these apps, which may be outside the EEA

Version 1.2 of the Data Processing Agreement, effective 23 October 2026: https://althi.work/dpa/v/1.2

work

Business email and calendar for EU companies.

support@althi.digital

Product

  • Pricing
  • Start free trial
  • Log in
  • Change your password
  • Admin portal

Legal

  • Terms of Service
  • Data Processing Agreement
  • Privacy
  • Switching and data export
  • Contact

Althi Digital Services B.V. · Bargelaan 200, 2333CW Leiden · KvK 60860448 · VAT NL854092031B02

All prices exclude VAT.