NLEN

Privacy policyLast updated on 26 October 2026

How SharpClicks handles personal data. Which data we collect, for which purposes, how long we keep it and which rights you have under the GDPR. This is version 2026-10-26.

Don't want to be recognized as a business?Opt out your organization with just your domain name. You don't have to give a reason.Go to opt-out

01Who we are and what this covers

1.1Who is responsible. SharpClicks is the controller for the processing in this privacy policy. SharpClicks is the sole proprietorship (eenmanszaak) of Jesse Scherpen, Krimweg 34A, 7741 NB Coevorden, the Netherlands. Chamber of Commerce (KvK) number 84939842. VAT number NL004034939B94. Questions about your data: jesse@sharpclicks.nl or +31 6 117 227 50.

1.2Who this applies to. Everyone whose data we receive: people who visit sharpclicks.nl, fill in a form or schedule a call, people who email us, and clients with their contact persons and signatories in the client workspace.

1.3What this does not cover. When we build a system for a client that processes other people's data, we do so on behalf of that client. The client is then the controller. We make separate arrangements for that in a data processing agreement. This also applies to cold outreach: we only find and enrich data on behalf of the client, and do not use it for ourselves.

1.4Definitions.

Personal data: any information about a person, or that can be traced to a person. For example your name, email address, phone number, IP address and what you write to us.
Processing: anything we do with data, such as collecting, storing, viewing, using, passing on and deleting.
Data subject: the person the data is about. Often that is you.
GDPR: the General Data Protection Regulation (Regulation (EU) 2016/679). SharpClicks complies with it and with the Dutch GDPR Implementation Act (Uitvoeringswet AVG).
Processor: a party that processes data on our behalf, such as our hosting provider.
Client workspace: the closed part of the site at sharpclicks.nl/onboarding. There, a client sees the quote, accepts the terms and signs. If we agree on it, the client also provides what we need there (article 3).
Onboarding: the client workspace of one client, for one assignment.
Signatory: the person who signs on behalf of the client in the client workspace.
Fingerprint (hash): a short code calculated from a file or text. If one character changes, the code changes. The content cannot be recovered from the code.

02What data we process on the website

2.1Forms. The site has these forms:

Form	What you fill in
Contact	name, email address, your company (optional) and where most of your time goes (optional)
The check (calculate your time savings), the message after the result	name, email address, and the result and your answers from the check
Free design (landing page)	for which company or which site, name and email address
Call about video (short-form content and company videos)	name, email address and what you want the video for
Free blog	topic, your website address and email address
AI findability: sample article	topic, your website address and email address
LinkedIn giveaway	name, company and email address. Which giveaway it is comes from the link
Opt out of business recognition	a domain name only

With each request we also store the page you sent it from and the time. Each request is stored in WordPress, under Aanvragen (Requests). This way nothing gets lost, even if an email fails.

For every form, Jesse gets an email with what you filled in. For Contact, the check, Free design and video, you get a confirmation by email yourself.
Free blog, the sample article, the giveaway and opting out also go to our own workflows in n8n. They have the article written, send the download or put your domain on the exclusion list (article 7.3).
A request about video goes to our video partner Fishuals. They contact you and schedule a call (article 7.6).

2.2Scheduling a call. On Contact, after the check and after a request for a free design, you schedule a 30-minute call yourself.

The planner shows the free times from Jesse's Google Calendar. The site only asks Google when Jesse is busy. The site does not see titles or names of other appointments, and neither do you.
When you pick a time, the planner asks for your name, your email address and, if you like, a message.
The site puts the appointment in Jesse's calendar, with you as a guest and a Google Meet link. Google sends you the invitation.
You also get a confirmation from SharpClicks by email.
The appointment is also stored under Aanvragen in WordPress: your name, your email address, the day and time, your message, the call link and the page.

2.3Email. If you email us, we keep your email and our reply in our mailbox at Hostinger. This lets us handle your question properly.

