This is a translation provided for convenience. In the event of any discrepancy between the language versions, the Dutch text prevails.
1. Data controller
Milo Moves B.V. is located at Stappenakker 10 03, 5124 RT Molenschot, the Netherlands. The company is registered in the Trade Register of the Netherlands Chamber of Commerce (KvK) under number 42097515 (establishment number 000066013976).
When are we responsible? For your account (signing in, two-factor authentication), the invoicing of your subscription, the security and logging of our service, the website, the newsletter, support requests and the usage data of the AI assistant (such as channel, time and usage), we decide ourselves why and how we use data. For those we are the data controller.
When do we work for a business? If you use Milo for your business, you put data about your customers, contacts and employees into your administration. For that data, and for what the AI assistant retrieves from your administration, the business is the controller and we are the processor. We then act on its instructions, under the data processing agreement.
For questions about privacy and requests about your personal data, you can reach us at support@milomoves.app.
2. Which data do we process?
Account and company details
When you register, we ask for your name, your email address and a password. We record which version of the terms and conditions and the data processing agreement you accepted and when, and that you declared that you use Milo as a business.
For your company profile we process your company name, address, phone number, email address, website, VAT number, Chamber of Commerce number and bank details. We need these details to set up your account and create invoices. We retrieve your address and your company's legal form from the Trade Register of the Netherlands Chamber of Commerce.
To secure your account, we process data for two-factor authentication and passkeys. In security logs we record important actions, such as failed login attempts and changes to access and integrations, together with your IP address and browser details. If you use the Milo API, we log your API requests with your IP address and, depending on the log level you choose, the content of the request and the response.
Usage data
For the website we use visitor statistics with your consent. We also process technical error data and load times to investigate faults. These are separate processing activities. Sections 6 and 9 list the services used for them.
For the AI assistant we also record usage data for running the service, monitoring costs, enforcing limits and preventing abuse. This data contains no message content, but it can be linked to a user or company ID. Data without message content is therefore not automatically anonymous.
Administrative and financial data
We process the data you put into your administration, such as customer and contact details, invoices, quotes, projects and time entries with a date and description. That data can include personal data of your customers and employees. We use it to provide the service, for example to email invoices, quotes and reminders to your customers on your behalf.
Payments
We do not process payment card details. You pay your Milo subscription through Mollie. If you connect your own Mollie account to Milo, we create a payment profile in that account with your company name. For each payment link we send Mollie the amount, the invoice number and an internal reference, and we receive the payment status in return. What your customer enters while paying is processed by Mollie itself. Milo only stores the payment status and the moment of payment. Mollie has its own privacy policy.
Communication data
If you contact us by email, we keep the correspondence so that we can help you. The same applies if you ask for support or send feedback through the assistant. You can then choose to share your conversation with the assistant. Support can view a shared conversation for 30 days. The retention periods are in section 4.
Sign-up list and newsletter
If you sign up on the website for messages about the launch of Milo or for the newsletter with new blog articles, we process your email address and the moment you signed up. These are two separate lists: you only receive the messages you signed up for yourself. You can unsubscribe at any time with the link at the bottom of every email.
Conversations with the AI assistant
Milo has an AI assistant that answers questions and can carry out administrative tasks. What you send to the assistant (your question, and with voice input the recording) is processed to give you an answer. With voice input, your recording is converted to text. We do not use the recording to recognise you by your voice.
Processing to give an answer is separate from storing conversation content. If you are signed in, we only store the conversation content on our AI server if you have given consent for that. Without that consent we still process your message to answer it, but we do not keep the content as conversation history on that server.
If you chat without signing in, for example on the website, in the knowledge base or through a chatbot that is not linked, we only store data about the conversation on our AI server, such as the channel and the time. We do not store the message content, your IP address or characteristics of your device.
The mobile app also keeps a local copy of your chat history, so that you can continue the conversation after a restart. The chat on the website, in the knowledge base and in the web app also keeps a copy of the conversation in your browser. This is separate from the consent for storage on the AI server. See section 9 for local storage.
Apart from the conversation content, we process data about the conversation, such as the channel, the time, the response time and the usage. For signed-in conversations, that data can be linked to your user and company ID. We use it for running the service, monitoring costs, enforcing limits and preventing abuse.
Section 5 explains how the assistant works and where your message goes.
Notifications through chat channels
You can link your Milo account to an available chat channel. For that link we process your phone number or chat ID. Linking does not switch on administrative notifications automatically: you choose per type of event whether you want to receive notifications. We record those preferences with your link. You can switch the notification preferences off and remove the link.
Push notifications on your phone
If you enable push notifications, we register a technical address for notifications (a push token) with your account, together with the platform and the app version. This lets us notify you, for example, that a quote has been accepted or a payment has been received. The notification does not mention a customer name or a document number: it says what happened, and when you tap it, the app opens the document. Delivery runs through Expo and the push services of Apple or Google, see section 6.
The mobile app remembers your notification preference per user on that device. When you sign out, the app deregisters the active push registration. If that fails because of connection problems, the app tries again. Your preference is kept. If you sign in again with the same account, the registration can be restored if notifications are still allowed on your device. You can switch notifications off in Milo or in the settings of your device. When your account is deleted, the app deletes the associated local preference.
3. Legal bases for processing
We process your data on the basis of:
- Performance of the contract: processing that is needed to provide the service.
- Legitimate interest: the security of the service, preventing fraud and abuse, and for the assistant cost monitoring and limits. Below, each processing activity states which interest we serve with it. You can object to this, see section 8.
- Consent: for visitor statistics, error reports and load times in your browser on the website, for storing your chat conversations on our AI server, and for messages about the launch of Milo and the newsletter. You can always withdraw your consent, as easily as you gave it. What we did with your consent before you withdrew it remains lawful.
- Legal obligation: keeping data that Milo itself is legally required to keep, such as the invoices for your subscription. Section 4 lists which data and periods this concerns.
What we do, why, and on which basis
- Creating an account, signing in, invoicing your subscription and answering questions to the AI assistant: performance of the contract.
- Retrieving data from the Chamber of Commerce to set up your company profile: performance of the contract.
- Answering support requests: performance of the contract.
- Error reports in the web app and the app, and administrative notifications and push registration that you switch on yourself: performance of the contract.
- Security logs and the log of API requests: our legitimate interest in being able to detect, investigate and stop break-ins into accounts and abuse of the API.
- Bot check at registration: our legitimate interest in keeping out fake accounts and automated sign-ups.
- Cost monitoring and limits of the AI assistant: our legitimate interest in keeping the use of the language models affordable within the subscription, and in limiting excessive use and abuse.
- Recording your acceptance of the terms: our legitimate interest in being able to show which version of the terms you accepted and which agreements applied.
- Storing conversation content of the assistant on our server: only with your consent.
- Visitor statistics, error reports and load times in your browser on the website: only with your consent.
- Messages about the launch and the newsletter: only with your consent.
- Keeping invoices for your subscription: legal obligation.
4. How long do we keep your data?
We keep account data for as long as you have an account. If you delete your account, your access stops immediately. Within 30 days after that, we permanently delete your personal data. If you are the only owner of the account, we also delete the account's administration within that period, including the data about your customers and employees.
As a business you generally have to keep your own administration for seven years. That obligation rests with you, not with Milo. So export your administration before you delete your account. After deletion, Milo only keeps data that we are legally required to keep ourselves, such as the invoices for your subscription, and no longer than the law requires.
The following periods apply to data on our servers. Local storage on your device or in your browser is described in section 9.
| What | Retention period |
|---|---|
| Conversation content on the AI server when using the web app or mobile app, if you allowed server storage | 90 days after the last activity in the conversation |
| Conversation content on the AI server through a linked chat channel, if you allowed server storage | 30 days after the last activity in the conversation |
| Data about conversations without signing in, such as through the website, the knowledge base or a chatbot that is not linked | 30 days after the last activity in the conversation |
| Buttons in a notification (for example "create draft invoice") | 30 days after the button expired |
| Handled notification records through chat channels | 90 days after receipt of the event, once processing has completed or failed |
| Withdrawn consent for notifications | 365 days after the last change to the withdrawn consent |
| Handled confirmations and customer choices in a conversation | 24 hours after handling or after they expired |
| Your link with a chat channel | Until you remove the link |
| Daily totals of usage, costs and limits of the assistant | 90 days. After that we only keep totals that can no longer be traced to a user or company. |
| Delivery records of push notifications | 30 days after creation |
| Disabled push tokens | 90 days after they were disabled |
| Push tokens of devices that have not checked in for 30 days | We disable them after those 30 days and erase them 90 days later |
| Email, support requests and feedback | 12 months after they have been handled |
| Security logs | 12 months |
| Log of API requests | The period you choose in your API settings: 7, 30 or 90 days (30 days by default) |
| Record of your acceptance of the terms | As long as your account exists, and 12 months after that |
| Emails you send to your customers through Milo (content and delivery data at the mail provider) | 45 days |
| Your email address on the sign-up list for the launch or for the newsletter | As long as you are signed up. If you unsubscribe, we only keep your email address with a note that you unsubscribed, so that you receive no more email from us. If you want that erased as well, email support@milomoves.app. |
| Error reports and load times in Sentry | 30 days |
| Backups of your administration | 7 days |
| Backups of the AI server | 7 days for the backup of the whole server; of the conversation database the last 14 copies are kept |
We store the content of a push notification encrypted. We erase that content as soon as Expo accepts the notification or delivery fails permanently.
A deletion also applies to backups: they disappear within 14 days through the normal course of the backup cycle. If we have to restore a backup, we carry out your deletion again afterwards.
If a user deletes their account in an administration with several users, we delete their account data. The business's administration remains, because it belongs to the business.
5. The AI assistant
Notice that you are talking to an AI
At your first contact with the assistant, we tell you that you are talking to an automated system and not to an employee, and that answers can contain errors.
Processing by external providers
To answer your question, we send your message and relevant earlier messages to a language model of an external provider. Depending on your question, data that the assistant retrieves from your administration is sent along as well, such as customer names, invoice lines, amounts and quote details. This can be data you did not type into the chat yourself, including personal data of your customers.
Which provider carries out the processing depends on the task and on availability. During one conversation, several providers can receive data, for example when another provider summarises an answer or takes over during an outage. The providers are OpenAI and Anthropic. As a last fallback, the processing can take place on our own server.
If you use voice input, the recording itself goes to OpenAI to be converted to text.
To answer questions about Milo, we search our own knowledge base. For that, your question is first converted at OpenAI into a mathematical representation that lets us find similar texts.
OpenAI and Anthropic do not use data that comes in through their API to train their models. OpenAI keeps messages and search queries for at most 30 days to detect abuse, and does not keep voice recordings. Anthropic erases messages and answers within 30 days, unless they indicate a violation of Anthropic's usage rules. Anthropic can keep those for up to two years.
Actions on your behalf
At your request, the assistant can directly create a draft invoice, draft quote or time entry. For sending or deleting documents, changing an invoice status and certain bulk actions, the assistant first asks for confirmation. It also asks for confirmation before creating a customer, customer group, project or catalog item. Check the proposed data before you confirm.
The assistant has the same rights as you. What you are not allowed to do in Milo, the assistant cannot do on your behalf either.
Automated decision-making and profiling
We do not make decisions about you based on automated processing, and we do not use the assistant to assess or profile your behaviour.
6. Sharing with third parties
We do not share your data with third parties for commercial purposes. To run Milo, we use the services and recipients below. Most of them work as a processor on our instructions. Where a party is itself responsible for what it processes, this is stated.
For this website (milomoves.nl) and the knowledge base
- Vercel: hosting of the website, with our server code running in Frankfurt, and with your consent visitor statistics without cookies
- Cloudflare: delivery of the support chat and the knowledge base
- Sender: management of the sign-up list for the launch and of the newsletter, and sending those messages (storage within the EU)
- Postmark: sending the confirmation email
- Sentry: error reports and load times, on servers within the EU. In your browser only with your consent. Errors and load times on our own server are always reported, without email addresses.
For the web app and the API (milomoves.app)
- DigitalOcean: hosting in Amsterdam. Documents you create in Milo are stored on those same servers.
- Postmark: sending emails from Milo, such as account emails and the invoices, quotes and reminders you send to your customers
- Mollie: payment of your subscription and, if you connect your own Mollie account, processing of payments by your customers. Mollie is itself responsible for those payments, including what the payer enters while paying.
- Netherlands Chamber of Commerce and the European VIES register: checking Chamber of Commerce and VAT numbers. They process that data for their own legal task and are themselves responsible for it.
- Cloudflare: bot protection at registration. Cloudflare receives your IP address for that.
- Sentry: error reports, on servers within the EU
For the mobile app (iOS and Android)
- Expo: processing of push tokens and notification content for delivery through the push services of Apple and Google, and the updates of the app. At every start, the app checks through Expo whether there is an update. Expo then sees your IP address and a random number that the app creates itself, even if you have notifications switched off. For that technical data about the use of its service, Expo is itself responsible.
- Apple Push Notification service and Google Firebase Cloud Messaging: delivery of push notifications to your device
- Sentry: technical error diagnostics. The mobile app only sends errors in the app itself, no crash reports or sessions, and does not track which screens you visit. Screenshots, breadcrumbs and performance tracing are switched off.
For the AI assistant
- OpenAI: language models, conversion of speech to text and making the knowledge base searchable, processing in the United States
- Anthropic: language models. Anthropic stores data in the United States and can process it in the United States, Europe, Asia and Australia.
- Cloudflare: secures and forwards the traffic between your app or browser and our AI server
- DigitalOcean: hosting of our AI server in Amsterdam
- Sentry: error reports from the AI server, on servers within the EU
For notifications and conversations through chat channels
- Meta (WhatsApp): receives your messages and voice recordings if you chat with the assistant through WhatsApp, and delivers the notifications you have switched on. For that, Meta processes your phone number and the content of the message. A notification can contain the name of your customer, a document number and a link to the invoice. Meta may process certain personal data as an independent controller, to the extent necessary for the safety, security and integrity of the WhatsApp Cloud API, including to detect, remove, report and take enforcement action against violations of the Cloud API terms and Meta's policies.
Data processing agreements and transfers outside the EEA
With parties that work as a processor for us, we have a data processing agreement. For Apple's push service that is not the case: Apple does not offer a data processing agreement for that service. A push notification therefore contains no customer names or document numbers.
If we work with a party that is established outside the European Economic Area, or that can access data from there, we only transfer data if appropriate safeguards apply: the EU-US Data Privacy Framework, the standard contractual clauses of the European Commission, or both. With most parties, the standard contractual clauses are also part of the agreement, so that they continue to apply if the certification under the Data Privacy Framework lapses. Apple is not in the Data Privacy Framework; for Apple, the standard contractual clauses from Apple's privacy policy apply. Which safeguard applies per party is listed in annex 2 of our data processing agreement. You can request a copy at support@milomoves.app.
7. Security
We take appropriate technical and organisational measures to protect your data. See our security page for more information.
Signing in and unlocking on your device
The mobile app stores session tokens in the secure storage of iOS or Android. On a suitable device, you can protect a signed-in session with Face ID or another available biometric method. That check is done by the operating system. Milo does not receive any facial or fingerprint data.
When you sign in with a passkey, our server verifies a cryptographic proof. Milo does not receive any biometric data or the private key of your passkey.
8. Your rights
Under the GDPR you have the following rights:
- Right of access: you can ask which data we hold about you.
- Right to rectification: have incorrect data corrected.
- Right to erasure: request the deletion of your data.
- Right to restriction: have processing temporarily restricted.
- Right to data portability: receive your data in a machine-readable format.
Objecting
If we process your data on the basis of legitimate interest, such as for security, cost monitoring and preventing abuse, you can always object because of your personal situation. We then stop that processing, unless we have compelling legitimate grounds that outweigh your interests, or need the data in a legal dispute. You can always object to the use of your data for direct marketing. We then stop immediately.
Exercising your rights
These rights also apply to your conversations with the assistant, your links with chat channels and your push registrations. For an access request, we provide the data the request concerns in a readable file format. For an erasure request, we also include the data in the AI and notification services. Data that Milo itself is legally required to keep is retained for as long as the law requires.
You delete your account through Settings → Delete account in the mobile app or through your profile in the web app. Your access stops immediately. The further deletion follows the periods and exceptions in section 4. If you can no longer sign in, send a request from the email address of your account to support@milomoves.app.
Does your request concern data in the administration of a business that uses Milo, for example because you are a customer of that business? Then that business is responsible for your data. Preferably send your request directly to that business. If you send it to us, we pass it on to the business if you tell us which business it concerns, and we let you know that we have done so.
Send a request to support@milomoves.app. We will inform you without undue delay and at the latest within one month of receipt about how it was handled. If an extension is needed because of the complexity or the number of requests, we will tell you why within that month. The period can then be extended by at most two months.
10. Complaints
If you have a complaint about how we handle your data, you can lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) at autoriteitpersoonsgegevens.nl.
11. Changes
We may update this privacy statement from time to time. If we want to use your data for a new purpose, we will let you know by email in advance. We also announce other material changes by email. The current version can always be found at milomoves.nl/privacyverklaring.