Skip to content

Privacy

What we keep about you

This statement covers ploink.io and the client portal at portal.ploink.io. It sets out which data exists, where it goes and how long it stays.

Last updated 21 August 2026

Who we are

The data controller is Ploink, Laakweg 62a, 3864 LD Nijkerkerveen, KvK 96547821, btw NL004512389B47. You can reach us at info@ploink.io or +31 6 37 08 30 36.

There is no data protection officer, and none is required: this is a one person company that processes no special categories of data and does not monitor people at scale.

In short

  • ploink.io carries no analytics, no tracking pixel and not a single cookie.
  • The portal sets one cookie, and that is your login. There is no second one.
  • The home scan does not keep your address. That is not a promise after the fact; it is why it uses a POST and caches nothing.
  • We sell nothing on and use nothing for advertising.

The site: ploink.io

The contact form

You fill in your name, email address, company name and message. That is sent to us as an email and goes nowhere else. It is not stored in a database and there is no second copy: only the message in the Ploink mailbox, kept for as long as the conversation runs and then two years for our records.

Basis: you send it yourself and we need it to reply. Delivery runs through Resend, see below.

The home scan

The demo on this site asks for a postcode and house number. We use those to look up the build year and floor area at PDOK, the Dutch government open map service. We do not keep the address, and we do not keep the result either.

That is built in rather than merely stated: the address travels as a POST and not in the URL, because URLs end up in logs, and the response carries no-store so nothing lingers along the way.

What the server sees

The site runs on Cloudflare. Like any web server it sees your IP address and browser type, and keeps that briefly for security and to block attacks. We do not store it ourselves and cannot follow a visitor with it.

The client portal: portal.ploink.io

The portal exists for clients only. Below is what each part holds.

Your account

Your name, email address, role and language. Your password is not in there: we keep only a cryptographic hash from which the password cannot be recovered. We cannot see your password, and there is no screen where we type one for you.

We also record when you last signed in, so it is visible whether an account is still in use.

Signing in and the cookie

When you sign in we set one cookie containing a random key and nothing else. Who you are lives in our database, not in that cookie, so a session can genuinely be revoked. The cookie is httpOnly and secure, never travels to ploink.io, and expires after fourteen days, or one day if you leave "stay signed in" unchecked.

With each session we also keep the device and browser type you signed in with, truncated. That is there so you can recognise which session belongs to which device.

An invitation or reset email contains a link that works once. We keep only a hash of that link, and it expires after seven days for an invitation and one hour for a reset.

What you upload yourself

Your sources, your documents and the articles we write for you. That is business information and usually not personal data, but names can appear in it, in a company profile for instance. Only you, your colleagues at the same company and we can see it. Other clients of ours cannot, and that is enforced on every query rather than merely hidden on screen.

Notifications

If you turn on notifications we keep the address your browser gives us at its own push service, two keys to encrypt the content, and the device type. There is no phone number in it and nothing that identifies you outside this portal. The content of a notification is encrypted: Google, Apple or Mozilla sees only bytes and cannot tell what it says. Turn them off and the address is deleted straight away.

The figures from your tools

If a tool of ours runs on your site, the portal counts how often it is opened, started and completed. By design it holds no address, no name and no IP, and that is enforced in the database rather than merely agreed. What it can hold is something coarse and non identifying, such as "heat pump" or "terraced house".

Your IP address

When signing in we use your IP address to count attempts per minute, so a password cannot be guessed. That counting happens at Cloudflare and we do not store the address.

Other parties

These are all the parties that get to see data about you. There are no others.

Cloudflare
Hosting, database and file storage for the site and the portal. Everything described above lives with them.
Resend
Delivers our email: a contact request, a portal invitation and a note that an article is waiting for your approval.
Anthropic
Writes the articles for the article engine. To do that, the sources you supply and your brief are sent to the model. We do not use that data to train a model, and Anthropic does not do so for business use either. If you do not use the article engine, nothing is sent.
Google, Apple and Mozilla
The browsers’ push services, only if you turn on notifications. They deliver an encrypted message and cannot read the content.
PDOK
The Dutch government open map service, only for the home scan. A postcode and house number go there, and nothing else.

The usual processor terms apply with these parties. Some of them process data outside the European Union, under the standard contractual clauses the European Commission has adopted for that purpose.

How long it stays

Sessions and one time links expire by themselves, within fourteen and seven days respectively. The rest stays for as long as you are a client, because it is your own work: your sources, your articles and your documents. If you stop, we remove your data within thirty days, except what we must keep for our accounts; that is the invoice, which is kept for seven years.

Anything already published on your own site simply stays there. That is yours.

How it is secured

  • Everything runs over https, and the portal sits on its own domain so the login cookie never reaches the site.
  • Passwords are hashed with a hundred thousand rounds and a unique salt per password.
  • The password we use to publish on your site is stored encrypted and cannot be read back anywhere, not even by us.
  • Every data query is scoped to the organisation, so one client can never reach another client’s work.
  • Screens behind the login may not be cached anywhere, including by your browser after you sign out.

What you can ask for

You may ask what data we hold about you, have it corrected or deleted, receive it in a usable file, and object to its use. Send an email and you will hear from us within a week, and in any case within a month.

If you disagree with how we handle it, you can complain to the Dutch Data Protection Authority.

If this changes

If what we keep or who receives it changes, this text changes with it and the date at the top is updated. For a change that means something for you, you will be told in the portal.