2.4Technical data. With every visit, the server receives your IP address, the type of browser, the page, the time and the result of the request. This is needed to send you the page. The server at Hostinger keeps logs of this, for security and to find errors.

For the forms, the planner and the cookie choice, we do not store your IP address. To prevent abuse, we do count how often something is sent from one address. For that we use a fingerprint of the address, which expires after ten minutes (one hour for the planner). The IP address itself does not go into the database.

2.5Your cookie choice. When you choose in the cookie notice, we record that choice, without your IP address (article 8.6).

2.6Storage in your browser. When you change page, the site stores a piece of the previous page in your browser (sessionStorage). This makes the transition smooth. It is deleted straight away on the next page and does not leave your browser.

2.7Reviews. On the homepage and the landing page we show a few reviews that clients wrote about us on Google. The name is shown as it appears on Google. We copy them by hand. If your review is among them and you do not want that, email us. We will then remove it.

2.8Instagram videos. A few pages show Instagram videos. They only load when you click on them. A request then goes to Instagram (Meta) and Meta's privacy policy applies.

03The client workspace

3.1What it is. If your company becomes a client, or a quote is ready for you, you get a personal link to the client workspace at sharpclicks.nl/onboarding. There you:

view and download the quote;
accept the terms, document by document;
sign;
see your invoice, if there is one;
answer questions about the service and upload files, if we agree on that with you;
see what happens next.

If you already accepted the quote by email, you give your acceptance of the terms in the client workspace.

3.2What we put in. Before you get the link, we put the following in the client workspace:

your company name, your registration number (KvK, a foreign number or your VAT number) and your address;
the contact person: name and email address, and for a shoot by our photography partner also a phone number if you give one;
the signatory: name, job title and email address;
the language (Dutch or English) and the services;
the quote: the PDF, the number, until when it is valid, the price lines and any options;
if you already accepted by email: that email as a PDF, and the date;
if there is an invoice: the invoice as a PDF, and possibly a payment link.

This data comes from our conversations, the quote and your emails. We check in the Dutch Business Register (KvK) whether the signatory is authorised to sign.

3.3The link and your session.

The link contains a long, random code. It sits after a # and therefore does not go to the server until you click "Open your workspace" yourself.
We do not store the code in readable form: only a fingerprint to recognise it, and an encrypted copy so we can send the same link again. We delete that copy when the onboarding is complete, or when we revoke the link.
The link stays usable for 30 days, also on a second device.
After the click, your device gets a session with one cookie: __Secure-sck. It only applies to /onboarding and cannot be read by scripts.
For each session we store a fingerprint, when it started, when you last did something and whether it has stopped.
After 30 minutes without activity, the session stops. "Log out" is on every page.

3.4The code by email. Before you sign, we send a 6-digit code to the signatory's email address. The email says what is being signed. The code is valid for 10 minutes and works once. Each code allows at most 5 attempts. After 15 wrong attempts, signing is closed until Jesse opens it again.

3.5Signing. You first see what you are signing: the quote number and, for each document, the version. Name, job title, company and registration number are fixed. You tick a box to confirm you are authorised. Then you sign with a mouse or finger, or type your name.

For a drawn signature, we only store the image: the points of the line, rounded. No pressure, no speed and no time per point. The server makes the image from those points itself. We do not use the signature to recognise you.

3.6The evidence. At each step we record what happens. This makes it possible to show later who agreed to what, and when.

For each step: a sequence number, the time (UTC), the type of step and what was shown, with a fingerprint of each document.
Each step builds on the fingerprint of the previous one. A later change therefore stands out.
At five steps we also store your IP address and your browser: the session starts, you request a code, you confirm the code, you tick a box and you sign.
IP address and browser are stored separately. This lets us delete them later while the evidence stays valid.

3.7The evidence sheet and the timestamp. After signing, we create a PDF once: the evidence sheet. It shows the fingerprints of the quote and of each document, the steps and the signature.

