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, 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. 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 and sign-in records, 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 (section 3.5). For these purposes we are the controller. We never use the content of messages for our own purposes. The content of messages is processed automatically to deliver, filter and secure mail; 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), 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 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.
- 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)).
- 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, 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).
- Purpose: providing the Customer Console, securing sign-in, sending service messages (such as confirmations, reminders before the end of the Trial, payment reminders, and notices of suspension and deletion), and recording changes for security and accountability.
- 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, 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.
- 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.
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, 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 |
| Administrator accounts | Until the Administrator is removed or the Account is deleted |
| Sign-in sessions | Deleted when they end, at the latest after 12 hours |
| Sign-in attempts (successful and failed) | 24 hours |
| Records for rate limits (IP address or network, and for signups 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 | 2 years after the change |
| Records of errors and security events, including error reports from browsers | 90 days; grouped summaries of them while they are open and until 90 days after they have been resolved |
| Identifiers of the notifications that Stripe sends us about payments and subscriptions | 90 days |
| Technical logs, including the access logs of our web server | 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 |
| 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.
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. Our systems look up domain names through our own DNS resolver; only when that resolver is unavailable or cannot resolve a name do they 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. 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.
- 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. The notifications are encrypted, so these services cannot read their content.
- 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, and all Customer Data, run on our own physical server (bare metal), which only we manage, in a data centre in Germany (EEA). We store the backups of that server, encrypted, on another server that we manage ourselves, in France (EEA) (section 4). 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, has no access to it, and cannot read the data on it, because all of that data is encrypted with keys that we hold.
6. Cookies
6.1 On the Website and in the Customer Console, 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 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, at the Customer's sign-in address under althi.work, is provided by the mailbox software of the Service (grommunio). It 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 webmail), 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 Customer Data and our own systems for the Service stay in the EEA (section 5.3). Some recipients in section 5 are located outside the EEA, or may process data there:
- Stripe and Cloudflare may transfer personal data to the United States. These transfers are covered by the EU-US Data Privacy Framework where the recipient 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.
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, 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.
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.