Back to the homepage

Privacy

Privacy statement

This site collects as little as possible. Below is exactly which data we receive from you, why we process it, who we share it with and how long we keep it, in plain language.

Last updated on

The short version

  • No analytics, no tracking cookies and therefore no cookie banner. We do not measure your visit.
  • No embedded buttons, videos or third-party fonts. Everything loads from our own server, so your visit does not pass by anyone else.
  • The contact form processes only what you type yourself, and after a successful send nothing about it stays on our server. Separately, the web server keeps a technical log for 14 days, as every web server does.
  • One processor outside the EU: the email service that delivers our notification message. Point 06 explains what that means.
  • Want to know what we hold about you, or want it gone? One email is enough, and it costs you nothing.

01 Who is responsible for your data

Distility Software Development is the controller: we decide why and how the data on this site is processed. These are our details.

Company
Distility Software Development
Address
Leeuwerikhof 2, 5348 XM Oss
Chamber of Commerce No.
86647199

We have no data protection officer, and a company of this size is not required to appoint one. Your question goes straight to Roy Garrido, the founder. Nobody sits in between.

02 What the contact form collects

If you fill in the form on the homepage, we process the details you enter yourself:

  • Your name, so we can address you.
  • Your email address, so we can reply.
  • The subject, if you fill it in. This field is optional.
  • Your message itself, with whatever you want to tell us.

We use those details solely to read and answer your message. It does not sign you up for a newsletter, we build no profile from it, and we sell or share it with nobody for commercial purposes.

Put only what is needed in your message. We never ask for data about health, beliefs, political views or other sensitive subjects, and we do not need it. The form also has a hidden field that only automated spam scripts fill in: if it is filled in, the message disappears without anything being stored or sent.

To stop a single visitor or bot from flooding the form, a limit of five submissions per hour applies. For that the server keeps no readable IP address but an unreadable hash of it (SHA-256) with the times of your submissions, and those expire by themselves within an hour. That is not fully anonymous, so we say so. Beyond that the form records nothing about your visit: no readable IP address, no user agent and no referer. The web server's general log is a separate matter; see point 04.

03 The legal basis for all this

The GDPR requires a legal basis for every processing activity. These are ours:

Reading and answering your message
Legitimate interest, art. 6(1)(f)

You send us a question of your own accord. Our interest is being able to answer it, and that is exactly what you expect from us. Your privacy does not outweigh it here, because we process nothing beyond what you wrote yourself and do nothing else with it.

Preparing a quote or a collaboration
Pre-contractual, art. 6(1)(b)

If your message is about a possible assignment, we also process it to take steps at your request before there is a contract. Think of a price indication or a first conversation.

Keeping the site safe and working
Legitimate interest, art. 6(1)(f)

This covers two things. The spam limit: five submissions per hour, tracked with a hashed IP address. And the web server's log, which includes IP addresses and which we use only for security and troubleshooting. Our interest is a site and a form that do not get buried by bots or abuse.

So we do not rely on consent, and we do not ask for it. That does mean you can object to the processing based on legitimate interest. Point 09 explains how.

04 How long we keep your data

No longer than necessary. This is what that means, place by place:

On our server
Only if a send fails

If the message goes out, nothing stays behind on our server. If it fails, we keep a copy outside the public website so your question does not disappear silently. We keep that copy no longer than we need it to still get your message answered.

The notification email in our mailbox
As long as we need it

This email is the only lasting trace of your message, and it is ordinary business correspondence. We keep it no longer than we need it for your question and whatever comes of it.

If you become a client
For the assignment, then 7 years

Your details then move to our client administration. Invoices and the related bookkeeping fall under the statutory Dutch tax retention period of seven years. Anything outside that we keep no longer than the assignment and the follow-up require.

At our email service
30 days

The sent message and the matching log entries are deleted there after 30 days. Backups disappear within a week after that.

The web server's log
14 days

For every request the web server writes a line with, among other things, the IP address, the time, the page requested and the type of browser. Those lines are deleted automatically after 14 days.

05 Who else processes your data

We bring in as few other parties as possible. For the site there are three, and we name them here by their role. If you want to know which companies they are, ask us: we will simply tell you.

A hosting provider, for the server

The website and the contact form run on a dedicated server that we rent from a hosting provider within the EU and manage ourselves: they supply the hardware and the network connection, the data on it is ours to manage. Only a failed send puts a copy of your message on this server. The web server also keeps a standard log, which includes IP addresses; it is deleted automatically after 14 days.

An email service, for delivering the notification email

The moment you press send, your name, email address, subject and message go to the service that delivers the notification email to us. That is an American company; point 06 explains what that means.

Nothing else travels with it: we pass on no technical details about your visit. The service deletes the content of the message and the matching log entries after 30 days.