We add a timestamp from DigiCert to the fingerprint of the evidence sheet. If DigiCert does not respond, the timestamp comes from Sectigo or FreeTSA. That service only receives the fingerprint. No content and no names.
You and Jesse receive by email the quote, the documents in the version that was signed, and the evidence sheet. The email itself contains the fingerprint of the evidence sheet and the last fingerprint of the steps. This way you have your own copy.

3.8Questions and files.

If we agree on that with you, you answer questions about the service after signing. Each answer is saved straight away, with the question and the version of the questionnaire.
You upload files as pdf, jpg, png, webp, docx, xlsx, csv or txt. Up to about 25 MB per file and 250 MB per onboarding. For each file we store the original name, the type, the size and a fingerprint.
We recreate photos, without hidden data such as the place where they were taken.
You send large files, such as videos, as a link. The file then stays with the service you choose, and that service's rules apply.
Questions and files containing personal data only open once you have accepted the data processing agreement that goes with the service.
You keep your passwords. We never ask for them.

3.9Where it is stored. Everything from the client workspace is on our server at Hostinger. Files are outside the public folder of the site and cannot be opened with a normal web address. You only download your own documents with a valid session.

3.10Who sees it. In the site's admin area, only Jesse sees the client workspace. Other administrators of the site have no access to it. We create an onboarding ourselves, sometimes with help from an AI assistant (Claude, by Anthropic). It then receives what is needed to create the onboarding, such as the company name and the name, job title and email address of the signatory. What you fill in, upload or sign afterwards is not read by that assistant. It never sees the link. Anthropic is our processor for this.

3.11The emails. The client workspace emails go through FluentSMTP and Hostinger's mail server. Emails with a link or a code (the invitation, a reminder, a new link and the code) do not go into the FluentSMTP log. If such an email fails, it may still end up in the log. That is why we immediately invalidate the link or code from a failed email. The email to our photography partner (article 3.15) and the copy of it to Jesse do not go into the log either. If such an email fails, we empty that line in the log: only to whom, when and the error remain.

3.12No tracking code. The pages under /onboarding have no Google Analytics, no Clarity and no cookie notice. The only cookie the client workspace sets is your session cookie (article 3.3).

3.13The nightly copy. The client workspace can make a copy of its files and data every night, so that nothing is lost. This copy is not switched on yet. Once it is switched on, it works like this:

The copy is encrypted, with a new key every night. That key is in turn encrypted with a key that only Jesse holds, outside the server. So the copy cannot be opened on the server.
Our own n8n collects the copy and stores it in a fixed location, which we will name here before the copy is switched on. The site then deletes the copy.
A copy is kept for 35 days.

3.14Retention. How long we keep what is set out in articles 6.6 to 6.16. The site cleans up by itself every day, including in the folder with files.

3.15The photography partner. If you book a shoot by StudioMieke through us (article 7.13), StudioMieke receives one email from the client workspace after signing. It contains:

your company name and your registration number;
the name, email address and phone number of the contact person;
who signed: name, job title and a shortened email address;
when it was signed, and whether you said no to StudioMieke's portfolio.

Attached are her terms and the agreements on the photography, as you signed them, and an evidence sheet for her. It has no IP address, browser, quote or price. She does not get your quote or your price. Jesse forwards your answers about the shoot to her. StudioMieke does not see the client workspace itself. We keep the evidence sheet for her with your other documents (article 6).

04What we use your data for

We only use your data for these purposes:

4.1Answering your question and scheduling a call.

4.2Delivering what you request: a free blog, a sample article, the giveaway or a free design.

4.3Presenting a quote, having it signed and recording the acceptance, in the client workspace.

4.4Carrying out the assignment, invoicing and keeping you informed.

4.5Being able to show who agreed to what, and when.

4.6Meeting legal obligations, such as the tax retention obligation.

4.7Securing the site and stopping abuse and spam.

4.8Seeing what works on the site, with Google Analytics and Clarity. Only after a yes.

4.9Handling your opt-out or objection.

