Skip to content
work
Menu
Pricing Log in Start free trial
Home›Privacy Statement›Version 1.1

Privacy Statement

Version 1.1 · effective 22 October 2026

Previous versions

This is version 1.1, which is no longer in force. Read the current version (1.2)

Contents

  1. 1. Who we are
  2. 2. Our two roles
  3. 3. What we process, why and on what legal basis
  4. 4. How long we keep data
  5. 5. Recipients and location
  6. 6. Cookies
  7. 7. Transfers outside the EEA
  8. 8. Security
  9. 9. Your rights
  10. 10. Changes to this Privacy Statement

This Privacy Statement explains how Althi Digital Services B.V. processes personal data in connection with Althi.work, its hosted business e-mail service: when you visit our Website, sign up, administer an Account, sign in to the webmail, pay or contact us. It also explains which data we process on behalf of our Customers, and where to go with questions about that data.

1. Who we are

1.1 Althi.work is provided by Althi Digital Services B.V., Bargelaan 200, 2333CW Leiden, registered with the Dutch Chamber of Commerce (KvK) under number 60860448, VAT identification number NL854092031B02 ("Supplier", "we" or "us"). Capitalised terms, such as Customer, User, Administrator, Account, Service, Customer Data, Customer Console and Website, have the meaning given in our Terms of Service at https://althi.work/terms.

1.2 You can contact us about privacy at support@althi.digital, in English or Dutch. We have not appointed a data protection officer.

2. Our two roles

2.1 As a controller, we decide why and how personal data is processed for the purposes described in section 3: our Website, signups, customer Accounts, billing, security and support.

2.2 As a processor, we process Customer Data on behalf of our Customers: the e-mail, calendars and contacts in their mailboxes, and the accounts of their Users. The Customer is the controller of that data, and our Data Processing Agreement at https://althi.work/dpa applies. This includes what the webmail does with your mailbox, the copying of mail from Microsoft 365 at a Customer's request, the DNS changes that a Customer has us make at its DNS provider, and the delivery of notifications by the push service of your browser's maker; the Data Processing Agreement (Annex III) describes who receives what. If you use a mailbox on Althi.work that your employer or another organisation provides, or if you exchange e-mail with such a mailbox, that organisation decides how your data is processed, and it is the right place for your questions and requests. If you contact us, we forward your request to that organisation.

2.3 We also use some data about the use of the Service, such as logs, sign-in records, records of changes and records of consent, for our own purposes: to secure the Service, to prevent and investigate abuse, to enforce sending limits, to count mailboxes for billing and to comply with the law (sections 3.5, 3.8 and 3.9). For these purposes we are the controller. We never use the content of our Customers' messages for our own purposes. The content of messages is processed automatically to deliver, filter and secure mail and to provide the functions of the Service, such as adding signatures, disclaimers and S/MIME signatures, showing messages and previews in the webmail, copying mail from another provider at the Customer's request, and producing the notifications that a User turned on; no person at Supplier reads it, unless the Customer or the User concerned explicitly asks us to, for example to solve a support request, or the law requires it.

3. What we process, why and on what legal basis

We receive most of the data below from you. We also receive data from the Customer you work for (for example when an Administrator adds you as an Administrator or creates your mailbox), from VIES (the company name and address registered there), from Stripe (the status of payments and the type of payment method), from the systems of the Service (logs and records of events), and from people who report abuse or illegal content to us.

3.1 Visiting the Website

  • Data: your IP address, the time, and the host name, page and result of your request, recorded in the access logs of our web server; if a script error occurs in your browser, the error message, the page, the script and the place of the error in it, and your browser's user-agent string (the type and version of your browser and operating system).
  • Purpose: delivering and securing the Website, and fixing errors.
  • Legal basis: our legitimate interest in a working and secure Website (Article 6(1)(f) GDPR).

On the login page, we use only the domain of the e-mail address you enter, to find the sign-in address of your organisation; we do not store or log the address itself. The pages on which Users change their password or accept an invitation are described in section 3.8. The Website uses only the cookies described in section 6. We do not use analytics, advertising or tracking tools, and the Website loads nothing from third parties.

