Privacy statement

I, Jorijn Schrijvershof, based at Postbus 465 4900 AL Oosterhout, am responsible for the processing of personal data as described in this privacy statement.

On this page (12)

Contact details

Website
jorijn.com
Address
Postbus 465, 4900 AL Oosterhout
Phone
+31 6 16 66 64 81
Email
jorijn@jorijn.com

I am the Data Protection Officer of my business and can be reached at jorijn@jorijn.com.

Personal data I process

I process your personal data because you use my services and/or because you provide this data to me.

Below is an overview of the personal data I process:

  • First and last name
  • Bank account number
  • Address details
  • Phone number
  • Email address
  • If you are a client, also data about your website: the domain name, which plugins and themes are installed and in which version, error messages, and the results of my checks. If you are a sole trader, that counts as personal data too.

Special and/or sensitive personal data I process

My website and/or service does not intend to collect data about visitors who are under 16 years of age, unless they have permission from a parent or guardian. I cannot verify whether a visitor is over 16. I therefore advise parents to be involved in their children’s online activities to prevent personal data being collected without parental consent. If you believe I have collected personal data about a minor without consent, please contact me at jorijn@jorijn.com and I will delete it.

Purposes and legal bases for processing

I process your personal data for the following purposes:

  • Handling your payment
  • Calling, emailing, or messaging you if this is necessary to carry out my services
  • Hosting, updating, and monitoring your WordPress site, if you are a client
  • Informing you about changes to my services and products
  • I also process personal data if I am legally required to do so, such as data needed for my tax filings.

What my management system processes about your site

If you are a client, your site runs on my own server in the Netherlands. That is where your site and its database live, along with the copy I make before every update (kept for seven days) and the daily backups (every day for the last two weeks, then a weekly version going back a month and a monthly one going back six months). For the data of your visitors and customers inside that site, you are the controller; I only process it on your instructions. You can request a data processing agreement from me.

My management system reads your site through a small connector of mine on the site and through the hosting server. It runs on a Hetzner server in Falkenstein (Germany). For each site it holds: which plugins, themes, and versions are installed, the results of the health checks, a log of what the system did, and for every error in the error log at most three sample lines, with email addresses, IP addresses, and URL query parameters masked. It also keeps screenshots of public pages of your site before and after an update, for 30 days. What is not there: no copy of your database, no orders, and no names, email addresses, or usernames from your site. Of the access credentials the system needs, it keeps an encrypted version only. Every night an encrypted backup of the system's database goes to Hetzner Object Storage in Nuremberg (Germany); it stays there for 13 months and cannot be deleted earlier, not even by me.

An AI reads along, but does not decide. For an opinion, the system sends text to the API of Anthropic (United States): the code changes between the old and new version of a plugin, your site's configuration without passwords or keys, the masked sample lines from the error log, and the screenshots of public pages. Before sending, the system masks every word containing an @ and every long key or token. So whatever is public on your page can be in a screenshot. What comes back is advice: how risky an update is, what probably caused an error, whether a page looks different. Whether an update goes ahead is decided by a fixed rule, and the only action that can follow from an AI opinion is rolling an update back. Of every opinion the system keeps the model, a fingerprint of the input (not the input itself), and the opinion. When I operate the system from Claude Code, what I look up there, for instance the last lines of your site's error log, also goes to Anthropic. That transfer to the United States rests on the standard contractual clauses in Anthropic's data processing agreement. Anthropic does not train its models on what comes in through the API and deletes inputs and outputs within 30 days by default, unless it flags a use as possible abuse.

Twice a day (at 6:30 am and 6:30 pm), your site sends a test email to a test address of mine, to check that email from your site arrives. That email contains only a fixed sentence with an identifier of your site and a random token. It arrives at Amazon Web Services (Amazon SES, Ireland region), which tells my system that it arrived: the time, the server it came from, and the outcome of the authenticity checks (SPF, DKIM, DMARC). My system does not keep the content of the email. Through the same service, the system sends me its morning overview of all sites every day; that overview is for me, not for you.

When a finding turns red (your site is unreachable, the test email does not arrive, a serious vulnerability), an alarm goes to my phone through All Quiet. That alarm contains the name of your site, the title of the finding, and the next step, no content from your site. All Quiet also checks from the outside whether your site is reachable. All Quiet is based in Germany; the alarms are stored in the EU.

Automated decision-making

I do not make decisions based on automated processing that could have significant consequences for individuals. There is no automated decision-making without human involvement. The AI advice in my management system is about updates and errors on your site, never about you or other people; the only action that can follow from it without me is rolling an update back.

How long I keep personal data