05Legal basis per processing activity

The GDPR only allows processing with a legal basis (Article 6(1) GDPR). These are they, per processing activity.

Para.	Processing	Legal basis	Why
5.1	Contact, the check, free design and video: answering your question	Legitimate interest (f). If your question is about an assignment, also: steps before a contract, at your request (b)	You ask us something, we answer
5.2	Free blog, sample article and giveaway	Contract (b)	You request something, we deliver it
5.3	Scheduling a call	Steps before a contract, at your request (b)	You schedule a call yourself
5.4	Email	Legitimate interest (f)	Handling a conversation properly
5.5	Client workspace: company details, quote, terms, questions, files and invoice	Contract (b). If you are a contact person or signatory on behalf of a company: legitimate interest (f)	Concluding and carrying out the assignment. We need to know who we are talking to and who signs
5.6	The link, the sessions and the code by email	Contract (b) and legitimate interest (f)	Only the right person gets in and signs
5.7	IP address and browser in the evidence	Legitimate interest (f)	Being able to show who signed, if that is ever disputed
5.8	Keeping the quote, acceptance, signed documents and invoices	Legal obligation (c)	The 7-year tax retention obligation (Article 52 of the Dutch General State Taxes Act, AWR)
5.9	The nightly copy	Legitimate interest (f)	Not losing data. Also the obligation to secure data (Article 32 GDPR)
5.10	Server logs and abuse counters	Legitimate interest (f)	Securing the site
5.11	The `sc_consent` cookie and your session cookie	Legitimate interest (f). No consent needed: they are strictly necessary (Article 11.7a of the Dutch Telecommunications Act)	Remembering your choice and keeping your session secure
5.12	Google Analytics and Clarity	Consent (a)	Only after a yes, can be withdrawn under Cookies
5.13	The log of cookie choices	Legal obligation (c)	Showing that you gave consent (Article 7(1) GDPR)
5.14	Reviews with the writer's name	Legitimate interest (f)	Showing what clients think of us
5.15	Opt-out and objection	Legal obligation (c)	Honouring your objection (Article 21 GDPR)
5.16	Instagram videos	Consent (a), by your click	You choose whether the video loads
5.17	Recognising business visitors, until 17 October 2026	Legitimate interest (f)	See article 9

06Retention periods

We do not keep data longer than needed, unless the law requires a longer period.

Para.	Data	Period
6.1	A request through a form or the planner, without follow-up	12 months, unless you have told us we may stay in touch
6.2	Email	24 months after the last contact, unless the email belongs to an ongoing file or falls under a longer retention obligation
6.3	The appointment in Jesse's Google Calendar	24 months after the appointment, just like email
6.4	Client data during the collaboration	As long as the collaboration lasts. After that, we delete what is not subject to a retention obligation
6.5	Invoices and the accounts	7 years
6.6	Client workspace: quote, acceptance, signed documents, evidence sheet and the steps of the evidence	7 years after the end of the contract
6.7	Client workspace: IP address and browser in the evidence	5 years after the end of the contract. Then deleted; the evidence stays valid
6.8	Client workspace: answers and files	90 days after the end of the service
6.9	Client workspace: a quote that expires or is not signed, with the steps	3 months after the date until which the quote is valid
6.10	Client workspace: the encrypted copy of the link	Until the onboarding is complete or the link is revoked. The link itself works for 30 days
6.11	Client workspace: sessions	A session stops after 30 minutes without activity. We delete the data on a session 90 days after the last activity
6.12	Client workspace: the code by email	Valid for 10 minutes
6.13	Client workspace: after an onboarding is cleaned up	Only the date and the last fingerprint. These say nothing about people
6.14	The nightly copy, once it is switched on	35 days
6.15	The FluentSMTP log	7 days
6.16	n8n for the client workspace	None. n8n only receives a number and does not keep the runs
6.17	Web server logs (IP address, browser, time)	At most 90 days, unless an incident requires longer. This does not apply to the evidence in the client workspace (para. 6.7)
6.18	The log of cookie choices	Eighteen months: the choice is valid for 6 months, plus one year to be able to show your consent
6.19	The cookie with your choice	6 months. Then we ask again
6.20	Abuse counters	10 minutes, 1 hour for the planner
6.21	Backups that Hostinger makes itself of the site and the n8n server	A limited time, under the arrangements with Hostinger. For n8n: a backup every day, kept for 14 days
6.22	Data on business visitors from before 17 October 2026	Deleted by 15 January 2027 at the latest (article 9.3)