An email provider, for our business mailbox

The notification email arrives in our business mailbox, and that is where we send you our reply from. The mailbox is with an email provider that stores the data within the EU.

WhatsApp, if you choose it yourself

The site has a link that lets you send us a WhatsApp message. It is an ordinary link and not a built-in chat: the site loads nothing from WhatsApp, and as long as you do not click, nothing happens. If you do click, the conversation runs through WhatsApp, a Meta service offered in Europe by WhatsApp Ireland Limited.

We then see your phone number, your profile name and whatever you send us. As with the form, we use that only to answer your question. What WhatsApp itself does with your data and where it ends up is decided by WhatsApp and set out in its own privacy policy. If you would rather not, the form, email and phone work just as well.

Nothing else. No analytics or advertising party, no CRM, no chat widget, no A/B testing service and no payment provider on this site.

06 Transfers outside the EU

There is one transfer outside the European Economic Area, and we want to name it explicitly.

The service that delivers our notification email is an American company. We send through its European region (Ireland), so your message does not leave Europe to be delivered. That narrows the transfer without removing it: the content of sent emails, the metadata and the log entries are kept in the United States for 30 days.

The transfer rests on two things. First, the European Commission's standard contractual clauses (decision 2021/914, module two), which form part of the processing agreement with this service. Second, its certification under the EU-US Data Privacy Framework, the European Commission's adequacy decision for transfers to the United States. If you want to know which service it is, or to see a copy of those arrangements, ask us.

What that means in practice: under US law, American government agencies can in theory request access to data held there. If you would rather avoid that, email or call us directly instead of using the form.

07 Cookies and browser storage

This site places no cookies. Not ours, not anyone else's. That is why you see no cookie banner: there is nothing to refuse.

We do keep one thing on your own device: your choice of the light or dark theme, under the name distility-theme in your browser's local storage. That value stays in your browser, is never sent to us or to anyone else, and contains nothing that identifies you. It is a functional preference, which needs no consent. You can wipe it by clearing this site's data in your browser.

The fonts on this site come from our own server. Loading this page therefore sends no request at all to Google Fonts or any other external domain. There are no embedded videos, maps, social media buttons or chat widgets either.

What we do have are ordinary outbound links: to LinkedIn, to X, to WhatsApp and to the websites of the projects we show. Click one and you leave our site, where that party's rules apply. As long as you do not click, nothing happens.

08 How we protect your data

Security is technical work, not a promise. This is what is actually in place:

  • All traffic runs over HTTPS. A request without encryption is redirected to the secure variant.
  • A successful send stores nothing. A failed one leaves a copy outside the public web folder, with restricted permissions, so it cannot be requested through a web address.
  • The request to the email service runs over a verified TLS connection, with certificate checking.
  • The key for that service lives outside the website and outside our source code.
  • Everything you enter is checked for length and validity and neutralised before it reaches the notification email. On top of that, the limit of five submissions per hour applies.
  • The browser receives security headers, including X-Content-Type-Options, Referrer-Policy, X-Frame-Options and Permissions-Policy.

One hundred percent secure does not exist, and we would rather say so. If you think something is wrong with the security of this site, let us know at info@distility.dev.

09 Your rights

The GDPR gives you rights over your own data. You can exercise these with us:

Access

You may ask which data we hold about you and receive a copy of it.

Rectification

If something is wrong or incomplete, we correct or complete it.

Erasure

You can ask us to delete your data. If no assignment is running and no statutory retention applies, we simply do it.

Restriction

You can ask us to pause the processing, for example while a correction or an objection is being handled.

Objection

You can object to the processing based on legitimate interest. We then stop, unless there are compelling grounds to continue. If so, we explain them.

Data portability

You can receive the data you supplied yourself in a common file format. Formally this right does not apply to every legal basis, but in practice we simply send you what you want from us.

We take no decisions about you based on automated processing alone, and we build no profiles.

How it works: send an email with your request to info@distility.dev. We respond within a month, usually within a few days, and it costs you nothing. If we doubt that it is really you, we ask a check question about the contact you had with us. We never ask for a copy of your ID.

10 Questions, complaints and changes

Questions about this statement or about what we do with your data? Email info@distility.dev or call +31 6 1331 1661.

If you feel we are not handling your data carefully, tell us first. We would rather solve it together. On top of that you always have the right to lodge a complaint with the Autoriteit Persoonsgegevens, the Dutch supervisory authority, at autoriteitpersoonsgegevens.nl.

If anything changes about this site or about the parties we work with, we update this statement and put a new date at the top. We keep no archive of earlier versions. If you want to know what changed, just ask.

Last updated on . Back to the homepage

Start a conversation