3.2 VAT lookup and signup

  • Data: company name, address and country; VAT identification number; name and e-mail address of the contact person; the chosen sign-in name; name and password of the first Administrator (we store the password only as a hash); the IP address and the browser's user-agent string; and the results of our checks.
  • Checks: we check the VAT number with VIES, the VAT Information Exchange System of the European Commission, and compare the company name and address with the details registered there. If you use the lookup function, we fill in the form with the details from VIES. We check that the contact e-mail address does not belong to a disposable e-mail service and that its domain can receive mail, and we note whether it belongs to a free e-mail service.
  • Returning businesses: to apply our rule of one Trial per Customer and to prevent fraud, we compare the VAT number with those of current and former Customers and of other signups. If the number is already in use, the person at Supplier who reviews the signup sees the name, sign-in name and status of the other Accounts and signups that use it, and for a former Customer the date on which its Account was deleted. For former Customers we use, for this purpose too, the administrative record that we keep under tax law (section 4).
  • Purpose: making sure that we contract only with businesses that have a valid EU VAT number, applying the correct VAT treatment, preventing fraud and abuse, creating the Account, and recording the acceptance of our Terms of Service and Data Processing Agreement.
  • Legal basis: if you sign up as a sole trader, taking steps at your request before entering into a contract (Article 6(1)(b) GDPR); otherwise our legitimate interest in concluding a contract with the business you represent (Article 6(1)(f)). For Customers, keeping evidence of the VIES checks is required for the correct VAT treatment (Article 6(1)(c); Article 18 of Council Implementing Regulation (EU) No 282/2011 and article 52 of the Dutch General State Taxes Act). For lookups and signups that do not lead to a contract, we keep that evidence on the basis of our legitimate interest in being able to show which checks we made and in preventing abuse (Article 6(1)(f)). Recognising returning businesses is based on our legitimate interest in preventing fraud and the repeated use of the Trial (Article 6(1)(f)).
  • Automated decisions: some checks decide automatically. A signup is refused if VIES says that the VAT number is not valid, if the contact address belongs to a disposable e-mail service, or if its domain cannot receive mail. A person at Supplier reviews a signup if the name or address does not match the details in VIES, if the VAT number is already in use, also by a former Customer, or if VIES remains unavailable for 7 days. If you think that a decision is wrong, contact us at support@althi.digital: a person will review it, and you can explain your point of view.