07Who we share data with

We only share data when that is needed for the site or our services, or when the law requires it. We have a data processing agreement with each processor. For large providers, these are their standard data processing terms.

7.1Hostinger (Hostinger International Ltd., Cyprus).

Hosts the site, the database and the client workspace files, in a data centre in France.
Hosts our n8n server, in Paris (article 7.3).
Sends the site's mail through smtp.hostinger.com and stores our mailbox.
The pages pass through Hostinger's network (CDN). That network also has edges outside Europe (article 12.2).

7.2FluentSMTP. Software on our own server, not a separate party. Passes the site's mail to Hostinger and keeps a log in our own database (articles 3.11 and 6.15).

7.3n8n. Our workflows run on our own n8n, at n8n.sharpclicks.nl, on our own Hostinger server in Paris, France.

n8n receives the requests for a free blog, a sample article, the giveaway and opting out. They come from our server, not from your browser.
n8n then sends you the email with the article or the download, through Hostinger's mail server.
n8n collects the encrypted nightly copy (article 3.13).
Traffic to n8n passes through the Cloudflare network. Cloudflare also runs the DNS of sharpclicks.nl.

7.4Google.

Google Calendar and Google Meet, for the planner (article 2.2).
Google Analytics 4, only after a yes (article 8.3).
Google Search Console, to follow how the site appears in Google. It does not place cookies on your device.

7.5Microsoft. Microsoft Clarity, only after a yes (article 8.4).

7.6Fishuals, our video partner. Jesse forwards your request for a call about video to Fishuals. Fishuals then contacts you and only uses your data for that and for the assignment.

7.7Our website partner Oh My Site. Co-manages the site. As a WordPress administrator, can see the requests from articles 2.1 and 2.2. Not the client workspace.

7.8AI services.

For the free blog and the sample article, our workflow uses Google Gemini for the text and OpenAI for the image. They receive what is needed to create the article: the topic and information about your website.
Claude by Anthropic may help when an onboarding is created (article 3.10). Anthropic is our processor for this.
For client assignments, OpenAI or Anthropic may be used. We make separate arrangements for that per project.

7.9The location of the nightly copy. The nightly copy is not switched on yet. Once it is, we will name its location here. That location only receives an encrypted copy, which it cannot open.

7.10The timestamp service: DigiCert, and if it does not respond, Sectigo or FreeTSA. Only receives a fingerprint (article 3.7).

7.11Our accounting software. We create your invoice and keep the accounts in it (article 6.5).

7.12Instagram (Meta). Only if you click on a video (article 2.8).

7.13StudioMieke, our photography partner. StudioMieke (Mieke Leemans, Coevorden, Chamber of Commerce number 87007169) takes the photos at a shoot you book through us. She only receives what she needs for the shoot (article 3.15) and only uses it for the shoot and to ask you for a review afterwards. She is responsible herself for what she does with the photos, just as we and you are each responsible for what we do with them.

7.14Supabase. The portal where clients of our blog automation review their articles uses a Supabase database in Ireland. The old data on business visitors is also still there (article 9.3).

7.15No sale. We never sell your data. We only share it with the parties above, or when the law requires us to.

08Cookies and similar techniques

8.1The notice. On your first visit, the site asks what is allowed. You choose "Accept all", "Only what is needed", or you choose per purpose. Even if you decline, the whole site works. You can always change your choice through Cookies at the bottom of every page, or with the small button at the bottom left.

