These Terms of Service apply to Althi.work, a hosted business e-mail service that Althi Digital Services B.V. provides. Althi.work is offered only to businesses established in the European Union. Together with the Data Processing Agreement, these Terms form the agreement between Althi Digital Services B.V. and its customers. They are general terms and conditions (algemene voorwaarden) within the meaning of article 6:231 of the Dutch Civil Code. You can save and print them, and they are always available at https://althi.work/terms.
1. Definitions
In these Terms, the following capitalised terms have the meaning given below. The singular includes the plural and vice versa.
1.1 Account: the Customer's organisation in the Service, with its Customer Domains, Mailboxes, Users and Administrators.
1.2 Administrator: a User whom the Customer has given access to the Customer Console. An Administrator has full rights in the Customer Console (an Administrator with full rights), unless it has a role with limited rights, such as the helpdesk role, which can only see the data of the Account and set new passwords for Mailboxes.
1.3 Agreement: the agreement between Supplier and the Customer for the Service, consisting of these Terms, the DPA and the prices and options that apply to the Account.
1.4 Beta: the period during which Supplier offers the Service as a beta version (clause 7).
1.5 Billing Period: a period of one month for which Fees are charged.
1.6 Customer: the business that has concluded the Agreement with Supplier.
1.7 Customer Console: the administration portal of the Service at my.althi.work.
1.8 Customer Data: all data, including personal data, that the Customer or its Users store in the Service or send or receive through it, such as e-mail messages and attachments, calendar items, contacts, tasks, Mailbox settings, the templates and images of signatures and disclaimers, and certificates with their private keys, and the data about Users that the Service needs in order to work, such as accounts, addresses and technical logs.
1.9 Customer Domain: a domain name that the Customer has added to the Account in order to send and receive e-mail with it.
1.10 DPA: the Data Processing Agreement for Althi.work, published at https://althi.work/dpa, which forms part of the Agreement.
1.11 Fees: the amounts that the Customer owes for the Service.
1.12 Mailbox: a mailbox in the Service: a User Mailbox, or a shared, room or equipment mailbox.
1.13 Privacy Statement: Supplier's privacy statement for Althi.work, published at https://althi.work/privacy.
1.14 Service: Althi.work, the hosted e-mail, calendar and contacts service described in clause 6, including the Customer Console, the webmail, support and the add-ons that the Customer orders.
1.15 Supplier: Althi Digital Services B.V., established at Bargelaan 200, 2333CW Leiden, registered with the Dutch Chamber of Commerce (KvK) under number 60860448, VAT identification number NL854092031B02.
1.16 Trial: the free trial period described in clause 5.
1.17 User: a natural person whom the Customer allows to use the Service, such as an employee. Administrators are Users too.
1.18 User Mailbox: a Mailbox for one person, as opposed to a shared, room or equipment mailbox.
1.19 VIES: the VAT Information Exchange System of the European Commission, which confirms whether a VAT identification number is valid.
1.20 Website: https://althi.work, including the signup pages and the pages on which Users change their password or accept an invitation.
1.21 Working Day: Monday to Friday, except public holidays in the Netherlands.
1.22 In writing includes by e-mail.
2. Scope
2.1 These Terms apply to every offer by Supplier for the Service, to every Agreement and to every use of the Service.
2.2 The Service is offered only to businesses that act in the course of their trade, business or profession, and not to consumers. By accepting these Terms, the Customer confirms that it uses the Service predominantly for its business.
2.3 Supplier rejects the applicability of the Customer's own general terms and conditions, whatever they are called.
2.4 A deviation from these Terms applies only if Supplier has agreed to it in writing, and only to the Agreement for which it was agreed.
2.5 Supplier makes these Terms and the DPA available electronically before the Agreement is concluded, in a way that allows the Customer to save them and to consult them later (article 6:234 of the Dutch Civil Code). On request, Supplier sends a copy free of charge.
2.6 These Terms are written in English. If Supplier provides a translation, the English text prevails. Supplier communicates with Customers in English or Dutch.
2.7 Where the provisions of chapter 7 of the Dutch Telecommunications Act (Telecommunicatiewet) that protect end-users, or the corresponding provisions of another member state implementing Directive (EU) 2018/1972 (the European Electronic Communications Code), apply to the Customer, for example because it is a micro or small enterprise or a not-for-profit organisation, those provisions apply and prevail over these Terms.
3. Who may become a Customer, and how the Agreement is concluded
3.1 Only businesses established in a member state of the European Union may become a Customer, and only if they have a VAT identification number that VIES confirms as valid. VAT numbers with the prefix XI (Northern Ireland) are not accepted. Supplier creates an Account only after VIES has confirmed the VAT number.
3.2 Signup takes place on the Website, in the following steps:
- (a) the applicant enters the company details, the VAT number and a contact e-mail address, and chooses the name of its sign-in address;
- (b) the applicant confirms the contact e-mail address through a link that Supplier sends to it;
- (c) the applicant creates the first Administrator account and accepts these Terms and the DPA on behalf of the business, and Supplier confirms the acceptance by e-mail;
- (d) Supplier checks the VAT number with VIES, starting as soon as the contact e-mail address has been confirmed, and, where VIES provides them, compares the company name and address with the details registered there;
- (e) Supplier creates the Account and sends a welcome e-mail.
The applicant can check and correct the information entered before submitting each step.
3.3 The Agreement is concluded when Supplier has created the Account. Supplier may refuse an application, in particular if VIES does not confirm the VAT number, if the details do not match those registered in VIES, if the VAT number is already used for another Account, including an Account that has been deleted, or if Supplier suspects abuse. If an application is held for review, a person at Supplier decides on it.
3.4 The person who accepts these Terms on behalf of the Customer confirms that he or she is authorised to bind the Customer.
3.5 Supplier keeps a record of the acceptance, including the versions of these Terms and the DPA that were accepted, the time, the IP address and the browser used.
3.6 The Customer ensures that the information it provides is correct and complete, and informs Supplier without delay of changes to its name, address, VAT number or contact e-mail address.
4. Account, Administrators and Users
4.1 Each Customer has one Account, unless Supplier agrees otherwise.
4.2 The Customer decides who may use the Service, creates the Mailboxes and appoints the Administrators. The Customer is responsible for all use of the Account, by its Users and by anyone who uses their credentials, and ensures that its Users comply with the Agreement.
4.3 Administrators sign in to the Customer Console with a password and a second factor: a one-time code from an authenticator app. They set up the second factor when they first sign in, and it cannot be switched off. Where Supplier offers this option, 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 ends earlier when the Administrator's password or second factor changes, when the Administrator forgets the browser in the Customer Console, or when Supplier switches the option off. Some actions, such as a change of the MX records of a Customer Domain through the Service (clause 11.8), require a new code, also in a trusted browser.
5. Trial
5.1 A new Customer can use the Service free of charge for 30 days from the creation of the Account, without providing a payment method. Supplier offers one Trial per Customer.
5.2 During the Trial, the Account can have at most 10 User Mailboxes, at most 10 shared, room and equipment mailboxes together and at most 3 verified Customer Domains, and the sending limits for the Trial apply (clause 9.2). Copying from another provider through the Service (clause 11.9) is limited to 20 GB in total for the Account. This limit on copying continues after the Trial until the Account is active and has been paid for and, where Supplier has planned to move the Account to an instance of its own (clause 13.7), until that move. Supplier carries out such a move within 30 days after the first payment; if the Account has not been moved by then, the limit on copying ends at that time.
5.3 Unless a payment method has been added, Supplier reminds the Customer by e-mail before the Trial ends. If the Customer has added a payment method in the Customer Console by then, the Service continues as a paid subscription when the Trial ends. Once it has added a payment method, the Customer can also end the Trial early; Fees are then due from that moment.
5.4 If no payment method has been added when the Trial ends, Supplier suspends the Account (clause 14), and no Fees are due for the period of that suspension. The Customer can resume the Account by adding a payment method before the Account is deleted; the Agreement then continues as a paid subscription, and the first Billing Period starts at that moment (clause 8.3). Without resuming the Account, the Customer can retrieve its Customer Data free of charge under clause 17.3. If the Account is not resumed, Supplier deletes the Account and all Customer Data as described in clause 16, and the Agreement ends at the deletion, unless the Customer has terminated it earlier (clause 15.2).
5.5 Supplier may change the conditions of the Trial for future Trials.
6. The Service
6.1 The Service provides business e-mail, calendars, contacts and tasks on the Customer's own domains, based on the open-source mailbox software grommunio. At the date of these Terms, it includes:
- (a) Mailboxes that Users can use with classic Outlook for Windows (through MAPI over HTTP), Outlook for Mac (through Exchange Web Services), phones and tablets (through Exchange ActiveSync), other mail apps (through IMAP and SMTP, encrypted with TLS on ports 993 and 465) and a webmail in a browser (clause 6.7);
- (b) shared mailboxes, and room and equipment mailboxes for scheduling, which Administrators create in the Customer Console, and the rights to a Mailbox that Administrators give to Users: Full Access, to open it; Send As, to send with its address; and Send on behalf, to send on its behalf. Room and equipment mailboxes do not accept or decline meeting requests by themselves: the requests wait in their inbox for a User with Full Access;
- (c) server-side rules, such as automatic replies and forwarding, subject to clause 9.6. An automatic reply has a text for senders within the Account and a text for other senders, which goes to nobody, only to the senders in the User's contacts, or to everyone, as the User chooses. The Service sends it at most once a day to the same sender. Automatic replies that leave the Account receive the Customer's disclaimers, but not its signatures and banners unless the Customer chooses otherwise;
- (d) delayed sending: outgoing messages wait for a period that the Customer can set (60 seconds unless the Customer chooses otherwise, at most 24 hours). Until a message is released, an Administrator can cancel it, and the sender then receives a notice with the message attached. A message cannot be called back once it has been released;
- (e) signatures, banners and disclaimers on outgoing messages, which the Customer designs in the Customer Console, filled in from the details of the User and the Customer, with images that are embedded in the message itself, and added according to rules that the Customer sets: signatures and banners under the newest text of a message, disclaimers at the bottom. They are not added to messages that a User's own app has signed or encrypted, to meeting invitations and responses, to reports such as delivery reports, to messages in Microsoft's TNEF format, to messages that already carry the DKIM signature of a domain outside the Account, or where adding them fails, in which case the message is sent without them. A message of a User of the Account that a server-side rule forwards or redirects receives only the disclaimer; a message of someone outside the Account that a rule forwards receives none of them, not even the disclaimer; and automatic replies receive by default only the disclaimer (clause 6.1(c)). They do not appear in the copy in the sender's Sent Items. When the Service signs a message with S/MIME (clause 6.9), it adds them first. For an Account that has not switched to them, the Service adds the footers of the earlier version instead: company-wide signatures filled in from the details of the User, which are not added to signed or encrypted messages, meeting invitations or delivery reports;
- (f) sending limits (clause 9.2);
- (g) filtering of incoming mail for spam and other unwanted mail (clause 10.2);
- (h) DKIM signatures on outgoing mail from verified Customer Domains, with keys that Supplier may replace (clause 11.1), the DNS records that the Service needs, which the Customer Console shows for each Customer Domain, and, at the Customer's choice, the creation of those records at the Customer's DNS provider (clause 11.8);
- (i) the Customer Console, in which Administrators manage Customer Domains, Mailboxes with their addresses and aliases, shared, room and equipment mailboxes and the rights to Mailboxes, delayed sending, signatures, banners, disclaimers and footers, messages waiting to be sent, S/MIME certificates, mobile devices, the setting for the notifications of the webmail, migrations from Microsoft 365, billing and Administrators, and can see a log of changes;
- (j) notifications from the webmail, also when the webmail is closed, on the devices on which a User turns them on, delivered by the push service of that device's browser: of new mail in the Inbox and in other folders that the User chooses, of reminders of appointments and tasks, and once a day of overdue tasks. A notification shows only that new mail arrived, or the time of an appointment or task, unless the User chooses on that device to see the sender and subject of messages and the titles and places of appointments and tasks, which then show on the device's lock screen, for at most 7 days after the User's last sign-in there. Mail that the spam filter has marked is not notified. The Customer can turn these notifications off for all its Users in the Customer Console;
- (k) copying mail, calendars and contacts from Microsoft 365 into the Mailboxes (clause 11.9);
- (l) S/MIME signatures on outgoing mail, with certificates that the Customer uploads for its Mailboxes (clauses 6.9 and 11.10); and
- (m) for phones and tablets that connect through Exchange ActiveSync: a list of the devices of each Mailbox, a device policy for the Account, and the remote wipe of a device that an Administrator orders, of the whole device or of the account only (clause 11.3(e)).
6.2 The Customer must use its own domain for e-mail. A domain can be used as a Customer Domain only after the Customer has proven that it controls the domain, by publishing a DNS record that Supplier specifies, or by letting the Service publish it (clause 11.8), which the Service checks at the domain's own name servers, or after Supplier has established in another way that the Customer controls the domain. Only one Account can verify the same domain. The address under althi.work that the Customer chooses at signup (such as yourcompany.althi.work) serves only for signing in, for connecting apps and for reaching the webmail; it is not an e-mail domain.
6.3 At the date of these Terms, the following limitations apply:
- (a) POP3 is not offered, and IMAP and SMTP are offered only with TLS from the start of the connection (ports 993 and 465), not on ports 143 and 587;
- (b) the new Outlook for Windows cannot connect to the Service as an Exchange account; it can add a Mailbox only as an IMAP account, without calendars and contacts, and it then reaches the Service through Microsoft's cloud (clause 11.6);
- (c) incoming mail from the internet that uses an address in a Customer Domain whose mail is delivered to the Service (clause 6.8) as the sender address in its envelope is refused. Systems outside the Service that send such mail to Mailboxes, such as a web shop, CRM system or scanner that sends through another provider, must instead send through an authenticated SMTP connection to the Service (port 465) or use another sender domain in the envelope;
- (d) a maximum message size applies;
- (e) the Service has no tool yet to export all Mailboxes at once (clause 17.1 describes how Customer Data can be exported);
- (f) the Service is not a backup or archiving service (clause 11.5);
- (g) the webmail of the Service (clause 6.7) has no server-side rules, no management of delegates or of the sharing of a User's own folders and calendar, no contact groups and no calendars of the User's own Mailbox other than its main calendar, and it exports only single messages and their attachments. Classic Outlook for Windows offers these functions, and so does grommunio-web for an Account that still has it. Rules that already exist keep working;
- (h) Full Access to a Mailbox cannot be limited to reading: in classic Outlook for Windows, through Exchange Web Services and in grommunio-web, it also allows sending with the address of that Mailbox;
- (i) in apps that connect through MAPI over HTTP or Exchange Web Services, a User can send with the address of another Mailbox of the same Account without having Send As or Send on behalf for it. The Service then ensures only that the sender address belongs to the Customer's own Customer Domains (clause 10.2(c)); and
- (j) incoming messages that the spam filter marks are delivered to the Inbox (clause 10.2(a)).
6.4 Supplier may offer optional add-ons, such as S/MIME certificates that a third-party certificate authority issues through the Service. An add-on shown as "coming soon" is not part of the Service. Before the Customer orders an add-on, Supplier informs it of the conditions that apply to it, including the terms of any third party that provides it and the data that third party receives. S/MIME signing with certificates that the Customer uploads itself (clause 6.1(l)) is part of the Service and is not an add-on.
6.5 Supplier may develop and change the Service, for example to improve it or to keep it secure. If a change materially reduces functionality that the Customer uses, Supplier announces it at least 30 days in advance, unless the change is needed for security or legal reasons. In both cases, the Customer may terminate the Agreement under clause 15.5.
6.6 Supplier performs the Agreement with due care, as a best-efforts obligation (inspanningsverplichting), unless the Agreement expressly promises a specific result.
6.7 Webmail. Depending on the Account, the webmail is the Service's own webmail at https://mail.althi.work, the webmail of the mailbox software, grommunio-web, at the Customer's sign-in address, or both. The Service's own webmail (the "webmail of the Service") offers mail, including the shared mailboxes to which a User has Full Access, automatic replies, calendars, contacts and tasks, and Users can install it as an app on computers, phones and tablets. It cleans the HTML of messages before it shows them, and holds back images and other content from the internet until the User chooses to show them (clause 10.2(f)). Where an Account has the webmail of the Service, the Customer's sign-in address leads to it; where an Account has only grommunio-web, the sign-in address leads to grommunio-web. Supplier may move an Account from grommunio-web to the webmail of the Service, and may end grommunio-web for an Account; because some functions of grommunio-web are not available in the webmail of the Service (clause 6.3(g)), clause 6.5 applies to such a change.
6.8 Customer Domains that are not live yet. A verified Customer Domain is live once its MX records point to the Service, which the Service checks at the domain's own name servers, or once an Administrator confirms in the Customer Console that its mail is to be delivered to the Service. Until then, mail that the Service sends to addresses in that domain, including Supplier's own notices, is delivered to the mail servers that its MX records name; mail from the internet for its addresses that reaches the Service is deferred; and mail from the internet that uses an address in that domain as the sender address in its envelope is accepted, so that Users who are still at the previous provider can keep exchanging mail with the Service. A live Customer Domain becomes not live again only when Supplier sets it back, or after an undo under clause 11.8(g), and only while its MX records do not point to the Service.
6.9 S/MIME signatures. Where an Administrator has uploaded an S/MIME certificate with its private key for a Mailbox and has turned on signing, the Service signs the outgoing mail of that Mailbox at the server, after adding signatures and disclaimers (clause 6.1(e)). Such a signature is applied automatically by the Customer's mail system: it shows that this system sent the message for that Mailbox, not that a person signed it, and Users who have Full Access or Send As for the Mailbox can cause it. It is neither an advanced nor a qualified electronic signature within the meaning of Regulation (EU) No 910/2014. The Service does not sign mail between the Customer's own Mailboxes unless the Customer chooses so, nor mail whose sender address differs from the address in its envelope, such as mail that a mail app sends through SMTP as another Mailbox or on its behalf, nor some other messages, such as mail that a server-side rule forwards or redirects, meeting invitations and responses, reports, automatic replies, messages that are already signed or encrypted, messages that would become too large, and mail of a Mailbox whose certificate has expired. If signing is temporarily not possible, the Service sends the message unsigned after a delay, unless the Customer has chosen to let it wait. The Service does not decrypt or encrypt mail.
7. Beta
7.1 The Service is currently offered as a beta version. Supplier announces the end of the Beta at least 30 days in advance, by e-mail or in the Customer Console. When the Beta ends, this clause 7 no longer applies.
7.2 During the Beta:
- (a) Supplier makes no commitment on availability or response times, and maintenance and updates may interrupt the Service more often than they will afterwards;
- (b) Supplier may change or remove functions at shorter notice than clause 6.5 provides, but announces a change that materially reduces functionality the Customer uses at least 7 days in advance, unless it is needed for security or legal reasons; clause 15.5 applies to such a change;
- (c) some functions are not yet available, such as a tool to export all Mailboxes at once;
- (d) support is provided on a reasonable-efforts basis; and
- (e) the automatic DNS setup (clause 11.8) and the copying from Microsoft 365 (clause 11.9) are new functions: the Customer checks their results, which the Service shows.
7.3 The Beta does not reduce Supplier's obligations regarding the security and confidentiality of Customer Data, the DPA, the notices and data rules of clauses 14 to 17, or the Customer's rights under clauses 15 and 22. The Service is not provided "as is": clause 19 on liability applies during the Beta as well.
7.4 The Customer can terminate the Agreement at any time under clause 15.2, during the Beta and afterwards.
8. Fees, invoices and payment
8.1 The Fees per Billing Period consist of:
- (a) a base fee, which includes up to five User Mailboxes;
- (b) a fee for each User Mailbox above five; and
- (c) the fees for the add-ons that the Customer has ordered.
A User Mailbox counts only while it is enabled. Shared, room and equipment mailboxes and disabled Mailboxes are free, within the limits of clause 9.8. The prices are those shown on the Website and in the Customer Console when the Agreement is concluded, as changed under clause 8.9.
8.2 All prices are in euros and exclude VAT.
8.3 Fees are charged monthly in advance. Fees are due on the first day of the Billing Period to which they relate, and other amounts on the due date stated on the invoice. The first Billing Period starts when the Trial ends or, if the Customer ends the Trial early or adds a payment method after the Account was suspended, at that moment. Supplier counts the User Mailboxes automatically after each change and once a day. A change in the number of User Mailboxes that stays within the five included in the base fee does not change the Fees. Supplier may charge for additional User Mailboxes and add-ons pro rata, immediately or with the next invoice, and credits a reduction against future invoices. Credits are not paid out, unless these Terms provide otherwise.
8.4 Payments are processed by Stripe. The Customer pays by card or SEPA Direct Debit and authorises Supplier to collect the Fees through Stripe from the payment method registered for the Account when they are due. The terms of Stripe apply to entering and storing the payment method.
8.5 Supplier issues invoices electronically only, and the Customer agrees to receive them electronically.
8.6 Supplier charges Dutch VAT (currently 21%) to a Customer established in the Netherlands. To a Customer established in another member state, Supplier invoices without VAT under the reverse-charge mechanism (article 196 of Council Directive 2006/112/EC), and the Customer accounts for the VAT in its own country. The Customer is responsible for the correctness of its VAT number. Supplier checks the VAT numbers of Customers outside the Netherlands with VIES again before renewals. If VIES no longer confirms the VAT number, Supplier charges the VAT that then applies from the next invoice, and may terminate the Agreement under clause 15.4 if the Customer does not provide a valid VAT number within 30 days.
8.7 If a payment fails or an amount is not paid when it is due, the Customer is in default without a notice of default being required. From the day after the due date, the Customer owes the statutory commercial interest (article 6:119a of the Dutch Civil Code) and compensation for the costs of collection (article 6:96 of the Dutch Civil Code) of at least EUR 40. If an amount is still unpaid 14 days after its due date, Supplier may suspend the Account (clause 14).
8.8 The Customer must raise objections to an invoice in writing within 30 days of the invoice date; after that, the invoice counts as accepted, unless the Customer could not reasonably have noticed the error earlier. An objection does not suspend the obligation to pay the undisputed part. The Customer may not set off amounts it owes against claims on Supplier, or suspend payment, unless Supplier has acknowledged the claim, a court has established it, or Supplier has been declared bankrupt or granted a suspension of payments.
8.9 Supplier may change its prices. Supplier announces a price increase at least 30 days before it takes effect, by e-mail or in the Customer Console. The increase applies from the first Billing Period that starts after that notice period. The Customer may terminate the Agreement under clause 15.5 before the increase takes effect. A price reduction may take effect sooner.
9. Acceptable use and sending limits
9.1 The Service is meant for the Customer's individual business correspondence. The Customer ensures that the Service is not used, by its Users or otherwise through the Account:
- (a) to send spam: unsolicited commercial communications without the consent that the law requires (including article 11.7 of the Dutch Telecommunications Act and the laws of other member states implementing article 13 of Directive 2002/58/EC), or other unsolicited bulk e-mail;
- (b) to send bulk e-mail, such as newsletters, marketing campaigns or other mailings sent in substantially the same form to many recipients, even if the recipients have agreed to receive them; a service designed for that purpose should be used instead;
- (c) to send or store malware, or for phishing, fraud or identity theft;
- (d) to forge or hide the origin of messages, or to use sender addresses that the User is not entitled to use;
- (e) to store or send illegal content, such as child sexual abuse material, terrorist content, content that infringes intellectual property rights, unlawful threats, discrimination or defamation, or personal data that is processed unlawfully;
- (f) to collect e-mail addresses without permission, or to send mail to purchased or rented address lists;
- (g) to get around the sending limits or other technical limits, for example by spreading mail over several Mailboxes or Accounts;
- (h) to disrupt, overload, scan or test the security of the Service or other networks, without Supplier's written permission;
- (i) to provide the Service to third parties other than its Users, without Supplier's written permission; or
- (j) in breach of the sanctions laws of the European Union or its member states.
9.2 To protect the Service and the reputation of its mail servers, Supplier applies sending limits to mail for recipients outside the Customer's own Customer Domains ("external recipients"), counted over sliding periods of 24 hours and of one minute. Mail between the Customer's own Customer Domains does not count. At the date of these Terms, the limits are:
| Limit | During the Trial | After the Trial |
|---|---|---|
| External recipients per sender address per 24 hours | 100 | 2,000 |
| External recipients per Account per 24 hours | 300 | 1,000 plus 500 per enabled User Mailbox (at least 1,500) |
| External recipients per message | 50 | 200 |
| Messages with external recipients per Account per minute | 10 | 30 |
Messages over the per-minute limit are delayed and delivered later. Recipients over another limit are refused, and the sender receives a delivery failure notice that explains the limit. While the Account is suspended, Users cannot send mail.
9.3 Supplier may change the sending limits. Supplier announces a general reduction at least 14 days in advance, unless an immediate change is needed to protect the Service. Supplier may raise the limits for an Account on request, and may lower them for an Account where there are indications of abuse or of a compromised Mailbox.
9.4 If Supplier reasonably suspects a breach of this clause 9, a compromised Mailbox or Account, or a risk to the Service or to the reputation of its mail servers, it may take measures that are proportionate to that risk, such as holding, delaying or refusing messages, cancelling messages that are waiting to be sent, lowering sending limits, blocking a Mailbox, stopping outgoing mail for the Account, or suspending the Account (clause 14). Supplier informs the Customer under clause 10.6.
9.5 Supplier may introduce limits on the storage space per Mailbox, announcing them at least 30 days in advance.
9.6 Supplier may limit or block the automatic forwarding of mail to addresses outside the Service where this is needed to protect the Service.
9.7 The Customer cooperates with Supplier in investigating abuse and in having the Service's mail servers removed from block lists, and bears the reasonable costs that Supplier incurs as a result of a breach of this clause 9 through the Account.
9.8 To protect the Service, an Account can have at most 100 shared, room and equipment mailboxes together, plus 2 for each enabled User Mailbox (during the Trial: 10, clause 5.2), and the number of Mailboxes that can be created per hour is limited. Supplier may raise these limits for an Account on request, and may change them as described in clause 9.3.
10. Content moderation, notices and complaints
This clause gives the information that Supplier provides under the Digital Services Act (Regulation (EU) 2022/2065).
10.1 Supplier has no general obligation to monitor the content that is stored in or sent through the Service, and does not actively search it for illegal content (article 8 of the Digital Services Act). Apart from the automated tools described in clause 10.2, Supplier does not check that content. Supplier applies the measures in clauses 9 and 10 diligently, objectively and proportionately, with due regard for the rights and legitimate interests of everyone involved, including freedom of expression and the confidentiality of communications.
10.2 Supplier uses the following automated tools:
- (a) Filtering of incoming mail. Incoming mail is checked by the open-source spam filter Rspamd. Among other things, it checks whether the sending server is listed on DNS-based block lists, whether the message passes sender authentication (SPF, DKIM and DMARC), and characteristics of the message itself, and it computes a score. For some of these checks, the filter consults outside block lists and reputation services, which receive only the items being checked, such as IP addresses, domain names, hashed e-mail addresses and links, and checksums, and never a readable copy of a message (DPA, Annex III). Depending on the score, a message is accepted, accepted with a spam marking, temporarily deferred (greylisting) or rejected; the sending server receives the reason for a rejection. A message accepted with a spam marking is delivered to the Inbox, with the marking in its header fields (X-Spam and X-Spam-Status). The Service does not move it to the junk folder; mail apps and rules that read these header fields can, and Users can move it themselves. The filter does not include an anti-virus scanner. No filter recognises all spam, phishing or harmful attachments, and a legitimate message may occasionally be marked or rejected.
- (b) Checks during delivery. Incoming mail for an address that does not exist is refused, and so is incoming mail from the internet that uses a domain hosted in the Service whose mail is delivered to the Service (clause 6.8) as the sender address in its envelope. Mail for an address that has been removed from an Account is refused for 32 days after its removal.
- (c) Controls on outgoing mail. Outgoing mail is subject to the sending limits (clause 9.2). Mail that mail apps send through SMTP is accepted only with a sender address of the User's own Mailbox, or of another Mailbox of the Account for which the User has Send As or Send on behalf. On every route, outgoing mail is accepted only with sender addresses in the Customer's own Customer Domains, except mail that a User or a rule forwards (clause 6.3(i)). Outgoing mail is not checked with outside block lists or reputation services, and Supplier does not scan it in order to block it on the basis of its content.
- (d) Signup checks. At signup, Supplier checks the VAT number with VIES, refuses contact addresses at disposable e-mail services, and checks that the domain of the contact address can receive mail.
- (e) Templates of signatures and disclaimers. When a template is saved, the Service keeps only an allow-list of HTML and removes other markup, such as scripts. This is a technical safety measure; the Service does not check what the template says.
- (f) Display in the webmail. Before the webmail shows a message, it removes active content, such as scripts, from its HTML, and holds back images and other content from the internet until the User chooses to show them; links whose text names another site than they lead to are shown only after the User confirms. The message in the Mailbox is not changed.
10.3 People at Supplier review the applications that the signup checks hold for review, notices and objections under clauses 10.4 and 10.7, and measures under clause 9.4 that go beyond a single message. Individual decisions of the spam filter on incoming messages are not reviewed by a person, unless the Customer asks for it.
10.4 Anyone may notify Supplier of content in the Service that he or she considers illegal, by e-mail to support@althi.digital. A notice should contain: an explanation of why the content is illegal; information that makes it possible to find it, such as the e-mail address concerned and the date, subject or message identifier of the message; the name and e-mail address of the person making the notice, except for notices about offences relating to child sexual abuse; and a statement that the person making the notice believes in good faith that the notice is accurate and complete.
10.5 Supplier confirms receipt of a notice, handles it in a timely, diligent, non-arbitrary and objective manner, and informs the person who made it of its decision, of whether automated means were used, and of the available means of redress.
10.6 If Supplier restricts the Service because it considers content illegal or contrary to these Terms, for example by refusing or cancelling messages, stopping outgoing mail, or suspending or terminating the Account, it gives the Customer a clear and specific statement of reasons, at the latest when the restriction takes effect. The statement describes the restriction and its duration, the facts and circumstances on which it is based, including whether it follows a notice under clause 10.4, whether automated means were used, the legal or contractual ground and why the content is considered illegal or contrary to these Terms on that ground, and the available means of redress (clauses 10.7 and 24). This does not apply where a competent authority has, on a legal basis, required Supplier not to inform the Customer, for as long as that requirement applies, nor to the decisions that the spam filter takes for the Customer on individual incoming messages (clause 10.2(a)).
10.7 The Customer, and anyone who made a notice, can object to a decision of Supplier under clause 9.4 or this clause 10 by e-mail to support@althi.digital within six months of the decision. A person at Supplier reviews the objection and informs the sender of the outcome without undue delay. This does not affect the right to go to court (clause 24).
10.8 If Supplier becomes aware of information that gives rise to a suspicion that a criminal offence involving a threat to the life or safety of persons has taken place, is taking place or is likely to take place, it promptly informs the law enforcement or judicial authorities of the member state concerned and provides all relevant information available (article 18 of the Digital Services Act).
10.9 support@althi.digital is Supplier's single point of contact for the authorities of the member states, the European Commission and the European Board for Digital Services, and for the recipients of the Service (articles 11 and 12 of the Digital Services Act). Recipients of the Service can also write to Supplier at Bargelaan 200, 2333CW Leiden. Supplier can be contacted in English and Dutch, and messages are read and answered by people.
11. Customer responsibilities
11.1 Domains and DNS. The Customer may add only domains that it owns or is authorised to use. The Customer publishes and maintains the DNS records that the Customer Console shows for each Customer Domain, such as the MX record, which names the MX host of that domain (a host name under althi.work derived from the name of the domain), and the SPF, DKIM, DMARC, autodiscover and autoconfig records, with its own registrar or DNS provider, or lets the Service make them there under clause 11.8. For most Customer Domains, the DKIM records point to keys that Supplier publishes in its own DNS zone; while they do, Supplier may replace those keys, keeping the previous key published for 7 days, and the Customer does not change these records while it uses the Service. The Customer is responsible for the consequences of the DNS changes it makes or confirms. Supplier is not responsible for the services of registrars and DNS providers.
11.2 Credentials. The Customer ensures that Users choose strong passwords, keep their passwords, authenticator apps and devices secure, and do not share them. Passwords for Mailboxes that are set in the Customer Console must have at least 10 characters, passwords that Users set themselves on the Website at least 12, and passwords of Administrators at least 12. The Customer keeps the access data that its Administrators create for its DNS provider secure (clause 11.8). The Customer informs Supplier without delay if it suspects that credentials have been compromised. Supplier may block a Mailbox or require a new password if it suspects a compromise.
11.3 Lawful use and information for Users. The Customer is responsible for Customer Data and for the lawfulness of its use of the Service. It informs its Users of the functions that concern them, in particular that Administrators:
- (a) can see, cancel and release messages that are waiting to be sent (including their sender, recipients and subject), can set new passwords for Mailboxes, and can see a log of changes;
- (b) can give other Users rights to a User's Mailbox: Full Access, which allows reading it and, in several apps, sending with its address (clause 6.3(h)), Send As and Send on behalf; can convert the Mailbox of a User who leaves into a shared mailbox that others then open; and can see who has which rights;
- (c) can set the details that signatures show, such as the User's name, job title and telephone numbers;
- (d) can upload, replace and export the S/MIME private key of a User's Mailbox, with which outgoing mail is then signed in the name of that Mailbox (clause 6.9). The User is notified of each export while the Mailbox is enabled, and where the key can also decrypt, whoever holds an export can read mail that others encrypt for the Mailbox (clause 11.10);
- (e) can see the phones and tablets that connect to a Mailbox and order their remote wipe; a full wipe resets the whole device to its factory settings, including the User's own data on it;
- (f) can turn off the notifications of the webmail for all Users (clause 6.1(j)), and can see in the log of changes the records of a User's choices to turn them on, change them or turn them off on a device; and
- (g) can connect the Microsoft 365 organisation of a previous provider and have the mailboxes of Users there copied into the Service (clause 11.9), and can have the Service invite Users to set a password;
and that, within the Account, Users see each other's name, address, job title and telephone number in the address book and each other's free/busy times in the calendar, but not those of other Accounts, except as Annex II of the DPA describes (Separation of customers). The Customer complies with the rules that apply to the monitoring of employees. The Customer also refers its Users to the Privacy Statement for the processing that Supplier carries out as a controller (clause 12.4).
11.4 Signatures, banners and disclaimers. The Customer is responsible for the content of the signatures, banners, disclaimers and footers that the Service adds for it, including the images and links in them and any information that the law requires in business correspondence, and ensures that it is entitled to use the logos and other images in them.
11.5 Own copies. The Service is not a backup or archiving service. The Customer keeps its own copies of Customer Data that it cannot afford to lose, and is responsible for keeping business records, including e-mail, for as long as the law requires.
11.6 Devices and software. The Customer is responsible for the devices, apps, networks and internet connections with which it uses the Service, and keeps them secure and up to date. Some apps do not connect to the Service themselves but through the cloud service of their maker. At the date of these Terms, these include Outlook for iOS and Android and the new Outlook for Windows: they reach the Service through Microsoft's cloud, which signs in with the User's password and keeps copies of the mail, under Microsoft's own terms and possibly outside the European Economic Area. Supplier lets Microsoft's servers connect for this purpose. The Customer decides whether its Users may use such apps, and is responsible for that choice (DPA, clause 7.2(f)).
11.7 Cooperation. The Customer gives Supplier the information and cooperation that Supplier reasonably needs to provide the Service.
11.8 Automatic DNS setup. An Administrator with full rights may let the Service create, change or remove the DNS records of clause 11.1 at the Customer's DNS provider, where the Customer Console offers this for that provider, with access data that the Administrator creates at the provider for this purpose. The following applies:
- (a) before each change, the Service shows the records it will add, change or remove, and it makes exactly that change, and only after the Administrator has confirmed it. Before it writes anything, it checks that the provider serves the zone of the Customer Domain. It never changes the name servers of a Customer Domain, and changes no records other than those of clause 11.1;
- (b) the Service changes the MX records of a Customer Domain, also in a first setup of a domain that does not receive mail anywhere yet, and undoes such a change, only in a step that the Administrator confirms with a new code of their second factor, and it shows which MX records it will remove. Once the domain's name servers show the new MX records, incoming mail for the domain is delivered to the Service (clause 6.8);
- (c) the Service uses the access data only during the setup session, for the changes that the Administrator confirms, and does not store it. Where the provider allows it, the Service ends the access itself after the last change (at the date of these Terms, at Amazon Web Services and Google Cloud). Otherwise, the Administrator deletes or revokes the access data at the provider afterwards, as the Service reminds them. The Administrator should create the narrowest access and the shortest validity that the provider offers, and remove Supplier's address from the provider's list of allowed IP addresses once it is no longer needed;
- (d) some providers only allow the Service to replace all records of a domain at once. The Service then reads the records first and writes them back with only the confirmed change, but records that the provider's programming interface does not show may be affected;
- (e) at some providers, a change is made record by record, and can therefore stop part-way. The Service then reads the records back, and shows and mails what they contain;
- (f) before it changes the MX records, the Service reads the Customer's own MTA-STS policy, if there is one, and does not make the change if that policy would make sending mail servers refuse the new MX host;
- (g) within 7 days after a change of the MX records through the Service, an Administrator can undo it once, with new access data and the second factor. The Service then restores the records that the change replaced, as far as they have not been changed since. Otherwise, the Customer restores records itself, with the old values that the history in the Customer Console and the notice of clause 11.8(h) list;
- (h) the Service checks the result at the domain's name servers and shows it, and informs the Customer's Administrators with full rights by e-mail of each change, including what changed and who confirmed it; these notices cannot be switched off; and
- (i) once the MX records of a Customer Domain no longer point to the Service, an Administrator can let the Service remove the records that the Service made at the DNS provider (clause 17.2). The Service never removes MX records: they are changed by the Customer or its new provider.
The Customer may let the Service act only in a DNS provider account that it is authorised to use, and remains responsible for its DNS, its account at the DNS provider and the scope of the access data. The automatic DNS setup is optional and free of charge.
11.9 Copying from Microsoft 365. An Administrator with full rights can have the Service copy mail, calendars and contacts from a Microsoft 365 organisation into Mailboxes of the Account, free of charge. The following applies:
- (a) the Customer connects the organisation by having an administrator of that organisation grant Supplier's application read-only access to it in Microsoft 365, unless that access is still granted from an earlier connection (clause 11.9(f)). That access covers all mailboxes and the directory of the organisation, not only the mailboxes that the Customer chooses to copy. The Service lists the users of the organisation, including its guests, with their mailboxes and folders, so that the Administrator can choose; it copies only the mailboxes that the Administrator assigns to Mailboxes, and changes nothing in Microsoft 365;
- (b) the Service accepts the connection of an organisation only if one of its domains is a Customer Domain that the Account verified through its DNS record, and Supplier may refuse an organisation from which another Account is still copying;
- (c) the Customer warrants that it is entitled to connect the organisation, also where it belongs to another legal entity, such as a business that the Customer has acquired, and that it has a legal basis for copying the mailboxes concerned, and it informs the Users and other persons concerned;
- (d) the Service creates the Mailboxes, aliases and rights that the Administrator sets, and can send each User an invitation to choose a password, to the address that the Administrator confirms;
- (e) not everything is copied. At the date of these Terms, tasks, server-side rules, archive mailboxes, automatic replies, permissions, attachments of calendar items, contact photos and contact groups are not, and deletions in Microsoft 365 after the last copy are not carried over. The Customer Console shows the details and a report per Mailbox;
- (f) when the Administrator has finished a migration, the Service stops using the access, and afterwards only asks Microsoft whether the access has ended. The access remains granted in Microsoft 365 until the Customer deletes Supplier's application there, as the Customer Console explains. As long as it remains granted, the Service can connect the organisation again for this Account without a new consent in Microsoft 365; another Account, also one that has verified one of the organisation's domains as a Customer Domain (for example after that domain has been removed from this Account or has lapsed and been registered by someone else), can connect it only after a Global Administrator or Privileged Role Administrator of the organisation has signed in at Microsoft for that Account's connection. The Customer therefore deletes Supplier's application in Microsoft 365 as soon as it has finished copying, and in any case before a domain of the organisation leaves the Account or lapses; and
- (g) copying is subject to the limit of clause 5.2.
11.10 S/MIME certificates and keys. Administrators can upload an S/MIME certificate with its private key for a Mailbox, replace and remove it, and export the private keys that Supplier holds for the Mailbox. The following applies:
- (a) the Customer uploads only certificates and keys that it is entitled to use for that Mailbox;
- (b) Supplier holds the private keys, sealed, in a separate component of the Service (DPA, Annex II), and uses them only to sign the outgoing mail of the Mailbox (clause 6.9) and to export them at an Administrator's request. Supplier's personnel cannot export them in Supplier's administration console; they can, however, create Administrators and reset their credentials (clause 12.3);
- (c) a private key whose certificate also allows encryption can also decrypt mail that others encrypt for the Mailbox, and anyone who obtains an export of it can read that mail. Supplier keeps such a key after it has been replaced, so that it can still be exported. Clause 13 of the DPA applies to such keys;
- (d) a replaced key that can only sign is destroyed at once. The keys of a deleted Mailbox are kept for 30 days, so that they can still be exported, and are then destroyed; all keys of the Account are destroyed when the Account is deleted; and
- (e) an export is protected with a password, which the Service gives once, in a separate step. Every export is recorded in the log of changes, and the Mailbox, while it is enabled, receives a notice of who exported a copy and when.
12. Customer Data, confidentiality and data protection
12.1 The Customer retains all rights to Customer Data. Supplier processes Customer Data only to provide the Service in accordance with the Agreement, and for its own purposes only as described in clauses 12.4 and 12.5. It does not use Customer Data for other purposes, such as advertising.
12.2 Supplier keeps the communications in the Service confidential (article 11.2a of the Dutch Telecommunications Act). The content of messages (their text and attachments), calendars, contacts and other Customer Data is processed automatically to deliver, filter and secure mail and to provide the other functions of the Service, such as delayed sending; adding signatures, banners, disclaimers, footers, DKIM signatures and S/MIME signatures; showing messages, previews of attachments and search results in the webmail; copying mail from another provider at the Customer's request; and producing the notifications that a User turns on. No person at Supplier reads or otherwise inspects that content, except:
- (a) at the explicit request of the Customer or of the User concerned, for example to solve a support request, and only to the extent needed for that request; or
- (b) where the law or a binding order of a competent authority requires it (DPA, clause 13).
12.3 To investigate and stop abuse, security incidents and breaches of clause 9, Supplier uses data about the messages concerned (such as sender, recipients, subject, time and number), the signals of its automated tools, and the messages that a person who reports abuse submits to Supplier; it does not read the content of messages in the Service for that purpose. Supplier's personnel can see the data about messages that is needed to operate and secure the Service, such as the sender, recipients and subject of messages that are waiting to be sent, and technical logs, and the data of an Account that the administration console shows, such as its Users, Mailboxes and their devices, certificates, the history of DNS changes and, for a migration, the users, mailboxes and folder names of the organisation it copies from. They can also take most actions of Administrators for an Account, including creating Administrators for it and resetting the password and second factor of its Administrators, but cannot export private keys in Supplier's administration console. These actions are recorded in the log of changes that the Customer's Administrators can see, and every export of a private key is notified to its Mailbox while that Mailbox is enabled (clause 11.10(e)). They use this access only to operate, support and secure the Service, or at the Customer's request, and are bound to confidentiality.
12.4 The DPA forms part of the Agreement. For Customer Data that consists of personal data, the Customer is the controller and Supplier the processor. Supplier processes personal data about the Customer, its contact persons and Administrators, and data about the use of the Service for security and abuse prevention, for its own purposes as a controller, as described in the DPA (clause 2.3) and the Privacy Statement. In case of conflict, the DPA prevails over these Terms as regards the processing of personal data.
12.5 Supplier may use anonymous, aggregated data about the use of the Service, such as numbers of messages, to operate and improve the Service. Such data does not identify the Customer or any person.
12.6 Each party keeps confidential the non-public information that it receives from the other party in connection with the Agreement and that it knows or should reasonably understand to be confidential, and uses it only for the Agreement. This does not apply to information that is or becomes public without a breach of this clause, or that a party must disclose by law or by order of a competent authority.
13. Availability, maintenance and support
13.1 Supplier strives to keep the Service available and monitors its components automatically, but does not guarantee that the Service will be available without interruptions or errors. During the Beta, clause 7 applies.
13.2 Supplier performs maintenance when needed. If planned maintenance is expected to interrupt the Service noticeably, Supplier tries to perform it outside office hours (Central European Time) and to announce it in advance. A move of the Account to an instance of its own (clause 13.7) is planned maintenance of this kind. Urgent maintenance, for example to fix a security problem, may take place without notice.
13.3 The delivery of e-mail also depends on networks and systems outside Supplier's control, such as the internet, DNS, and the mail servers and spam filters of recipients. Supplier does not guarantee that a message is delivered to or accepted by a recipient's mail server.
13.4 Supplier provides support to Administrators by e-mail at support@althi.digital, in English or Dutch, on Working Days and on a reasonable-efforts basis. Users contact their Administrators.
13.5 Supplier makes regular backups of its server and stores them, encrypted, on another server that it manages itself, in France, within the European Economic Area (DPA, clause 12.3). In addition, the Service keeps the two most recent nightly copies of the data of each instance of the mailbox software on the same server in Germany, 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. Supplier uses the backups and these copies only to restore the Service after an incident (disaster recovery), never for any other purpose. It does not promise that Customer Data can be restored from them, and is not obliged to restore individual messages or Mailboxes on request.
13.6 Supplier informs the Customer without undue delay of significant incidents that are likely to affect the provision of the Service, and of measures that the Customer can take itself in response to a significant cyber threat.
13.7 Instances. The Service runs the mailbox software in separate instances, each with its own database, on the same server. During the Trial, and until it is moved, an Account shares an instance with other Accounts and is separated from them logically. Supplier may move an Account that pays to an instance of its own. A move takes place at night, between 02:00 and 05:00 Amsterdam time, and Supplier announces it at least 18 hours in advance by e-mail to the Administrators with full rights and to the contact e-mail address, and in the Customer Console. During the move, the Mailboxes are unavailable for a few minutes, and incoming mail is held or deferred and delivered afterwards. Devices that were set up with the host name of the shared instance instead of the Customer's sign-in address must be set up again. An instance of its own is not a separate server: it shares the server, its network, the mail servers that send and receive mail, the spam filter, the Customer Console and the backups with the other instances.
14. Suspension
14.1 Supplier may suspend the Account:
- (a) if an amount is still unpaid 14 days after its due date;
- (b) when the Trial ends without a payment method (clause 5.4);
- (c) when the Agreement ends (clause 16);
- (d) in the cases of clause 9.4, or if the Customer otherwise seriously breaches the Agreement; or
- (e) where this is needed to comply with the law or a binding order of a competent authority.
14.2 Before a suspension under clause 14.1(a), Supplier informs the Customer by e-mail of the date on which the Account will be suspended.
14.3 While the Account is suspended:
- (a) Users cannot sign in to their Mailboxes or send mail, and messages that were waiting to be sent are not sent (their senders receive a notice);
- (b) incoming mail for the Customer Domains, other than Supplier's own notices under these Terms, is not delivered to the Mailboxes: it is refused or returned, and its senders receive a notice that it could not be delivered;
- (c) Administrators can still sign in to the Customer Console, for example to pay or to terminate the Agreement; and
- (d) copying from Microsoft 365 (clause 11.9) that has already started is not stopped by the suspension, within the limit of clause 5.2; Supplier stops it at the Customer's request.
14.4 A suspension for non-payment ends when the Customer has paid, and a suspension at the end of the Trial when the Customer has added a payment method. During a suspension under clause 14.1(a), the Customer remains liable for the amounts that were due when the suspension started, but Supplier charges no Fees for later Billing Periods; if the Customer resumes the Account, a new Billing Period starts at that moment. During a suspension under clause 14.1(b), no Fees are due (clause 5.4). During a suspension under clause 14.1(d), the Customer remains liable for the Fees.
14.5 Supplier is not liable for damage resulting from a suspension in accordance with this clause.
15. Term and termination
15.1 The Agreement is concluded for an indefinite period. Fees are charged per Billing Period.
15.2 The Customer may terminate the Agreement at any time, in the billing section of the Customer Console or by e-mail to support@althi.digital. 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 under clause 14.1(a) or (b), at once. Fees paid for the current Billing Period are not refunded, except in the cases of clause 15.5.
15.3 Supplier may terminate the Agreement with at least 60 days' notice, with effect from the end of a Billing Period.
15.4 Either party may terminate (dissolve) the Agreement in writing with immediate effect if the other party seriously breaches the Agreement and, where the breach can be remedied, has not remedied it within 14 days of a written notice; or if the other party is declared bankrupt, is granted a suspension of payments or ceases its business. Supplier may also terminate the Agreement with immediate effect if:
- (a) the Customer or its Users seriously or repeatedly breach clause 9;
- (b) the Customer provided incorrect information at signup, or is not, or no longer, a business that may be a Customer under clause 3.1;
- (c) the Customer does not provide a valid VAT number in the situation of clause 8.6; or
- (d) continuing the Agreement would be contrary to the law or to a binding order of a competent authority.
15.5 If Supplier announces a price increase (clause 8.9), a change that materially reduces functionality (clauses 6.5 and 7.2(b)), a material change of these Terms or the DPA (clause 22) or a new Sub-processor to which the Customer has objected (DPA, clause 6), the Customer may terminate the Agreement by notice before the date on which the change takes effect, with effect from that date, or, for a change that took effect without prior notice, by notice within 30 days after it took effect, with immediate effect. Supplier then refunds the Fees paid in advance for the period after the termination, pro rata. The same applies if Supplier terminates the Agreement under clause 15.3.
15.6 Termination does not affect amounts that are due for the period before the termination. What Supplier has performed before a termination or dissolution is not undone, and the amounts invoiced for it remain due, unless the Customer shows that Supplier was in default as regards that performance.
15.7 Provisions that by their nature are meant to continue after the end of the Agreement, such as clauses 8 (as regards amounts that are due), 10.7, 12, 16, 17, 19, 20, 23.4 and 24, remain in force.
16. Customer Data after a suspension or the end of the Agreement
16.1 When the Agreement ends, Supplier suspends the Account (clause 14.3), unless it is already suspended. The Customer should change the DNS records of its Customer Domains in good time, in particular the MX records, because incoming mail is not delivered while the Account is suspended.
16.2 About 30 days after the start of a suspension, Supplier may stop the instance of its own of the Account, where the Account has one (clause 13.7) ("hibernation"). The data stays where it is, and Supplier informs the Customer 7 days in advance. While the Account is hibernated, restoring access or resuming the Account may take longer.
16.3 183 days (about six months) after the start of the suspension, Supplier permanently deletes the Account, its Mailboxes and the Customer Data in them, including the Account's instance of its own, its records of migrations and its S/MIME keys, unless the Account has been resumed before then; the deletion is postponed where clause 17.3 requires it. Supplier warns the Customer by e-mail 30 days, 7 days and 1 day before the deletion. The Agreement ends at the deletion, if it has not ended earlier. Copies of Customer Data in backups, including the copies of clause 13.5, can remain for at most 365 days after the deletion and are put beyond use during that time, as described in the DPA (clause 12.3). Annex I of the DPA lists the few records that remain after the deletion, and for how long.
16.4 The Customer may ask Supplier to delete the Account and the Customer Data earlier. Supplier then deletes them within 30 days and confirms the deletion.
16.5 Deleted Customer Data cannot be recovered. Supplier is not liable for the loss of Customer Data that it deletes in accordance with this clause.
16.6 Supplier keeps the data about the Customer that it needs for its own purposes, such as invoices and VAT records, as described in the Privacy Statement.
17. Export of Customer Data and switching provider
17.1 While the Account is active, the Customer can export Customer Data itself at any time. Users can download all their e-mail folders with a mail app that connects through IMAP (such as Thunderbird or Outlook), save individual messages and their attachments from the webmail, and export calendars, contacts and tasks with the export function of Outlook or another compatible app. Administrators can copy the settings shown in the Customer Console, such as signatures and disclaimers, download the certificates of Mailboxes and the reports of migrations, and export the S/MIME private keys of Mailboxes, and the Customer can ask Supplier for an export under clause 17.4. While the Account is suspended, mail apps cannot connect; the Customer can then retrieve its data after the Account has been resumed, or under clause 17.3.
17.2 The Customer may switch to another provider, or to its own systems, at any time, by terminating the Agreement under clause 15.2. The notice period for starting the switch is the period until the termination takes effect, and is never longer than one month. With the termination, or before it takes effect, the Customer may tell Supplier that it wants to:
- (a) switch to another provider, in which case it gives Supplier the details of that provider that are needed for the switch;
- (b) switch to its own systems; or
- (c) have its Customer Data erased when the termination takes effect (clause 16.4).
In cases (a) and (b), the Service continues at the Customer's request for a transitional period of up to 30 calendar days after the date on which the termination would otherwise take effect. The Customer may extend the transitional period once, by notice before it ends, for a period that it considers more appropriate for its own purposes. 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 tells the Customer so within 14 Working Days of its request, explains why, and states an alternative transitional period of no more than seven months, during which the Service continues. If the Account is suspended under clause 14.1(a) or (b), the Service continues during the transitional period only once the Account has been resumed; the Customer can always retrieve its Customer Data free of charge under clause 17.3.
During the notice period and the transitional period, Supplier provides reasonable assistance to the Customer, and to third parties that the Customer authorises, such as its new provider; supports the Customer's exit strategy, including by providing all relevant information, such as the export options of clause 17.4 and the DNS changes that are needed, and, at the Customer's request, by removing through the Service the DNS records that the Service made at the Customer's DNS provider once the MX records no longer point to the Service (clause 11.8(i)); acts with due care to maintain business continuity and continues to provide the Service; gives clear information about known risks to continuity; and maintains a high level of security, in particular of Customer Data while it is being transferred and during the retrieval period of clause 17.3.
The Agreement ends when the switch has been completed, which is at the end of the transitional period unless the Customer confirms earlier that the switch has been completed, or, without a transitional period, when the termination takes effect. Supplier confirms the end of the Agreement to the Customer by e-mail.
17.3 While the Account is suspended, including after the end of the Agreement (clause 16.1), the Customer can retrieve its Customer Data free of charge until the Account is deleted (the retrieval period). At the Customer's request, made at any time during the retrieval period, 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. Where necessary, Supplier postpones the deletion under clause 16.3, 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 that restored access. During the retrieval period, Supplier may block the sending and receiving of mail, and may take other measures that are needed to keep the Service secure, such as requiring new passwords. Supplier keeps Customer Data as secure during the retrieval period as during the Agreement. This clause does not apply to the extent that a binding order of a competent authority prevents it.
17.4 The data and digital assets that can be exported in a switch (the exportable data) are exhaustively:
- (a) the contents of the Mailboxes: messages with their attachments and folders, calendars, contacts, tasks and notes;
- (b) the settings that Users manage for their own Mailbox, such as server-side rules and automatic replies;
- (c) the data about Users, Mailboxes, Administrators and Customer Domains, and the settings of the Account, that the Customer Console shows, such as names, addresses and aliases, the rights to Mailboxes, the blocks, rules, groups, company details and images of signatures, banners and disclaimers, footers, the delayed-sending period and the device policy for mobile devices;
- (d) the log of changes of the Customer Console, the history of the DNS changes made through the Service, the reports of migrations for as long as the Service holds them, the records of outgoing messages that the Service still holds (DPA, Annex I) and the DMARC aggregate reports received for the Customer Domains; and
- (e) the S/MIME certificates of the Mailboxes and the private keys that Supplier holds for them.
Messages are exported through IMAP in the standard format for e-mail messages (MIME); calendars, contacts, tasks, notes and rules through the export functions of compatible apps, in standard formats such as iCalendar and vCard where the app supports them. On request, Supplier exports free of charge within 14 days the data in (c) and (d) in a structured, commonly used and machine-readable format such as CSV or JSON, with images in their own format (PNG or JPEG), the data in (b) by hand in such a format as far as the Users' apps cannot export them, and the certificates in (e), with their chains, in PEM format. The private keys in (e) are exported by Administrators themselves in the Customer Console, in PKCS #12 format; Supplier's staff cannot export them in Supplier's administration console (clause 11.10(b)). Administrators can also download the reports of migrations as CSV or JSON. Supplier describes the procedures and methods for switching and exporting and their known limitations, and the data structures, data formats and standards in which the exportable data are available, in an online register at https://althi.work/switching, and keeps that register up to date.
The following data are specific to the internal operation of the Service and are, exhaustively, not exportable data, because exporting them would disclose Supplier's trade secrets or endanger the security of the Service: 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 (d), data that Supplier processes as a controller for its own purposes (clause 12.4) are not part of a switch; the Privacy Statement explains how data subjects can exercise their rights in respect of them.
17.5 Supplier charges no switching charges, no early termination penalties and no fees for exporting Customer Data, including when the Customer leaves after the Trial. During a transitional period under clause 17.2, only the Fees for the Service are due.
17.6 At the end of the retrieval period, when the Account is deleted under clause 16.3, or earlier at the Customer's request (clause 16.4), Supplier erases all exportable data and all other Customer Data in full from all active systems of the Service. This does not include the records that Supplier keeps for its own purposes as a controller (clause 12.4), such as the log of changes, which are erased as the Privacy Statement states, nor the bare record that an S/MIME key was destroyed, without its certificate or address, the entry of the deletion in Supplier's journal of deletions, without the address, or the identifier of a Microsoft 365 organisation that the Account connected, without anything that identifies the Account, which Annex I of the DPA describes. Copies in backups, including the copies of clause 13.5, follow the rotation of the backups: 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, never for any other purpose; if a backup or such a copy is restored, Supplier erases the data again (DPA, clause 12.3). Supplier confirms the erasure on request.
17.7 The infrastructure of the Service is Supplier's own server, which only Supplier manages and which is located in a data centre in Germany; the copies of clause 13.5 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. In addition, Supplier publishes the public DKIM keys of Customer Domains in its own DNS zone, which Cloudflare, Inc. hosts (DPA, Annex III, part A). Supplier is established in the Netherlands. The infrastructure is therefore subject to the jurisdiction of Germany and the Netherlands, the backups also to that of France, and the DKIM records at Cloudflare also to that of the United States. The DPA (clause 13) describes how Supplier handles requests from authorities for access to Customer Data. Supplier publishes this information, with a general description of the measures it takes against governmental access to Customer Data from outside the European Union that would conflict with Union or member state law, at https://althi.work/switching, and keeps it up to date.
18. Intellectual property and third-party software
18.1 All intellectual property rights in the Service, in the software developed by Supplier, in the Website and in the documentation remain with Supplier or its licensors.
18.2 Supplier grants the Customer, for the term of the Agreement, a non-exclusive, non-transferable right to use the Service for its own business purposes, and to let its Users use it. The Customer may not copy, decompile or modify the software of the Service, except to the extent that the law or an open-source licence allows it.
18.3 The Service uses open-source software, such as grommunio, Postfix, Rspamd, Traefik, MariaDB, Redis and, in the webmail, Mozilla's pdf.js. These components are subject to their own licences, and nothing in the Agreement limits the rights that those licences grant. On request, Supplier provides the information and source code that those licences require.
18.4 The Service is designed to work with common apps, such as Microsoft Outlook, Apple Mail and the mail apps of phones and tablets, but Supplier does not guarantee that it works with every app, device or version, now or in the future. Supplier is not affiliated with the makers of these apps or of grommunio. Microsoft, Microsoft 365, Outlook, Exchange and Exchange ActiveSync are trademarks of Microsoft Corporation, and Apple and Mac are trademarks of Apple Inc.; other names may be trademarks of their owners. They are used only to describe compatibility.
18.5 Supplier may use suggestions and feedback from the Customer freely.
19. Liability
19.1 Supplier's total liability for an attributable failure in the performance of the Agreement, for tort or on any other ground, is limited to compensation of direct damage, up to the amount of the Fees (excluding VAT) that the Customer paid for the Service in the 12 months before the event that caused the damage, with a minimum of EUR 500. A series of connected events counts as one event.
19.2 Direct damage means only:
- (a) the reasonable costs that the Customer had to make to bring Supplier's performance into conformity with the Agreement, unless the Agreement is dissolved;
- (b) the reasonable costs of determining the cause and extent of the damage, insofar as they relate to direct damage;
- (c) the reasonable costs of preventing or limiting damage, insofar as the Customer shows that they limited direct damage; and
- (d) the reasonable costs of restoring Customer Data that was lost or corrupted through an attributable failure of Supplier, for example from copies that the Customer keeps.
19.3 Supplier is not liable for indirect damage, including consequential damage, lost profit, lost savings, loss of goodwill, damage due to business interruption, damage resulting from claims of the Customer's customers or other third parties, and damage resulting from the delay of messages, including messages that the spam filter refused or marked. For the loss or corruption of Customer Data, Supplier is liable only for the costs in clause 19.2(d), within the limit of clause 19.1.
19.4 The limitations and exclusions in this clause 19 do not apply if the damage is caused by intent or deliberate recklessness (opzet of bewuste roekeloosheid) of Supplier's management. As regards Supplier's obligations concerning Customer Data, they also do not apply if the damage is caused by intent or gross negligence of Supplier.
19.5 Supplier is liable for an attributable failure only if the Customer gives Supplier a prompt written notice of default with a reasonable period to remedy the failure, and Supplier still fails after that period. The notice describes the failure as precisely as possible. No notice is needed if performance has become permanently impossible.
19.6 The Customer reports damage to Supplier in writing within 60 days after it discovered the damage or should reasonably have discovered it; a claim for damages that is reported later lapses. A claim for damages also lapses if the Customer has not brought it before the court within 12 months after it discovered the damage or should reasonably have discovered it.
19.7 The persons and businesses that Supplier engages in performing the Agreement may also invoke this clause 19.
19.8 Fines imposed by a supervisory authority are borne by the party on which they are imposed. This clause does not affect the liability of the parties towards data subjects under article 82 of the General Data Protection Regulation.
19.9 This clause 19 also applies during the Trial and the Beta.
20. Indemnity
20.1 The Customer indemnifies Supplier against claims of third parties, and the reasonable costs of defending them, that arise from Customer Data, from use of the Service through the Account in breach of the Agreement or the law, from the domains that the Customer uses with the Service, or from an organisation that the Customer connects for copying under clause 11.9, except to the extent that the claim is caused by Supplier, in particular by a breach of the Agreement or of data protection law by Supplier. Supplier informs the Customer of such a claim promptly and consults the Customer on the defence.
21. Force majeure
21.1 Neither party is liable for a failure caused by force majeure (article 6:75 of the Dutch Civil Code). Force majeure includes, insofar as the party concerned could not reasonably have prevented the failure or its consequences: failures of the data centre, the power supply, internet connections and other telecommunication networks; attacks such as distributed denial-of-service attacks despite reasonable security measures; failures of suppliers on which Supplier depends, such as certificate authorities, DNS providers, push services and payment service providers; the listing of the Service's mail servers on block lists by third parties, where the Customer has complied with clause 9; measures of authorities; and war, terrorism, epidemics, strikes, fire and flooding.
21.2 If force majeure lasts, or is expected to last, more than 60 days, either party may terminate the Agreement in writing with immediate effect. What has been performed before then is paid for.
22. Changes to these Terms
22.1 Supplier may change these Terms and the DPA for a valid reason, such as a change of the Service, of the law or its interpretation, or of the conditions of Supplier's own suppliers. The DPA can be changed only in accordance with the General Data Protection Regulation.
22.2 Supplier announces a material change at least 30 days before it takes effect, by e-mail to the contact e-mail address of the Customer or in the Customer Console, and explains what changes. Other changes, and changes that must take effect sooner because of the law, take effect on the date that Supplier announces.
22.3 If the Customer does not accept a material change, it may terminate the Agreement under clause 15.5, with effect from the date on which the change takes effect. If the Customer continues to use the Service after that date, it accepts the change.
22.4 The current versions of these Terms, the DPA and the Privacy Statement are published on the Website. Supplier keeps earlier versions available on the Website or provides them on request.
23. Other provisions
23.1 Assignment. The Customer may not transfer its rights and obligations under the Agreement without Supplier's written consent. Supplier may transfer the Agreement to a party that takes over the Service as part of a transfer of its business; the Customer hereby gives its cooperation to such a transfer in advance (article 6:159 of the Dutch Civil Code). Supplier informs the Customer of the transfer, and the Customer may then terminate the Agreement with immediate effect.
23.2 Subcontracting. Supplier may engage third parties to perform the Agreement and remains responsible for them. For Sub-processors (DPA, clause 1.4), the DPA applies.
23.3 Notices. Supplier sends notices to the contact e-mail address that the Customer provided at signup or notified later, or shows them in the Customer Console. The Customer keeps that address up to date and reads the mail sent to it. Notices to Supplier are sent to support@althi.digital. Messages about billing, security, suspension and deletion, the notices of DNS changes made through the Service (clause 11.8(h)), of moves to an instance of its own (clause 13.7) and of exports of S/MIME keys (clause 11.10(e)) are part of the Service and cannot be switched off.
23.4 Evidence. Supplier's records, such as logs and records of acceptance, serve as evidence, subject to proof to the contrary.
23.5 Entire agreement and order of precedence. The Agreement contains everything the parties have agreed about the Service. In case of conflict, the following order applies: (1) terms that the parties have agreed individually in writing; (2) the DPA, as regards the processing of personal data; (3) these Terms; (4) descriptions and prices on the Website and in the Customer Console.
23.6 Severability. If a provision of the Agreement is void or is annulled, the other provisions remain in force, and the parties replace the provision with a valid one that comes as close as possible to its purpose.
23.7 No waiver. If a party does not enforce a right, this does not mean that it waives it.
24. Governing law and disputes
24.1 The Agreement is governed by Dutch law. The United Nations Convention on Contracts for the International Sale of Goods (CISG) does not apply.
24.2 The parties first try to resolve a dispute by consultation. If that does not succeed, the dispute is decided exclusively by the competent court in the district in which Supplier has its registered office.