Privacy

What I collect

Today I receive personal data through one channel: email you send me. When you email me you share your email address and whatever else you choose to put in the message, typically your name and a description of the work you have in mind. I do not collect more than you send.

The contact page shows a project-intake form, but it is a preview: the fields are disabled, there is no submission endpoint, and it captures nothing. Use the email address on that page to reach me. When that form goes live (planned for a later build stage), it will collect your name, email, project brief, and an optional budget for the same purpose as email, and this notice will be updated to say so at that point. Until then it collects nothing.

Beyond email, the site handles a few technical items. The theme system stores a functional value in your own browser (a first-party local-storage item): whether you prefer the light or dark appearance, a live choice you control today. A site-language choice and a text-size (UI-scale) preference are planned and will be stored the same first-party way once built; today neither exists.

The hosting provider processes standard request data, such as your IP address, to serve the site, keep it available, and protect it against abuse. My host also produces aggregate, cookieless traffic statistics from its own server logs: this sets nothing on your device and does not track you across sites.

I set no tracking cookies, run no client-side analytics scripts, load no ad or social pixels, and keep no account or database. There is nothing to log in to.

Why I collect it

Email you send me: to read and answer your enquiry, and to scope and deliver the work you ask about.

Your theme preference (and, once built, the language and text-size preferences): to remember how you like the site shown between visits. These are functional settings, not identifiers.

Request data and aggregate traffic statistics at the host: to serve the site, keep it available, understand overall usage in aggregate, and protect it against abuse.

When live, the intake form: the same purpose as email, to receive and respond to a project brief.

Lawful basis (GDPR Article 6): for answering an enquiry and scoping work, and, when it goes live, for the intake form, I rely on taking steps at your request before entering a contract (Article 6(1)(b)) and, where broader, my legitimate interest in responding to business enquiries (Article 6(1)(f)). For serving and securing the site and reading aggregate traffic statistics I rely on legitimate interest (Article 6(1)(f)). Where a business relationship follows, I keep the financial and administrative records the law requires me to keep, on the basis of my legal obligations (Article 6(1)(c)).

How long I keep it

Email you send me stays in my Proton mailbox for as long as it takes to deal with your enquiry and any relationship that follows, and is deleted when it is no longer needed for that purpose. Where a paid engagement follows, the financial and administrative records tied to it are kept for the statutory Dutch tax-retention period, currently seven years.

Your theme preference (and, once built, the language and text-size preferences) is held in your own browser's local storage, not by me, and remains until you clear your browser data. I cannot see or delete it for you.

Host request data and aggregate statistics are retained per the hosting provider's own logging policy.

There is no server-side store on my side to retain anything else.

Who it is shared with

I do not sell personal data, and no advertising or client-side analytics network receives anything from this site. The web fonts are served from this site's own origin, so loading a page makes no request to Google or any other font host at runtime.

To run the site and its email I rely on a small number of service providers who process data on my behalf, under their data-processing terms: Proton AG (Switzerland), my email provider, processes the content and metadata of email you send me (Switzerland is covered by an EU adequacy decision, so no additional transfer safeguard is required); Cloudflare provides hosting and CDN for the static site and produces the aggregate, cookieless traffic statistics, processing request data such as IP addresses in its edge logs (any transfer outside the EEA is covered by Cloudflare's data-processing agreement and standard contractual clauses).

If and when the project-intake form and any associated storage go live, the provider handling them will be added here, with its data-processing agreement, before the form starts collecting. I may also disclose data where the law requires it.

Your rights

Under the GDPR you have the right to access the personal data I hold about you, to have it corrected or erased, to restrict or object to its processing, and to receive it in a portable form. Where processing rests on consent, you can withdraw that consent at any time.

You also have the right to lodge a complaint with the Dutch supervisory authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl).

To exercise any of these rights, email me at fullstagdigital@proton.me and I will respond.

Contact

For any question about this notice or your personal data, or to exercise your rights, email fullstagdigital@proton.me.

Controller: Full-Stag Digital, Wattstraat 17, 5621 AG Eindhoven, Netherlands. Chamber of Commerce (KvK): 42076725.