Privacy statement
Last updated: 21 October 2026
Who we are
Dorelli Cloud (dorelli.cloud) builds, hosts and maintains websites and apps for customers. Dorelli Cloud is a trade name of Uitgeverij Doreleijers. For privacy questions, contact support@dorelli.cloud.
What data we process
When you submit a request: your name, email address and message. As a customer: your login details (email and an encrypted password), your support tickets and the technical statistics of your website (availability, response time, visitor counts). When you sign up we ask whether you are a private person or a business and in which country you live or are based; for a business also the company name, the registration number, the VAT number and the billing address. In that form and in the portal we suggest the country that Cloudflare derives from your IP address. We don't store that country unless you confirm it yourself by sending the form, and you can always change it. If you ask us to register a domain name, also the name, address and phone number of the holder, which we pass on to the registrar. If you publish a trial site, the “Trial sites” section below applies as well. We never collect more than necessary.
Trial sites
If you publish a site on a dorelli.cloud subdomain — through the upload form, a template, the command line or our GitHub Action — we process your email address and the files you supply. The email address is needed to send you the management link and to warn you before the trial period ends; it is used for nothing else. We keep an encrypted form of your IP address for at most an hour, only to cap the number of attempts per hour. After that we delete it, and we never store the address itself. Only the recovery copy of our database still holds that form for up to 35 days. The management key is stored hashed, so we cannot read it ourselves. We remove the stored location from photos before they go online.
Abuse screening
Before a site becomes reachable for the first time, and at every new publication, we have the text of its pages checked automatically for abuse (phishing, fraud, illegal content). As long as a website is with us, we do that again every day, also after you have paid and when it is paused. If someone reports the site to us, we check it again right away. We host those sites, often under our own domain, so we want to know what goes on them. For that check the text goes to Anthropic (see “Sub-processors”): the visible text, the page title, the texts in form fields, the text of .txt, .svg and .xml files and the rules from a _redirects file, together roughly 12,000 characters at most. Before that come the names of the fields and the addresses the pages load or that forms and scripts send to, roughly 3,000 characters at most. Images, the rest of the scripts and styling are not sent. If that text contains names or other personal data, as in customer reviews, they go along. A trial site nobody has claimed yet closes right away when it is rejected. A claimed or paid site only goes offline without a human for evident phishing or malware: in a new version after one verdict, at the daily check or after a report only when two extra checks confirm it. The owner is then told and can respond. In all other cases a human decides. So only put other people’s personal data on your site if it may be public there.
Apps and databases
If your application runs in a container with us (App and Platform plans), we process what your app stores in its database and storage on your behalf: you are the controller, we are the processor (see the data processing agreement). That data lives in Microsoft data centers within the EU (Amsterdam region for containers and storage, Dublin region for databases). On first start we have the start page of your app screened automatically for abuse, in the same way as websites: the text of the page, without scripts and styling, goes to Anthropic. Secrets you enter in your portal (for example API keys) are stored with Microsoft and not shown again; technically we can retrieve them, and we do so only at your request or to resolve an incident. To bill usage we record per day how much compute, memory, requests, traffic and storage your building blocks used; those are quantities, not content.
Contact forms on customer sites
If a site we host has a contact form, those messages travel through us to the owner of that site, as email through Cloudflare. We do not keep the content: we forward it and it is then gone from our systems. What we do record briefly is that something was sent (which site, a hashed form of the IP address, the time), solely to block spam; that is deleted automatically after two days. For those messages the site owner is the controller and we are the processor.
Support and email
When you ask a question through the form, by email or from your portal, it becomes a ticket. Mail to support@dorelli.cloud and abuse@dorelli.cloud arrives through Cloudflare Email Routing, which delivers it to us; Cloudflare is already a processor (see “Sub-processors”). We keep the subject, the text and your email address, plus the names and sizes of attachments; we do not store the attachments themselves. A satisfaction score after closing is anonymous: we keep the number and your comment, not linked to your name. For a support question or an abuse report, our assistant drafts something: a reply or an assessment. For that the content of the ticket and the details of the site it concerns go to Anthropic, and for a report also the text of that site. That assistant works with Claude through a subscription with Anthropic. Anthropic's terms for that subscription apply, not a data processing agreement with us; the setting that lets Anthropic use conversations for training is off, and Anthropic then keeps them for 30 days. A human reads a draft reply before it is sent. If your domain name gets stuck, for example because your choice is taken or your nameservers have not been changed yet, the same assistant writes you an email; for that your domain name (or your choice), the name of your site, your plan and your language go to Anthropic. That email reaches you without a human in between, as a ticket you can reply to. We keep the assistant's work logs, with the content of the task, for 30 days on our own server. The chat assistant on our site works through Anthropic's business service: what you type goes there, and if you are logged in also the names, plans, status, expiry date and domains of your sites, so the answer is about your situation. A chat answer is always recognisable as AI. We keep the conversation for 90 days; if you ask for a human, it becomes a ticket and the term for tickets applies.
What we use it for
Solely to handle your request, publish, host and monitor your website, provide support and invoice you. We use your country and whether you are a private person or a business for the right VAT rule on your invoice, for your right of withdrawal, and so as not to deliver to countries under sanctions. We check an EU VAT number with VIES, the register of the European Commission; only the number goes to the Commission, and we keep the result with the date. We do not sell or share data for marketing and we send no newsletters unless you ask for them.
Cookies
Dorelli Cloud uses functional cookies only: one for your language preference, one for your portal login session, and one with your browser's time zone, so we show times in your own time. That last one is kept until you close your browser. If you close the bar that offers the page in another language, your browser remembers that in its local storage, not in a cookie; this only happens when you click it. Forms are protected by Cloudflare Turnstile, which blocks bots without tracking you and without puzzles. No tracking, no ad cookies, no cookie wall needed.
Where your data lives
Websites, databases and backups run in data centers within the European Union (Amsterdam and Dublin regions). There are four exceptions. First: the text of a website is sent to Anthropic for the abuse check, which processes outside the EU, at every publication and daily after that (see “Abuse screening”). It is text you intended to publish on a public website. Second: the content of support tickets, reports and chat conversations, and the details for an email about your domain, go to Anthropic for a draft or an answer (see “Support and email”). Anthropic does not use those texts to train models and deletes them within 30 days, longer only if a text is flagged as abuse. Third: email to and from us, and the submissions of forms on customer sites, travel through Cloudflare; where Cloudflare processes that email, we cannot limit to the EU. Fourth: if we register a domain name for you, the holder's name, address and phone number go to the registrar and the registry of that extension, because the domain name cannot be registered otherwise. For some extensions, such as .com, they are outside the EU. Registrars and registries receive that data as separate controllers, not as our processors. Other than that, customer data (accounts, statistics, invoices) does not leave the EU. A copy of every backup is kept at Cloudflare, stored with the EU as jurisdiction.
Sub-processors
We work with a small number of GDPR-compliant suppliers: Microsoft (EU data centers for hosting and storage), Cloudflare (security, CDN, bot protection and email), Mollie (payments, Netherlands) and Anthropic (the automated abuse check on the text of websites and the start page of apps, drafts of support replies, assessments of reports, emails about your domain, and the chat assistant; United States, under the European Commission’s standard contractual clauses). Data processing agreements are in place with each of them, with one exception: for the drafts for support and reports and the emails about your domain, Anthropic works under the terms of a subscription, without a data processing agreement and without standard contractual clauses (see “Support and email”).
Retention
Requests that do not lead to a customer relationship are deleted within 6 months. A trial site stays online for 14 days; the files are then deleted, and the registration (email address, subdomain name) within 6 months after that. The contact-form spam log is kept for 2 days. Customer data is kept for the duration of the service. After cancellation your site goes offline; 30 days later we delete its files and your company details, and 6 months later the registration too (email address, subdomain name). Invoices are kept for 7 years due to tax law, together with what belongs to them, such as what you ordered and whether you are a private person or a business. Your account stays, so you can still get to your invoices; if you want us to delete it, one email is enough. If you have had no site, subscription or invoice with us for two years and have not signed in, we delete your account ourselves: we email you a month ahead, and signing in before that date stops it. If a payment or a question of yours is still open, we wait. The invoices themselves we keep for the full 7 years. App databases and storage are kept for 30 days after deletion (an own database server 7 days); usage records are kept for 7 years with the invoice they belong to. Backups are kept for 90 days; data you delete is gone from the backups after that as well, and on request we delete the backups of your database sooner. Monitoring data is automatically deleted after 90 days. We keep the assistant's work logs for 30 days. Support tickets are kept for 2 years after closing, so we can look up an earlier problem; after that they are deleted.
Your rights
You have the right to access, correct, delete and transfer your data, and to object to processing. Email support@dorelli.cloud and we will handle your request within 30 days. If you want a trial site removed sooner than after 14 days, one email is enough. You can always lodge a complaint with the Dutch Data Protection Authority.
Security
All connections are encrypted (HTTPS/TLS), passwords and keys are stored hashed, systems are monitored 24/7 and daily backups run of the platform and of every customer database, with a copy outside the data center. A trial site and a Website consist of static files; no code of theirs runs on our servers. An app runs in its own container, separate from the platform. What a page loads in a visitor’s browser, such as a script from another service, is up to the site owner. A trial site made of static files carries noindex, so search engines leave it out. A paid Website may be found, on its trial address too, unless it is blocked or paused. An app sends its own responses; we add no noindex to them. Access to customer data is limited to what is strictly necessary. Signing in, the chat and the check of a domain name or VAT number work the same way as publishing: we keep an encrypted form of your IP address for at most an hour, only to cap the number of attempts per hour, and then we delete it. When you sign in we count per address and email address together; when you publish, also per email address on its own. The second step of signing in also counts per account, and publishing with the deploy token per token or per GitHub repository. All these counters are encrypted and go after at most an hour; only the recovery copy of our database still holds them for up to 35 days. We never store the address itself.