3.3 Customer Accounts and the Customer Console

  • Data: the company details of the Customer and its contact person; the name, e-mail address, role, password hash and encrypted two-factor secret of Administrators; sign-in sessions with IP address and the browser's user-agent string; sign-in attempts; the service e-mails we send (recipient, type, time and the details in the message); and the audit log of the consoles: who made which change, when and from which IP address. The audit log also records what Users do themselves, such as a password change on the Website, the acceptance of an invitation and their choices for notifications on a device (section 3.9), and, for changes of DNS records through the Service, the records before and after.
  • Purpose: providing the Customer Console, securing sign-in, sending service messages (such as confirmations, reminders before the end of the Trial, payment reminders, notices of suspension and deletion, notices of a planned move of the Account to an instance of its own, notices to all Administrators with full rights of DNS changes made through the automatic DNS setup, and notices to a User when an Administrator exports the S/MIME key of the User's mailbox), and recording changes for security and accountability.
  • Automatic DNS setup: if an Administrator uses it, we use the access data they enter for their DNS provider only during that setup, for the changes they confirm, and we do not store it.
  • Legal basis: performance of the contract where the Customer is a sole trader (Article 6(1)(b)); otherwise our legitimate interest in performing the contract with the Customer and in securing the Service (Article 6(1)(f)).

3.4 Billing and payments

  • Data: company name, address, VAT number and contact e-mail address; the subscription and the number of mailboxes; invoices and payments. Payment details are entered on Stripe's pages and processed by Stripe; we see only the type of payment method and, for example, the last digits of a card number.
  • Purpose: invoicing, collecting payments, applying the correct VAT treatment (including checking the VAT numbers of Customers in other member states again before renewals, and reporting cross-border services to the Dutch Tax Administration), and keeping our accounts.
  • Legal basis: performance of the contract (Article 6(1)(b)) or our legitimate interest in performing it (Article 6(1)(f)); our legal obligations under tax law (Article 6(1)(c)).

3.5 Security and abuse prevention

  • Data: IP addresses, records that count requests for rate limits, sign-in attempts and the places from which accounts signed in, technical logs, and records of errors and security events (in which e-mail addresses are replaced by their domain and a short hash). In case of abuse, also data about the messages concerned, such as sender, recipients, subject, time and number, the signals of our automated tools, and reports from third parties, including the messages they submit to us. We do not read the content of messages in the Service to investigate abuse. Section 3.8 describes the sign-in records of the webmail.
  • Purpose: protecting the Service, our Customers and others against attacks, fraud, spam and other abuse; enforcing the sending limits; investigating incidents; and keeping the Service stable.
  • Legal basis: our legitimate interest in a secure and reliable Service (Article 6(1)(f)); our legal obligations where they apply (Article 6(1)(c)).

3.6 Contact, support, notices and complaints

  • Data: your name and e-mail address, the content of your message and the information you provide; for a notice of illegal content, also the information described in clause 10.4 of our Terms of Service.
  • Purpose: answering questions, providing support, and handling notices and complaints, including under the Digital Services Act.
  • Legal basis: our legitimate interest in communicating with you and in handling notices and complaints (Article 6(1)(f)); performance of the contract where you are the Customer as a sole trader (Article 6(1)(b)); our obligations under the Digital Services Act (Article 6(1)(c)).

3.7 Data you must provide

The data that the signup form and the Customer Console mark as required are needed to conclude and perform the Agreement; the company details and the VAT number are also needed to comply with tax law. Without them we cannot create or administer an Account. Whether you give us other data, for example in a message to us, is up to you.

3.8 The webmail, and the pages for Users

Depending on your organisation's Account, its webmail is our own webmail at https://mail.althi.work, grommunio-web at your organisation's sign-in address, or both. What a webmail shows comes from your mailbox, which we process for the Customer (section 2.2). For signing in to our own webmail and for its security, we also process the following as a controller.

  • Data:
    • when you sign in: your e-mail address and password. We keep your password only in your session, sealed with a key that only your browser holds, so that the webmail can open your mailbox for you; we never store it in readable form;
    • your sessions: the IP address, your browser and operating system (from the user-agent string), your time zone and the times of sign-in and last use;
    • the sign-in log: every sign-in and renewed sign-in, with its time, its result, the organisation and mailbox, the IP address, the user-agent string and a keyed hash of your address (never the address itself);
    • known browsers: a random code in a cookie (section 6.2), of which we keep only a hash, linked to the mailbox, so that a browser in which you signed in before is recognised;
    • the places from which accounts signed in (an IP address or network), and records that count failed sign-ins for rate limits;
    • script errors in the webmail: the error message, the place of the error, the page and the version of the webmail, without your identity or your user-agent string;
    • on the Website's page for changing a password: your e-mail address, your current and new password, which we do not store (the mailbox software stores the new password as a hash), records that count attempts per address and per IP address for rate limits, and an entry in the audit log with your IP address when the password is changed;
    • on the Website's page for accepting an invitation, which an Administrator can have the Service send when the Customer moves to Althi.work: the invitation link, of which we keep only a hash, your name and new address, which the page shows, and an entry in the audit log with your IP address when you accept it. The password you choose is not stored by us; the mailbox software stores it as a hash.
  • Purpose: letting you sign in securely, letting you see and end your sessions (in our own webmail's settings, under Devices), limiting the guessing of passwords, recording changes for security and accountability, and fixing errors.
  • Legal basis: our legitimate interest in a secure and working Service (Article 6(1)(f)).

Our own webmail loads nothing from third parties and does not use analytics or tracking. Images from the internet in a message are shown only if you choose to show them; your browser then loads them directly from the sender's servers, which see your IP address. Section 6.2 describes what the webmail keeps in your browser.

3.9 Consent to notifications of the webmail

A User can turn on notifications of the webmail for each device. The moment new mail arrives is traffic data, which we use for these notifications only with the User's consent (article 11.5 of the Dutch Telecommunications Act). Before the browser asks for its permission, the webmail tells the User which push service delivers the notifications, in which country, and what that service receives.

  • Data: a record of each choice to turn notifications on, to change them or to turn them off on a device: a code for the device (not its push address), the push service, what the device is notified of, whether the sender and subject, and the titles and places of appointments and tasks, are shown, the version of the information shown, and the time.
  • Purpose: being able to show that, and on the basis of which information, consent was given, changed and withdrawn.
  • Legal basis: our legal obligation under article 11.5 of the Dutch Telecommunications Act (Article 6(1)(c) GDPR).

Turning notifications off on a device, removing the device or signing out on it withdraws the consent. These records are entries in the audit log of the Customer's Account, which its Administrators can see.

3.10 Captures of our own test mailboxes

  • Data: complete copies of the messages that one of our own test mailboxes sends, as the Service receives them, including their recipients, the text of earlier messages quoted in them and the header fields that name the sending app; the address of the test mailbox; and who started, stopped and downloaded a capture.
  • Scope: only test mailboxes in our own organisation on Althi.work, never a mailbox of a Customer; at most 5 at a time, each capture ending within 14 days. Mail sent to the test mailbox is not captured.
  • Purpose: testing how mail apps format messages, so that signatures and disclaimers are placed correctly. Our staff download the copies to their work computers and remove personal data from them; only copies without personal data are kept for testing.
  • Legal basis: our legitimate interest in a working Service (Article 6(1)(f)).

4. How long we keep data

Data Retention
Signups whose e-mail address was not confirmed Deleted after 48 hours
Signups that were not completed within 7 days after the e-mail address was confirmed, and rejected signups Deleted 90 days after they ended
Evidence of VIES checks, including lookups on the Website (VAT number, result, details registered in VIES, details entered, IP address and time) For Customers: 7 years after the end of the calendar year in which the check was made; for lookups and signups that did not lead to an Account: 90 days after the check
Records of the acceptance of the Terms of Service and the Data Processing Agreement (versions, time, IP address, browser, company and Administrator e-mail address) For Customers: as long as the Account exists, and 5 years after it has been deleted, as evidence of the contract; for signups that did not lead to an Account: deleted together with the signup
Company details and contact person of Customers, including their signup As long as the Account exists. When the Account is deleted, we delete them, except for an administrative record of the company (name, sign-in name, VAT identification number, address, country, the dates on which the Agreement started and ended, and the customer number at Stripe), which we keep for 7 years after the end of the calendar year in which the Account was deleted, and which we also use to recognise returning businesses (section 3.2)
Administrator accounts Until the Administrator is removed or the Account is deleted
Sign-in sessions of the Customer Console Deleted when they end, at the latest after 12 hours
Sessions of the webmail Until you sign out; a session ends after 12 hours without use and at the latest after 7 days; a session that was ended is kept 1 more day, so that your browser can show why
Sign-in log of the webmail 90 days
Known browsers of the webmail 90 days after the last sign-in from that browser
Sign-in attempts at the Customer Console and of apps (successful and failed), and the places from which accounts signed in 24 hours after the attempt or the last sign-in from that place
Records for rate limits (IP address or network; for signups the e-mail address; for password changes and the webmail a hash of the e-mail address) 2 days
Records of service e-mails sent, including alert e-mails to our own staff 90 days
Audit log of the consoles, including the entries of Users who act themselves, the records of DNS changes and the records of consent to notifications 2 years after the change or the choice
Records of errors and security events, including error reports from browsers and from the webmail 90 days; grouped summaries of them while they are open and until 90 days after they have been resolved
Captures of our own test mailboxes Until the capture ends, at most 14 days after it started; the copies that our staff download, until personal data has been removed from them, at the latest 14 days after the capture ended
Identifiers of the notifications that Stripe sends us about payments and subscriptions 90 days
Technical logs, including the access logs of our web servers (the access log of the mailbox software's web server records the path and query of each request and the user name of each request that signs in with a password, which is the mailbox address; for some phones and tablets, the query contains that address as well), and the request logs of the webmail Log files that are rotated by size: when a log reaches its maximum size, its oldest entries are removed automatically, so how long an entry is kept depends on the amount of traffic, and at the latest after 90 days
Invoices and other records that we must keep under tax law 7 years (article 52 of the Dutch General State Taxes Act)
Correspondence with us, including notices, complaints and reports of abuse, and the data about messages that we keep for a specific case of abuse As long as needed to handle the matter, and up to two years after it has been closed

We delete data earlier on request (section 9), unless we must keep it, for example under tax law, or need it to establish, exercise or defend legal claims.

We make regular backups of our server and store them, encrypted, on another server that we manage ourselves, in France (EEA). We keep each backup for 365 days and then overwrite or delete it, so data that we have deleted can remain in backup copies for at most 365 days after its deletion. During that time it is put beyond use: we use backups only to restore our systems after an incident (disaster recovery), never for any other purpose, and if we restore a backup, we delete the data that had been deleted again. The working data of the webmail (its sessions, sign-in log and limits) is not included in these backups. On the same server in Germany, we also keep the two most recent nightly copies of each instance of the mailbox software, to restore it quickly after a failure; they contain mailbox data that we process for our Customers, and the Data Processing Agreement (clause 12.3) describes them.

For the data that we process on behalf of Customers, Annex I of the Data Processing Agreement gives the retention periods.

5. Recipients and location

5.1 We share personal data only where this is needed for the purposes described in section 3:

  • Stripe processes payments and invoices for us; our contract is with Stripe Payments Europe, Limited (Ireland). For some purposes, such as fraud prevention and compliance with financial regulation, Stripe companies act as independent controllers; Stripe's privacy policy names them and explains how they process data.
  • Cloudflare (Cloudflare, Inc., United States) hosts the DNS zone of our domain althi.work, without routing our traffic through its network, and answers DNS queries for our host names. In that zone, it also publishes for us the public DKIM keys of our Customers' domains, under names derived from those domain names, and answers queries for the mail server names of those domains; for our Customers, it is our Sub-processor for this (Data Processing Agreement, Annex III, part A). Our systems look up domain names through our own DNS resolver; only when that resolver is unavailable or cannot resolve a name do some of them use Cloudflare's public resolver (1.1.1.1), which then receives the domain names being looked up, such as those of the mail servers to which we deliver mail and the domain in the sender address of an incoming message, which our receiving mail server checks. Our spam filter, and the checks of our Customers' domains at their own name servers, never use it. Cloudflare never receives the content of messages.
  • The European Commission and the tax authorities of the EU member states receive the VAT numbers that we check through VIES, and for Spanish VAT numbers also the company name and address entered.
  • The Dutch Tax Administration (Belastingdienst) receives the information that we must report, such as the VAT numbers of Customers in other member states and the amounts we invoiced to them.
  • Let's Encrypt (Internet Security Research Group, United States) receives the host names for which we need TLS certificates. Like all publicly trusted certificates, these are published in public Certificate Transparency logs.
  • Operators of DNS servers receive the domain names that our DNS resolver looks up, for example to find the mail server of a recipient or to check the sender of an incoming message. To check our Customers' domains, the Customer Console also asks those domains' own name servers, and those of their parent zones, directly.
  • Operators of block lists and reputation services receive what our spam filter checks in incoming messages: in clear, the IP address of the server that delivers a message and of earlier servers named in its headers, and domain names that appear in the message or its headers (for example Spamhaus, SURBL and URIBL); hashed e-mail addresses and hashed links (for example MSBL and the Rspamd project); and checksums of the text and attachments (the Rspamd project). They never receive a readable copy of a message, and we do not check outgoing messages with them. These operators are independent third parties.
  • The push services of browser makers (Google, Apple, Microsoft and Mozilla) deliver alert notifications to our own staff and the notifications of the webmail that a User turns on (Data Processing Agreement, Annex III, part C). The notifications are encrypted, so these services cannot read their content.
  • Microsoft, when a Customer copies its mail from Microsoft 365, and the Customer's DNS provider, when an Administrator uses the automatic DNS setup, receive our requests as providers of the Customer. Microsoft also receives your password and mail if you use Outlook for iOS and Android or the new Outlook for Windows, which reach our Service through Microsoft's cloud (Data Processing Agreement, Annex III, part D).
  • Authorities, where the law requires us to provide data.
  • Professional advisers, such as an accountant or a lawyer, where needed; they are bound to confidentiality.

5.2 We do not sell personal data and do not use it for advertising.

5.3 Our own systems for the Service run on our own physical server (bare metal), which only we manage, in a data centre in Germany (EEA), and we store Customer Data only there and in the backups of that server, which we store, encrypted, on another server that we manage ourselves, in France (EEA) (section 4). In addition, Cloudflare publishes the public DKIM keys of our Customers' domains in our DNS zone (section 5.1). The recipients in section 5.1 receive the data described there. The operator of a data centre in which one of our servers is located is not a recipient: it only provides space, power and network connectivity for that server, and it cannot access the data on it, because all of that data is encrypted with keys that we hold.

6. Cookies

6.1 On the Website, in the Customer Console and in the webmail, we use only cookies and similar technologies that are strictly necessary for the service you request. Under article 11.7a of the Dutch Telecommunications Act, they do not require consent. We do not use cookies or browser storage for analytics, advertising or tracking.

Name Where Purpose Duration
__Host-csrf Website Protects forms against cross-site request forgery Until you close your browser
__Host-signup Website Links your browser to your signup after you have confirmed your e-mail address, so that you can continue it and follow its status 14 days
__Host-console Customer Console Keeps an Administrator signed in Until you close your browser; the session ends after 30 minutes of inactivity and at the latest after 12 hours
billing-banner entries in session storage Customer Console Remember that you closed a billing notice Until you close the browser tab
legal-notice entries in local storage Customer Console Remember that you closed the notice about a new version of the Terms of Service or the Data Processing Agreement Until you clear your browser's site data

6.2 Webmail. The webmail at mail.althi.work keeps the following in your browser. All of it is needed for the webmail to work as you ask it to; none of it is used to track you, and none of it holds the messages in your mailbox: the message you are writing is kept only in that browser tab.

Name Kind Purpose Duration
__Host-wm cookie Keeps you signed in to the webmail; it also holds a key that protects your session on our servers Until you sign out; the session ends after 12 hours without use and at the latest after 7 days
__Host-wmd cookie Recognises a browser in which you signed in before, so that the limits on failed sign-ins for unknown browsers do not lock you out, and links your sessions and notifications to this browser 90 days after your last sign-in in that browser
wm-lang, wm-notify, wm-notify-seen, wm-active-at, wm-open-mailboxes, wm-badge local storage This device's choices: the language of the sign-in page; whether and how the webmail notifies you of new mail on this device, with a code for the user who chose it (not your address); which of your open tabs shows a notification; which shared mailboxes' folders are open; whether the app's icon shows the number of unread messages Until you clear your browser's site data
wm-compose, wm-after-login session storage The message you are writing, so that reloading the tab does not lose it; the page of the webmail to return to after you sign in Until you close the tab; the message also when you sign out
Service worker /sw.js and database wm-sw browser storage, only after you turn on notifications on a device where the browser can show them only this way (Android, and the webmail added to the Home Screen of an iPhone or iPad), or turn on notifications when the webmail is closed To show the webmail's notifications on this device; the database holds a code for the mailbox signed in on the device (not your address) and whether the app's icon shows the number of unread messages, and with notifications when the webmail is closed also a number for this device and a key that proves this device's changes and delivery confirmations, which cannot be copied off the device Until you turn notifications off on the device, sign out, or clear your browser's site data; the number for this device and its key already when you turn off the notifications when the webmail is closed
wm-push-device local storage, only after you turn on notifications when the webmail is closed The number of this device's notifications, a code for the mailbox (not your address), the version of the information you agreed to and which push service it named, and the language and time zone last given for them Until you turn these notifications off on the device, sign out, or clear your browser's site data
Push subscription made by your browser at your request, only after you turn on notifications when the webmail is closed This device's address at the push service of your browser's maker, to which our notifications are sent encrypted Until you turn these notifications off on the device, sign out, or clear your browser's site data

If you install the webmail as an app (Add to Home Screen, Add to Dock, Install), your browser or operating system keeps the app's name, icons and shortcuts; the webmail stores nothing more for that. The number of unread messages on the app's icon is shown by your device and not stored by the webmail. An e-mail address that a mailto: link passes to the webmail stays in your browser and reaches our servers only when the message is saved as a draft or sent.

Where your organisation still uses grommunio-web, at its sign-in address under althi.work, grommunio-web sets a session cookie and a cookie with a key that protects the session, which end when you close your browser, and three cookies that are kept for one year: lang (the language of grommunio-web), domainname (the domain of the address you signed in with) and webapp_title (your name and company, shown in the browser tab, also after you sign out).

6.3 When an Administrator adds a payment method or opens the billing portal, Stripe's pages are used. Stripe sets its own cookies there; see Stripe's cookie policy.

7. Transfers outside the EEA

7.1 We store Customer Data and run our own systems for the Service in the EEA; Cloudflare publishes the public DKIM keys of our Customers' domains (section 5.3). Some recipients in section 5 are located outside the EEA, or may process data there:

  • Cloudflare, Inc. is in the United States and is certified under the EU-US Data Privacy Framework, which covers the transfers to it. Stripe may transfer personal data to the United States; these transfers are covered by the EU-US Data Privacy Framework where the Stripe company concerned is certified under it, and otherwise by the standard contractual clauses of the European Commission. You can ask us for a copy of these safeguards at support@althi.digital.
  • Let's Encrypt receives only host names, which it needs to issue certificates and which become public in Certificate Transparency logs.
  • Lookups in DNS servers, block lists and reputation services may be answered by servers outside the EEA; they contain only the item being looked up or checked, such as an IP address, a domain name, a hashed address or link, or a checksum.
  • The push services of browser makers cannot read the content of the notifications. For the notifications of the webmail to Users, the Data Processing Agreement (Annex III, part C) names the basis of each transfer.
  • Microsoft and the DNS providers of our Customers are chosen by the Customer, and apps such as Outlook for iOS and Android by the Customer and its Users; the Data Processing Agreement (clause 7.3) describes these transfers.

7.2 E-mail that Users send to recipients outside the EEA is transferred on the instructions of the Customer.

8. Security

We protect personal data with appropriate technical and organisational measures, including full-disk encryption of our server, encrypted backups, encrypted connections, two-factor sign-in for Administrators, sessions of the webmail whose password only your browser's key can open, restricted administrative access and central monitoring. Annex II of the Data Processing Agreement describes these measures in more detail.

9. Your rights

9.1 You have the right to access your personal data, to have it corrected or deleted, to restrict its processing, and to receive it in a structured, commonly used and machine-readable format where we process it on the basis of a contract (Articles 15 to 20 and 22 GDPR).

Your right to object. Where we process your data on the basis of our legitimate interests (section 3), you can object at any time, on grounds relating to your particular situation (Article 21 GDPR). We then stop the processing, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or need the data to establish, exercise or defend legal claims.

9.2 You can send a request to support@althi.digital. We may ask you to confirm your identity. We respond within one month; if a request is complex, we may extend this by two months, and we inform you if we do.

9.3 For data in a mailbox of a Customer, the Customer is the controller (section 2.2): please contact that organisation. Users can also view, export and delete their own mail in the Service, and see and end their sessions in our own webmail.

9.4 You have the right to lodge a complaint with a supervisory authority, in particular in the EU member state where you live or work or where the alleged infringement took place. In the Netherlands, this is the Autoriteit Persoonsgegevens (https://www.autoriteitpersoonsgegevens.nl). We appreciate it if you contact us first, so that we can try to resolve your concern.

10. Changes to this Privacy Statement

We may change this Privacy Statement, for example when the Service changes. The current version is always available at https://althi.work/privacy. We inform Customers of material changes by e-mail.

Version 1.1 of the Privacy Statement, effective 22 October 2026: https://althi.work/privacy/v/1.1

work

Business email and calendar for EU companies.

support@althi.digital

Product

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

Legal

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

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

All prices exclude VAT.