This page explains how a Customer of Althi.work, the hosted business e-mail service of Althi Digital Services B.V., can move its data to another provider or to its own systems, in which formats that data is available, what switching costs, and where the infrastructure of the Service is located. It gives the information that Supplier provides under articles 26, 28 and 29 of the Data Act (Regulation (EU) 2023/2854). It is always available at https://althi.work/switching.
1. About this page
1.1 Capitalised terms, such as Account, Administrator, Agreement, Billing Period, Customer, Customer Console, Customer Data, Customer Domain, Fees, Mailbox, Privacy Statement, Service, Supplier, Trial, User, Website and Working Day, have the meaning given in the Terms of Service at https://althi.work/terms ("Terms"), and Sub-processor has the meaning given in the Data Processing Agreement at https://althi.work/dpa ("DPA").
1.2 This page describes how the switching rules of clauses 15 to 17 of the Terms and clause 12 of the DPA work in practice. It does not change them: if this page differs from the Terms or the DPA, the Terms and the DPA prevail.
1.3 This page is the online register of the data structures, data formats and standards in which the exportable data are available (clause 17.4 of the Terms; section 5), and the information on jurisdiction and on governmental access that clause 17.7 of the Terms refers to (sections 7 and 8). Supplier keeps it up to date.
2. How switching works
2.1 Notice. The Customer can switch to another provider, or to its own systems, at any time by terminating the Agreement, in the billing section of the Customer Console or by e-mail to support@althi.digital (clause 15.2 of the Terms). The termination takes effect at the end of the current Billing Period; during the Trial, at the end of the Trial; and while the Account is suspended for non-payment or at the end of the Trial, at once. The notice period is therefore never longer than one month.
2.2 The Customer's choice. With the termination, or before it takes effect, the Customer can tell Supplier that it wants to switch to another provider, giving the details of that provider that are needed for the switch; to switch to its own systems; or to have its Customer Data erased when the termination takes effect (clause 17.2 of the Terms).
2.3 Transitional period. If the Customer switches to another provider or to its own systems, the Service continues at its request for a transitional period of up to 30 calendar days after the date on which the termination would otherwise take effect. The Customer can extend the transitional period once, for a period that it considers more appropriate. The Agreement continues to apply during the transitional period, and the Fees for that period are due pro rata. If a transitional period of 30 calendar days is technically not feasible, Supplier says so within 14 Working Days of the request, explains why, and offers an alternative transitional period of at most seven months. If the Account is suspended for non-payment or at the end of the Trial, the Service continues during the transitional period only once the Account has been resumed; the Customer can always retrieve its data free of charge under section 2.6.
2.4 Assistance. During the notice period and the transitional period, Supplier assists the Customer, and third parties that the Customer authorises, such as its new provider. It provides all relevant information, such as the export options (sections 3 and 5) and the DNS changes that are needed, removes at the Customer's request the DNS records that the Service made at the Customer's DNS provider (section 2.10), continues to provide the Service with due care, informs the Customer of known risks to continuity, and keeps Customer Data secure, also while it is being transferred.
2.5 End of the Agreement. The Agreement ends when the switch has been completed: at the end of the transitional period, or earlier if the Customer confirms that the switch has been completed. Without a transitional period, it ends when the termination takes effect. Supplier confirms the end of the Agreement by e-mail.
2.6 Retrieval period. When the Agreement ends, Supplier suspends the Account: Users can no longer sign in, and incoming mail for the Customer Domains, other than Supplier's own notices, is not delivered (its senders receive a notice that it could not be delivered). The Customer can still retrieve its Customer Data free of charge until the Account is deleted, 183 days (about six months) after the start of the suspension (the retrieval period). At the Customer's request, Supplier restores access to the Mailboxes by hand, within two Working Days and for at least 30 calendar days, so that Users can retrieve their data with their mail apps and webmail. During that time, Supplier may block the sending and receiving of mail. Where needed, Supplier postpones the deletion, so that, where the Agreement ended before the deletion, the retrieval period ends no earlier than 30 calendar days after the termination took effect, and in any case no earlier than the end of the restored access (clauses 16 and 17.3 of the Terms). The same applies while the Account is suspended for another reason, for example at the end of the Trial.
2.7 Erasure. At the end of the retrieval period, when the Account is deleted, or earlier at the Customer's request (within 30 days of the request), Supplier erases all exportable data and all other Customer Data in full from all active systems of the Service, including the Account's instance of its own of the mailbox software, its records of migrations and its S/MIME keys, and confirms the erasure on request. The few records that remain after the deletion, such as the bare record that an S/MIME key was destroyed and the records that Supplier keeps for its own purposes as a controller, are listed in Annex I of the DPA. Copies in backups, and the copies of each instance of the mailbox software on the same server, follow their rotation: they can remain for at most 365 days after the erasure, during which they are put beyond use and used only to restore the Service after an incident; if a backup or such a copy is restored, Supplier erases the data again (clause 17.6 of the Terms and clause 12.3 of the DPA). Supplier keeps the data that it needs for its own purposes, such as invoices and VAT records, as described in the Privacy Statement.
2.8 Recommended order. To avoid losing mail, the Customer should:
- (a) set up the new provider and copy the data while the Service is still running (section 3);
- (b) change the DNS records of its Customer Domains, in particular the MX records, at its own DNS provider, or have its new provider do so, and keep the Service running until the changes have taken effect; then replace or remove the DKIM records that point to Supplier's DNS zone and the autodiscover and autoconfig records that point to the Service, or let the Service remove the records it made (section 2.10); and
- (c) only then let the Agreement end, because incoming mail is not delivered while the Account is suspended.
2.9 Moving to Althi.work. A business that moves to Althi.work from Microsoft 365 can have the Service copy the mail, calendars and contacts of its mailboxes, free of charge, after an administrator of its Microsoft 365 organisation has granted Supplier's application read-only access to it (clause 11.9 of the Terms). The Service also creates the Mailboxes, aliases and rights that the Administrator sets, and can invite the Users to choose a password. It does not copy tasks, server-side rules, archive mailboxes, automatic replies, permissions, attachments of calendar items, contact photos and contact groups, and deletions in Microsoft 365 after the last copy are not carried over. From other providers, a business can copy its messages into the Mailboxes over IMAP, with a mail app or a migration tool, and import calendars, contacts, tasks and notes with classic Outlook for Windows or another compatible app. It then verifies its domains and publishes the DNS records that the Customer Console shows, or lets the Service make them at its DNS provider (clause 11.8 of the Terms). Supplier charges nothing for moving data in.
2.10 Removing the DNS records that the Service made. Once the MX records of a Customer Domain no longer point to the Service, and until the Account is deleted, an Administrator can let the Service remove, with new access data for the DNS provider, what the Service made there: Supplier's ownership record, Supplier's part of the SPF record (or the whole SPF record, if the Service created it), the DKIM records, the DMARC record that the Service created (never one of the Customer's own), and the autodiscover and autoconfig records that point to the Service. The Service never removes MX records, nor records that the Customer made itself. Nothing is removed automatically at the end of the Agreement, because Supplier holds no access data. Supplier keeps publishing the DKIM keys in its own DNS zone until 7 days after the Customer Domain or the Account has been deleted. Records that the Customer leaves in its own zone keep pointing to names under althi.work, so the Customer should replace or remove them.
3. Export methods
3.1 Who exports. While the Account is active, the Customer can export its data itself at any time; while it is suspended, after Supplier has restored access (section 2.6). The Service has no tool yet to export all Mailboxes at once, so each Mailbox is exported on its own, with its own sign-in details. Administrators can set a new password for a Mailbox in the Customer Console, for example so that a migration tool can copy it.
3.2 Mail apps over IMAP. A mail app or migration tool that supports IMAP can download all e-mail folders of a Mailbox, with their messages and attachments, from the Customer's sign-in address under althi.work (such as yourcompany.althi.work), port 993, with TLS. IMAP is a protocol for e-mail; calendars, contacts, tasks and notes are exported through the routes below.
3.3 Webmail. Depending on the Account, the webmail is the Service's own webmail at mail.althi.work, grommunio-web at the Customer's sign-in address, or both (clause 6.7 of the Terms). In the webmail of the Service, a User can download a message as a file in the standard e-mail format (EML), and the attachments of a message one by one or together as a ZIP file. In grommunio-web, where the Account has it, a User can download a message as an EML file, several selected messages at once as a ZIP file of EML files, a contact as a vCard file and an appointment as an iCalendar file.
3.4 Classic Outlook for Windows. Classic Outlook for Windows, connected to a Mailbox through MAPI over HTTP, can export the Mailbox, including its calendars, contacts, tasks and notes, to an Outlook data file (PST), and can save calendars and contacts in standard formats such as iCalendar and vCard. Other apps, such as Outlook for Mac (through Exchange Web Services) and the apps of phones and tablets (through Exchange ActiveSync), may have their own export functions.
3.5 CalDAV and CardDAV. The mailbox software also offers calendars through CalDAV and contacts through CardDAV, at the Customer's sign-in address. Apps that support these protocols can read and export calendars and contacts with them. Supplier gives the connection details on request.
3.6 Customer Console. The Customer Console has no general export function yet. Administrators can view and copy what it shows: the data about Users, Mailboxes, Administrators and Customer Domains, the rights to Mailboxes, the settings of the Account, such as the signatures, banners and disclaimers with their rules, footers and the delayed-sending period, the history of DNS changes made through the Service, and the log of changes. They can download the S/MIME certificate of each Mailbox (as a PEM file with its chain) and the report of each migration (as CSV or JSON), and export the S/MIME private keys (section 3.8).
3.7 Export by Supplier on request. On request to support@althi.digital, Supplier exports free of charge, within 14 days, in the formats of section 5: the settings that Users manage for their own Mailbox, such as server-side rules and automatic replies; the data and settings that the Customer Console shows, including the signatures, banners and disclaimers with their rules, groups, company details and images; the log of changes; the history of DNS changes; the records of outgoing messages that the Service still holds; and the DMARC aggregate reports received for the Customer Domains. Supplier also exports the S/MIME certificates of the Mailboxes, with their chains (clause 17.4 of the Terms); the private keys that it holds for them are exported by Administrators themselves (section 3.8), because Supplier's staff cannot export them in Supplier's administration console (clause 11.10(b) of the Terms).
3.8 S/MIME keys. Administrators can export, in the Customer Console, every private key that Supplier holds for a Mailbox, with its certificate and chain, as a PKCS #12 file protected with PBES2 and AES-256 (an older format with 3DES can be chosen for older apps). The password is given once, in a separate step, and the Mailbox receives a notice of the export. The keys of a deleted Mailbox can still be exported for 30 days after its deletion.
4. Known restrictions and technical limitations
- The Service has no tool yet to export all Mailboxes at once; each Mailbox is exported on its own (section 3.1).
- IMAP is offered only with TLS from the start of the connection (port 993). POP3 is not offered.
- The new Outlook for Windows can add a Mailbox only as an IMAP account, so it cannot export calendars, contacts, tasks or notes from the Service.
- The webmail of the Service downloads single messages and their attachments, but not several messages at once, contacts or appointments, and it imports nothing (section 3.3); grommunio-web, where the Customer still has it, downloads single items or a selection of messages. Neither downloads a whole Mailbox.
- Tasks and notes can be exported as a file through classic Outlook for Windows (PST) or the export functions of other apps; the Service offers no other file format for them.
- There is no common open standard for the server-side rules and automatic replies of the mailbox software, nor for the rules of signatures and disclaimers. Supplier exports them on request (section 3.7), but the new provider may have to set them up again.
- For shared, room and equipment mailboxes, Supplier helps on request (section 2.4).
- The DKIM keys of the Service are not exported (section 5.2). The Customer's DKIM records point to keys in Supplier's DNS zone; the new provider issues its own keys, and the Customer replaces those records, or lets the Service remove them (section 2.10).
- The sign-in address under althi.work and the MX host names under mx.althi.work cannot be taken along: they are not e-mail domains (clause 6.2 of the Terms).
- While the Account is suspended, apps cannot connect until Supplier has restored access (section 2.6), and incoming mail is not delivered.
- An export through an app depends on the functions of that app. Supplier does not guarantee that every app can export every type of data (clause 18.4 of the Terms).
5. Register of exportable data
5.1 The exportable data are exhaustively the data listed in clause 17.4 of the Terms. They are available as follows. "Self-service" means that the Customer or its Users can export the data themselves (section 3); "on request" means that Supplier exports the data free of charge within 14 days of a request to support@althi.digital (section 3.7).
| Data (clause 17.4 of the Terms) | Data structure | Formats and route | Standards and specifications | How |
|---|---|---|---|---|
| (a) Messages, with their attachments and folders | A tree of folders per Mailbox; each message with its header fields, body parts and attachments | EML files through IMAP or the webmail (in grommunio-web, also several at once as a ZIP file); the whole Mailbox as an Outlook data file (PST) through classic Outlook for Windows | Internet Message Format (RFC 5322) and MIME (RFC 2045 to RFC 2049); IMAP (RFC 3501) with TLS (RFC 8314); ZIP; PST: Microsoft open specification MS-PST | Self-service |
| (a) Calendars | Calendar folders with appointments and meetings, including times, recurrence, attendees and reminders | iCalendar files from apps, or from grommunio-web where the Customer still has it; CalDAV; PST through classic Outlook for Windows | iCalendar (RFC 5545); CalDAV (RFC 4791); MS-PST | Self-service |
| (a) Contacts | Contact folders with contacts: names, e-mail addresses, telephone numbers, street addresses and other fields | vCard files from apps, or from grommunio-web where the Customer still has it; CardDAV; PST through classic Outlook for Windows | vCard (RFC 6350); CardDAV (RFC 6352); MS-PST | Self-service |
| (a) Tasks | Task folders with tasks: subject, dates, status and description | PST through classic Outlook for Windows, or the export functions of other apps | MS-PST; iCalendar (RFC 5545) where an app exports tasks in that format | Self-service |
| (a) Notes | Note folders with notes: text and times | PST through classic Outlook for Windows | MS-PST | Self-service |
| (b) Server-side rules and automatic replies | Per Mailbox: rules with name, order, conditions, actions and status; the automatic reply with status, period, audience and reply texts | JSON | JSON (RFC 8259); there is no common open standard for these rules | On request |
| (c) Users, Mailboxes, Administrators, Customer Domains and the settings of the Account | One record per User, Mailbox, Administrator and Customer Domain, with names, e-mail addresses, aliases, roles, status and the rights to Mailboxes; settings of the Account, such as footers (templates in HTML and plain text), the delayed-sending period and the device policy for mobile devices | CSV or JSON | CSV (RFC 4180); JSON (RFC 8259); e-mail addresses as in RFC 5322; HTML for footer templates | On request; can be viewed in the Customer Console |
| (c) Signatures, banners and disclaimers | Per Account: the blocks (templates in HTML and plain text), the rules with their conditions and order, the groups with the addresses of their Mailboxes, the company details, the settings, and the images with their names and sizes; per Mailbox the fields that signatures show | JSON, with the images as PNG or JPEG files encoded in it | JSON (RFC 8259); HTML; PNG (ISO/IEC 15948); JPEG (ISO/IEC 10918-1); Base64 (RFC 4648) | On request; can be viewed in the Customer Console |
| (d) Log of changes of the Customer Console | One entry per change: who made it, what changed, when, and from which IP address | CSV or JSON | CSV (RFC 4180); JSON (RFC 8259); times in ISO 8601 | On request; can be viewed in the Customer Console |
| (d) History of DNS changes made through the Service | One entry per change: the Customer Domain, the provider, the step, the records before and after (names, types, lifetimes and values), the Administrator who confirmed it, and the times; kept 2 years, and deleted earlier with the Customer Domain | CSV or JSON | CSV (RFC 4180); JSON (RFC 8259); DNS records as in RFC 1035; times in ISO 8601 | On request; can be viewed in the Customer Console |
| (d) Reports of migrations | Per migration: counts per Mailbox and folder, folder paths, target addresses, and the items that failed or were skipped, with their code; the summary is kept 90 days after the migration ended, the list of items 30 days | CSV or JSON | CSV (RFC 4180); JSON (RFC 8259) | Self-service, in the Customer Console |
| (d) Records of outgoing messages | One record per message: sender, recipients, subject, size, times, status and message identifier, kept for 30 days after the message reached its final status | CSV or JSON | CSV (RFC 4180); JSON (RFC 8259); addresses and message identifiers as in RFC 5322 | On request |
| (d) DMARC aggregate reports | The reports that other mail providers send about mail in the name of the Customer Domains, per reporting provider and period, kept for 90 days after receipt | The reports as received: XML files, usually compressed | DMARC (RFC 7489) | On request |
| (e) S/MIME certificates and their private keys | Per Mailbox: every certificate whose private key Supplier holds, with that key and its certificate chain | PKCS #12 file, protected with PBES2 and AES-256 (optionally 3DES), the password given separately; the certificate alone as a PEM file | PKCS #12 (RFC 7292); PBES2 (RFC 8018); X.509 certificates (RFC 5280); S/MIME (RFC 8551) | Self-service, in the Customer Console; the certificates also on request |
5.2 The following data are specific to the internal operation of the Service and are, exhaustively, not exportable data (clause 17.4 of the Terms): the working data of the spam filter, of the mail queues and of the sending limits (such as counters and caches), the technical logs of the components of the Service, the DKIM keys and other cryptographic keys of the Service, and the configuration of Supplier's systems. Apart from the log of changes, data that Supplier processes as a controller for its own purposes are not part of a switch; the Privacy Statement explains how data subjects can exercise their rights in respect of them.
6. Charges
6.1 Supplier charges no switching charges, no data egress charges, no fees for exporting Customer Data and no early termination penalties, also when the Customer leaves after the Trial (clause 17.5 of the Terms). Exports on request (section 3.7), restored access during the retrieval period (section 2.6) and the removal of DNS records that the Service made (section 2.10) are free of charge.
6.2 The Customer pays only the standard Fees for the Service, as shown on the Website and in the Customer Console (clause 8 of the Terms), also during a transitional period, pro rata. The Agreement has no minimum term and can be terminated at any time (section 2.1); Fees already paid for the current Billing Period are not refunded, except in the cases of clause 15.5 of the Terms.
7. Jurisdiction
7.1 The Service runs on Supplier's own server, which only Supplier manages, in a data centre in Germany; the copies of each instance of the mailbox software that serve to restore it quickly are kept on the same server. The backups of that server are stored, encrypted, on another server that Supplier manages itself, in France, within the European Economic Area (EEA). Supplier publishes the public DKIM keys of Customer Domains in its own DNS zone, which Cloudflare, Inc. hosts (Annex III, part A of the DPA). Supplier is established in the Netherlands.
7.2 The infrastructure of the Service is therefore subject to the jurisdiction of Germany and the Netherlands, the backups also to the jurisdiction of France, and the DKIM records at Cloudflare also to the jurisdiction of the United States.
8. Measures against unlawful governmental access
8.1 Supplier takes the following measures to prevent governmental access to, or transfer of, Customer Data held in the European Union, including non-personal data, from outside the Union, where that access or transfer would conflict with Union law or with the law of the member state concerned (article 28(1)(b) of the Data Act).
8.2 Technical measures.
- Customer Data is stored only in the EEA: on Supplier's own server in Germany and, for the backups, on another server that Supplier manages itself in France (section 7). No third party administers these servers, and none can read the data on them. In addition, Supplier's one Sub-processor, Cloudflare, publishes the public DKIM keys of Customer Domains in Supplier's DNS zone; these keys are public by their nature (Annex III, part A of the DPA).
- 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, so the operator of a data centre cannot read the data.
- The private S/MIME keys that Supplier holds for Mailboxes are sealed in a separate component of the Service, under a master key that is kept outside the backups (Annex II of the DPA).
- Apps and browsers connect to the Service only over encrypted connections (HTTPS, and IMAP and SMTP with TLS). Mail is exchanged with other mail servers with TLS whenever they support it.
- Apart from Cloudflare's publication of DKIM keys, no processor outside the EEA handles Customer Data for Supplier. Some parties outside the EEA receive limited data because of how e-mail and the internet work (Annex III, part B of the DPA): the mail servers to which Users send mail; Let's Encrypt, which receives the host names for which it issues certificates; the DNS servers, block lists and reputation services that the Service consults, which receive domain names, IP addresses, hashed addresses and links, and checksums, but never a readable copy of a message; and Cloudflare's public DNS resolver, which the Service uses only when Supplier's own DNS resolver is unavailable or cannot resolve a name, and which then receives the domain names being looked up, such as the domains of the senders of incoming mail. The push service of a User's browser receives the encrypted notifications that the User turned on (Annex III, part C of the DPA). The Customer's own providers, such as its DNS provider and Microsoft 365, receive data only on the Customer's instructions, and so does Microsoft's cloud where Users use apps that reach the Service through it, such as Outlook for iOS and Android (Annex III, part D of the DPA).
8.3 Organisational measures. Only Supplier's own personnel administer the servers. They are bound to confidentiality, and no person at Supplier reads the content of Customer Data, except at the explicit request of the Customer or the User concerned, or where the law or a binding order of a competent authority requires it (clause 12.2 of the Terms).
8.4 Handling of requests from authorities. Supplier handles requests from authorities as described in clause 13 of the DPA:
- (a) Supplier discloses Customer Data to an authority only if Union or member state law requires it to do so. It 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;
- (b) Supplier informs the Customer of a request without delay, unless the law prohibits this, and where possible refers the authority to the Customer;
- (c) 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; and
- (d) these rules apply to personal data and to non-personal data alike (clause 13.4 of the DPA), and to the S/MIME keys that Supplier holds (clause 13.5 of the DPA). Sub-processors that Supplier engages are bound by obligations that offer at least the same level of protection (clause 6.5 of the DPA).
9. Contact
9.1 Questions and requests about switching, exports and the retrieval of data, such as a request for a transitional period, for an export on request or for restored access, can be sent to support@althi.digital, in English or Dutch. The Customer can terminate the Agreement in the billing section of the Customer Console or by e-mail to the same address.