The small print, set large.
Because it's written for you too.

Four documents. What's in them, why it matters to you, and where to go if you disagree with us.

I'm not going to pretend anyone reads this for fun. But if a system answers your phone and handles your customers' data, then it should be in writing what happens to that data and who carries what. Here it is.

Last updated: 11 September 2026 · Questions? Email iliacevermeulen@digiduckai.com and you get a person.

Privacy statement.
What we keep about you, and why.

This document is about your data - the visitor, the prospect, the client. What we keep when you email me or book a call, why we keep it, how long, and who else sees it. One distinction matters: this is not about your customers' data flowing through a system we built - that's the DPA. So read this if you want to know what happens to your name and number after you type them in here. Short version: your details are used to get back to you and to raise an invoice, and you can ask for them or have them deleted at any point.

Terms and conditions.
What you buy, what you get, when you stop.

This is the agreement itself: what the build covers, what it costs, when you pay, what happens if either of us doesn't hold up their end, and how you get out. That last part is the one to check. With us you can stop after any phase and everything built stays yours - that isn't a slogan, it belongs in the terms, or it's worth nothing. Read the sections on ownership and on what gets delivered in particular. If anything there doesn't match what I told you, call me. Then something's wrong on my side.

Cookie policy.
What this site puts on your device.

Short version: this site sets no cookies of its own and stores nothing in your browser. No analytics, no ad pixels, no tracking - which is why there is no cookie banner. The fonts come from our own server, not from Google. Two places involve a third party: the booking calendar on Book a Call is Google's, and it only loads when you click to show the available times; and the globe on the Contact page loads a drawing library and map outlines from two code hosts. The full policy lists exactly that - which is why it is short.

Data processing agreement (DPA).
The document about your customers' data.

This is the most important of the four, and the only one we both sign. The moment I build something that handles calls or books appointments, your customers' data runs through a system I made. At that point the law says: you decide why that data is processed, I do what you instruct and nothing more. This agreement pins that down - what data, for what, for how long, who else can reach it, what happens when something goes wrong, and what happens to everything if we stop. It gets signed before a single connection goes live. Not after, and not "we'll sort that out later".

This isn't legal advice.
And it doesn't pretend to be.

What you read above are summaries and structures. The privacy statement and the cookie policy are published in full; the terms and the DPA get reviewed by a lawyer before anyone signs them. If you spot something here that doesn't match a full document, the document wins - and I'd want to know, because then my summary is wrong.

Questions about your data? Email iliacevermeulen@digiduckai.com.

Not happy with our answer? You can complain to the Belgian Data Protection Authority, Drukpersstraat 35, 1000 Brussels.

Digi Duck AI · Iliace Vermeulen · BE 1023.452.443 · Lindestraat 93, 2880 Bornem · VAT: exempt under art. 56bis of the Belgian VAT Code