I keep your personal data no longer than strictly necessary to achieve the purposes for which it is collected. I apply the following retention periods for the following categories of personal data:

  • Invoice and payment data: statutory fiscal retention period.
  • Contact data: as long as needed to handle your request.
  • Your IP address when you send the contact form: one minute, only to stop repeated sending.
  • The copy of your site made before an update: seven days. The daily backups of your site: every day for the last two weeks, then a weekly version going back a month and a monthly version going back six months.
  • Screenshots and test reports of your site in my management system: 30 days.
  • The data about your site in my management system (inventory, checks, log): as long as you are a client. When the contract ends, I delete your site after handing it over to you or your new provider. The backups disappear following the schedule above; after six months, the last one is gone. After that, the data about your site in my management system remains only in that system's encrypted backup, until 13 months after the end; nobody can delete it earlier, not even me.
  • The encrypted backups of my management system's database: 13 months.

Sharing personal data with third parties

I share your personal data with third parties when this is necessary to perform the agreement and to comply with any legal obligation. With companies that process your data on my behalf, I sign a data processing agreement to ensure the same level of security and confidentiality. I remain responsible for these processing activities. For the data inside your site, you are the controller; Hetzner, Anthropic, Amazon Web Services, and All Quiet are my sub-processors for it. I only share your personal data with other third parties with your explicit consent.

With Hetzner, Amazon Web Services, Anthropic, and All Quiet, their standard data processing agreements apply.

Scroll the table sideways to see all columns.

Third-party category Name + jurisdiction Purpose Data Basis
Accounting Moneybird (Netherlands) Invoicing and administration Name, address details, email address, invoice and payment data Performance of the agreement, legal obligation
Email Google Workspace (United States) Sending and receiving email Name, email address, email content, and contact details Performance of the agreement
Server of my management system Hetzner (Germany: Falkenstein, backups in Nuremberg) Running and backing up my management system Domain name, plugins and versions, check results, log, masked error lines, screenshots of public pages, encrypted access credentials Performance of the agreement
AI advice Anthropic (United States) Advice on the risk of an update, the cause of an error, and differences between screenshots Plugin code changes, site configuration without keys, masked error lines, screenshots of public pages Performance of the agreement; transfer: standard contractual clauses in Anthropic's data processing agreement
Transactional email Amazon Web Services, Amazon Simple Email Service (SES), Ireland region The test email from your site (twice a day) and the morning overview of my management system Identifier of your site, sending server, and delivery metadata of the test email; in the overview, the findings per site Performance of the agreement
Alarms All Quiet (Germany) Alarm to my phone on a red finding; reachability check from the outside Name of your site, title of the finding, next step Performance of the agreement
Messaging WhatsApp (Meta), Ireland, with transfers to the United States Messaging me, if you choose that channel Your phone number, name, and profile as you have them on WhatsApp, timestamps and other metadata of our messages; the messages themselves are subject to WhatsApp's terms Your choice: you start the conversation. Prefer email or a call? Always possible.

Website measurement

I use my own Plausible installation for basic, aggregated website statistics. Plausible does not use cookies and I do not use Google Analytics, Google Ads, or remarketing on this website. Besides page views, I count a few clicks: on the button to the contact page, on email, phone, and WhatsApp links, on the play and pause button of the update strip, whether the contact form was actually sent, and whether one of the hidden extras was found. What you type or copy never goes along. Plausible runs on a server of my own in the Netherlands.

You can disable Plausible in this browser on the analytics opt-out page.

Storage in your browser

If you type a message in the contact form, your browser keeps a copy of that text in this tab, so it isn't lost if you reload the page or step away for a moment. That copy never leaves your browser and I don't see it. It disappears as soon as your message is sent or you close the tab. Beyond that, your browser only remembers in this tab whether the update strip's animation has already played and whether the compass at the top left has already turned back once, and whether you've already seen the note after copying or after the Konami code. What you copy never leaves your browser and isn't stored anywhere. If you disable Plausible on the analytics opt-out page, your browser remembers that too, in every tab, until you turn it back on there.

Accessing, correcting, or deleting data

You have the right to access, correct, or delete your personal data. You also have the right to withdraw your consent for data processing or object to the processing of your personal data by me. You also have the right to data portability. This means you can submit a request to have the personal data I hold about you sent to you or another organization you specify in a computer file.

You can send a request for access, correction, deletion, data transfer, withdrawal of consent, or objection to processing to jorijn@jorijn.com.

To verify that the request for access was made by you, I ask you to include a copy of your ID. In this copy, please black out your photo, MRZ (machine readable zone, the strip with numbers at the bottom of the passport), passport number, and citizen service number (BSN). This is to protect your privacy. I will respond as soon as possible, but within four weeks.

You can file a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) via this link: autoriteitpersoonsgegevens.nl.

How I secure personal data

I take the protection of your data seriously and take appropriate measures to prevent misuse, loss, unauthorized access, unwanted disclosure, and unauthorized modification. If you believe your data is not properly secured or there are indications of misuse, please contact me at jorijn@jorijn.com.

Wondering if this is a good fit for your site?

Book an intro call, and I'll look at your site with you.