8.2Necessary (always on).

sc_consent, from SharpClicks: remembers your choice, 6 months. It contains: the version of the text, your choice per purpose, the date and a random number that says nothing about you.
In the client workspace: __Secure-sck, your session (article 3.3).

8.3Measuring (off until you say yes). Google Analytics 4 counts which pages you view and how you got here. It also counts a few actions, such as a submitted form, a click on the phone number, the email address or WhatsApp, and a scheduled appointment. Cookies: _ga and _ga_*, 6 months.

8.4Recordings (off until you say yes). Microsoft Clarity records where you click and how far you scroll. Cookies: _clck, _clsk, MUID, MR, ANONCHK and SM.

8.5How we enforce your choice.

At the top of every page, everything is first set to "denied" (Google Consent Mode v2, the basic form).
The Google Analytics script only loads after a yes for Measuring.
The Clarity script only loads after a yes for Recordings. Clarity then gets its own signal that you gave consent.
If you withdraw a yes, we pass that on straight away and delete the cookies for that purpose.
We do not place advertising cookies. If they come, we update this policy and the notice, and ask you again.

8.6The log of choices. On the server we record each choice: the random number from your cookie, the date and time, the version of the text, your choice per purpose, where you chose and on which page. No IP address and no name. This lets us show that you gave consent. A record is kept for eighteen months.

8.7Only on sharpclicks.nl. The measuring tools only load on sharpclicks.nl. We keep our own visits out of the measurements with the sc_intern cookie (1 year). It is only set when someone opens a special address themselves.

8.8Other storage in your browser. See article 2.6.

8.9What is not there. No reCAPTCHA, no Google Maps map and no Google Fonts: the fonts are on our own server. Links to LinkedIn, WhatsApp and Google Maps are plain links. Instagram videos only load after a click (article 2.8).

8.10Deleting cookies. You can always delete cookies in your browser. If you delete sc_consent, the site asks for your choice again.

09Recognising business visitors

9.1Until 17 October 2026. Until that date, for a visit from the Netherlands, Belgium and Germany, the previous site checked whether the IP address belonged to a business network. If so, it recorded the organisation behind that network, with the pages viewed. The IP address itself was not stored. It also took over contact persons that a company published on its own website: at most five per company, with the page and the date.

9.2Since 17 October 2026. The new site does not do this. If we ever do it again, a new version of this article comes first.

9.3What is left. The data from before 17 October 2026 is still in the old database (Supabase) and in an overview in Google Sheets. We delete it by 15 January 2027 at the latest, 90 days after the last visit to the old site.

9.4Opting out. You can still opt out. Enter your domain name at sharpclicks.nl/privacy/afmelden, or email it to jesse@sharpclicks.nl. We put your domain on the exclusion list and delete what we already had. You do not have to give a reason: for direct marketing, objecting is always allowed (Article 21(2) GDPR).

9.5Are you such a contact person? Request access or have your data deleted through jesse@sharpclicks.nl. We delete it without you having to give a reason.

10Your rights

Under the GDPR you have these rights:

10.1Access. You may know what data we hold about you, and receive a copy.

10.2Correction. If your data is wrong, you have it corrected or completed.

10.3Deletion. You can ask us to delete your data. We do so, unless we have to keep it, for example for the tax retention obligation or as evidence of a contract (articles 6.6 and 6.7).

10.4Restriction. In some cases you can ask us to restrict the use for a while, for example while we check a correction.

10.5Objection. If we use your data on the basis of a legitimate interest, you can object. We then weigh it again. For direct marketing, we always stop.

10.6Portability. You can receive the data you gave us yourself in a common file format, to pass it on to someone else. This also applies to your answers in the client workspace.

10.7Withdrawing consent. If you gave consent, you can always withdraw it. What we did before remains lawful. For cookies, you do this through Cookies at the bottom of every page.

10.8In the client workspace. You receive your signed documents and the evidence sheet by email and can download them in the client workspace. If you want to know what the evidence says about you, ask us.

10.9How to arrange this. Email your request to jesse@sharpclicks.nl. We first check that it is you, so we do not give anything to the wrong person. You get an answer within four weeks. If it is complex, this can take at most two months longer; we will let you know in time. It costs you nothing.

11Security

We take appropriate measures against loss, access by others and misuse.

11.1Encrypted traffic. All traffic with the site goes through HTTPS. This also applies between the site, n8n and the mail server.

11.2Encrypted storage.

The permission Jesse gave Google for the planner is stored encrypted in the database.
In the client workspace, the copy of the link is stored encrypted. The nightly copy is encrypted with a key that only Jesse holds.

11.3Access. Only people who need it for their work can get to the data. Only Jesse sees the client workspace. Every administrator logs in with their own account and a strong password. Two-step verification is available in WordPress.

11.4The client workspace.

Files are outside the public folder of the site.
A session stops after 30 minutes without activity. Revoking or a new link stops all sessions straight away.
The site refuses requests that do not come from its own page.
There are limits on the number of attempts.
The pages are not in search engines and are not stored in a cache.

11.5Keeping up to date. We regularly update the software and the settings.

11.6In case of a data breach. We follow a fixed approach: establish, contain, assess and, where the law requires, report to the Dutch Data Protection Authority within 72 hours. If there is a high risk for you, we let you know.

12Transfers outside the European Economic Area

12.1Preferably within the EEA. The site, the database and the client workspace are at Hostinger in France. n8n is at Hostinger in Paris. The blog portal uses Supabase in Ireland.

12.2Hostinger's network. The pages pass through Hostinger's network (CDN). That network also has edges outside Europe, including in the US. The standard contractual clauses of the European Commission apply to this.

12.3US services. Google, Microsoft, Meta, OpenAI, Anthropic, Supabase and Cloudflare may process data outside the EEA.

12.4Safeguards. For transfers outside the EEA we use the safeguards the GDPR provides, such as the EU-US Data Privacy Framework or the standard contractual clauses of the European Commission. Which safeguard applies differs per party; feel free to ask us.

13AI and decisions by a computer

13.1No decisions by a computer alone. We do not take decisions with legal effects, or with a similarly significant effect on you, that are made by a computer alone. A person always decides on collaboration, the content of an assignment and how it is carried out.

13.2AI in our work. The free blog and the sample article are written with AI. An AI assistant helps us build and manage the site, and create an onboarding. What you fill in, upload or sign in the client workspace is not read by that assistant (article 3.10).

13.3Honest about limits. AI can make mistakes. We are honest about what AI can and cannot do, and always have important decisions checked by a person.

14Changes

14.1Why. We update this policy when the law changes, when we add or replace a service or party, or when we can arrange something better.

14.2Versions. Each version has a number: the date on which it takes effect. We will send you an old version on request.

14.3Notice. For a major change, we announce it on the site. The latest version is always on this page.

14.4Which version applies. The version that applies at the time of the processing.

15Complaints and contact

15.1First with us. Do you have a question or complaint about your data? Email jesse@sharpclicks.nl or call +31 6 117 227 50. We take it seriously and look for a solution together.

15.2The Dutch Data Protection Authority. If you think we do not handle your data properly, you can file a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP). Postbus 93374, 2509 AJ Den Haag, the Netherlands. Online at autoriteitpersoonsgegevens.nl.

15.3Other EU countries. If you live in another EU country, you can also go to the supervisory authority there.

15.4Our details. SharpClicks, Krimweg 34A, 7741 NB Coevorden, the Netherlands. Email jesse@sharpclicks.nl. Phone +31 6 117 227 50. KvK 84939842. VAT NL004034939B94.

16Language

16.1This privacy policy exists in Dutch and in English. If the two differ, the Dutch text prevails.

Questions about this privacy policy? Send us a message via the contact page or email jesse@sharpclicks.nl.