Privacy Policy

Privacy statement (privacyverklaring). This explains what Ridoco does with personal data, under the General Data Protection Regulation (AVG). Last revised 26 October 2026.

1. Who is responsible

The controller (verwerkingsverantwoordelijke) is:

Ridoco, a Dutch sole proprietorship (eenmanszaak)
De Nieuwe Erven 3-12572, 5431 NV Cuijk, Netherlands
Chamber of Commerce (KvK) 95439609, VAT identification number (btw-identificatienummer) NL005153257B49
Email: contact@ridoco.com
Phone: 06 49154776, from outside the Netherlands +31 6 49154776

There is no data protection officer, and none is required. Art. 37 AVG requires a DPO for public authorities, for organisations whose core activity is large-scale regular and systematic monitoring of people, and for large-scale processing of special categories of data. Ridoco is a one-person business that builds websites and does IT and security work. None of those conditions apply. Questions go to contact@ridoco.com and are answered by the person who runs the company.

2. What is processed, why, and for how long

2.1 Your account

Data: username, display name, email address, a one-way hash of your password (never the password itself), and anything optional you choose to fill in such as an avatar, a short description, social links or a date of birth. Date of birth is private by default.

Why and on what basis: to give you the account you asked for and to let you sign in, art. 6(1)(b) AVG, performance of a contract with you.

How long: while the account exists. Deleting it is covered in section 7.

2.2 Support tickets, and their attachments

Data: the subject and body of your ticket, the category and any tags, every reply on the thread, and any files you attach, up to three per message. Attachments often contain more than people expect: screenshots of a desktop, an exported configuration, a log file, an invoice. Whatever you send is what is stored.

Where the files live: attachments are written to a private area of the server that sits outside the public web root. They have no public URL. They can only be reached through a route that first checks the request belongs to the person the ticket belongs to. They are not sent to any third party.

Why and on what basis: to answer you and to carry out the work, art. 6(1)(b). Where the ticket is not about a contract, art. 6(1)(f), the legitimate interest in running a support channel at all.

How long: kept with your account so the history of a job stays readable. A ticket that evidences a paid job forms part of the record of that transaction and follows the seven year rule in 2.5. You can ask for a specific attachment to be deleted at any time and it is deleted.

2.3 Bookings

Data: the name and email address you enter, your time zone, any notes you add, the slot you chose, and a random token that is part of your management link so you can change or cancel the appointment without an account. For a visit to your address the booking also records the street and number, the postcode, the town, a telephone number, and the province you pick for the travel charge.

Why and on what basis: art. 6(1)(b), a step taken at your request before a contract.

How long: for as long as the appointment and any follow-up are relevant, and removed on request. A booking that turned into a paid job becomes part of the record of that job.

2.4 The contact form, and WhatsApp

Data: your name, email address, subject and message, plus the company name and telephone number when you fill those in.

Why and on what basis: to answer you, art. 6(1)(f) and, where you are asking about work, art. 6(1)(b).

How long: what you send is recorded as a support ticket on this site and emailed to the operator. The ticket is kept as long as the correspondence is relevant and is removed on request. The email in the mailbox is kept on the same footing.

WhatsApp: the footer of every page offers WhatsApp as a way to make contact. If you use it, the conversation runs over a service operated by WhatsApp Ireland Ltd, part of Meta, and their terms and privacy statement apply to it alongside this one. What is processed there is your phone number, which is how the service identifies you, and whatever you send. The message content is end-to-end encrypted between the two devices; the fact that you made contact, when, and from which number is not. The chat stays on both phones until it is deleted at either end. Same legal bases as above. If a question involves documents, account details or anything you would rather not put through a third party's messenger, use email or a support ticket instead. Ticket attachments stay on this server, see 2.2.

2.5 Orders, invoices, and withdrawal statements

Data: what you bought, amounts, currency, VAT treatment and rate, the capacity you declared (consumer or business) and for a business the company name and the KvK and VAT numbers, the payment status and a payment reference, the IP address recorded at the time of the order, and the timestamps that decide a withdrawal deadline. Where the site asks you to confirm a statement before buying, the exact wording you agreed to is stored together with a hash of it, the time, your IP address and your browser user agent.

If you withdraw from a contract, the withdrawal statement is stored: your name, which contract, the contact address you gave, the text of your statement, the time it arrived and whether it was inside the deadline.

Why and on what basis: art. 6(1)(b) to perform the contract, and art. 6(1)(c) because Dutch tax law requires the administration to be kept. The consent records exist to prove later what you were shown, art. 6(1)(f), legitimate interest. The withdrawal records exist to meet obligations under consumer law, art. 6(1)(c).

How long: seven years from the end of the financial year, the retention period for business records under Dutch tax law. These records are not deleted on request during that period. The obligation to keep them overrides the request. Everything else about you still is. The IP address and browser user agent on a consent record are deleted two years after the contract ends; the wording, its hash and the time stay for the seven years.

2.6 Care plans and other subscriptions

Data: the plan, the billing interval and amount, VAT rate and country, a VAT number for reverse charge where it applies, the start date, the current billing period, and the dates of any cancellation, payment failure or suspension.

Why and on what basis: art. 6(1)(b) and art. 6(1)(c) for the invoicing part.

How long: while the plan runs, then under the seven year rule in 2.5 for the parts that are invoicing records.

Data: your email address, where you signed up, a one-time confirmation token, and the dates you subscribed, confirmed and unsubscribed.

Why and on what basis: art. 6(1)(a), your consent. Sign-up is double opt-in: nothing is sent until you click the link in the confirmation email. An address entered by someone else never receives anything.

How long: until you unsubscribe. Every mailing carries an unsubscribe link. The record that you consented, and when, is kept afterwards as proof that the mailings were lawful.

2.8 Comments and anything else you post

Data: what you wrote, when, and the account it was posted from.

Why and on what basis: art. 6(1)(b): publishing what you posted is what you asked for. Art. 6(1)(f) covers moderation.

How long: while it is published. Removed on request, or by moderation.

2.9 Server and application logs

Data: the web server records requests with an IP address, a timestamp, the page requested and your browser user agent. A signed-in session is stored server side with the IP address and user agent it was created from. Application error logs may contain a URL, an account id and a technical stack trace. Automated calls to outside services made on your behalf are logged with the endpoint and the result.

Why and on what basis: art. 6(1)(f). The interest is keeping the site working, finding faults, and dealing with abuse such as brute force login attempts and spam. Logs are not used to build a profile of you and are not used for marketing.

How long: a signed-in session expires after 120 minutes of inactivity. Web server logs are deleted after 8 days at most, application and error logs after 90 days at most.

2.10 Cookies

Covered in section 3, and in full in the Cookie Policy.

2.11 Reviews from Google

Data: the homepage can show reviews that people left for Ridoco on Google. Ridoco fetches them from its own Google Business Profile once a day and shows them as written: the name the reviewer uses on Google, the stars, the text, the date, and Ridoco's reply. Google's own average score and review count are shown with them. The reviewer's profile photo is left out, and a review posted anonymously is shown as "Google user".

Why and on what basis: art. 6(1)(f), legitimate interest. The interest is showing visitors what customers say about Ridoco's work, taken from the place where they chose to publish it. The reviews are already public on Google, and nothing is added to them.

How long: each copy is refreshed by the daily fetch and deleted no more than 30 days after it was last fetched. A review that is changed or deleted on Google changes or disappears here at the next fetch. A review Ridoco copies by hand from the original is marked on the page as typed up, and stays until it is removed or you ask for its removal.

Objecting: you can object at any time under art. 21 by writing to contact@ridoco.com and naming the review. Ridoco then removes it from this site and keeps only Google's reference number for it. The daily fetch uses that number to skip the review. The review is not stored or shown here again. Ridoco keeps the number until the daily fetch reads Google's complete list of reviews and the review is no longer on it, and deletes the number then. The objection stays in force while the reviews section or the daily fetch is switched off. You can also change or delete the review on Google yourself, and this site follows at the next daily fetch.

2.12 Appeals against a moderation decision

Data: when you lodge an appeal at /appeal: the email address you give, which kind of decision you are appealing, its reference and date if you give them, what you write, the time it was lodged, your IP address and your browser user agent, and later the outcome, the reasons for it and when it was decided. The link in the confirmation email carries that email address. A cookie holding the same address lets the browser you lodged the appeal from open it without the address in the link; see section 3. Lodged while signed in with the same address, the appeal is also filed as a support ticket on your account, which 2.2 covers. When an account is suspended, the decision and the reasons for it are recorded and sent to the email address on the account.

Why and on what basis: art. 6(1)(c) for the reasons that go with a suspension, which article 17 of the Digital Services Act requires. The appeal itself: art. 6(1)(f), the interest in looking at a decision again and being able to show that it was answered. The IP address and user agent are there to deal with abuse of a form anyone can use without an account.

How long: an appeal is kept for one year from the day it was lodged. If you ask for erasure within that year, your IP address and user agent are removed straight away and the rest of the record when the year is over. The record of a suspension and its reasons is deleted automatically after one year.

2.13 Bug reports

Data: what you enter in the bug report form: a title, how bad the problem is, what happened, and the address of the page it is about. When you are signed in, the report is linked to your account.

Why and on what basis: art. 6(1)(f). The interest is finding and fixing what is broken on this site.

How long: for as long as it helps to keep the site working. Removed on request.

2.14 Requests for a partner's service

Data: what you enter when you ask for a service a partner delivers, on the page Services through partners: your name and email address, your phone number and company if you give them, the date or period, the number of people, your message, which offer it is about, and the moment you asked for it to be passed on.

Why and on what basis: to pass your request to the partner who delivers the service. Art. 6(1)(b), a step at your request before a contract; ticking the box on the form is your instruction to pass it on. Ridoco receives a fee from the partner when a request leads to an order, and keeps track of which orders came through this site for that reason. Keeping that record rests on art. 6(1)(f): the interest is that the partner pays Ridoco for a customer Ridoco refers. You can object to it at any time under art. 21 by writing to contact@ridoco.com. What was passed on before stays with the partner; ask the partner to delete it.

How long: deleted no more than 18 months after it arrives. That is the period in which a partner pays a fee on orders, plus the time to settle it. For a request that led to an order, the amounts and the fee stay in Ridoco's records without your details. A request held as spam is deleted after 30 days.

2.15 RidoGuard

Data: RidoGuard, the free Windows tool, checks for updates. The check is a standard web request to GitHub, where the releases are published, with no identifier in it. GitHub (GitHub, Inc., United States) sees your IP address when your PC makes that request. RidoGuard sends nothing to Ridoco.

Why and on what basis: art. 6(1)(f), legitimate interest. The interest is that you get security fixes.

Switching it off: from version 1.3.0, turn off Check for updates when RidoGuard starts on the About screen. RidoGuard then contacts GitHub only when you press Check for updates yourself.

3. Cookies

This site sets a small number of first-party cookies and nothing else.

Cookie	What it does	How long
`ridoco_session`	Keeps you signed in during a visit. Required.	Session, 120 minutes of inactivity
`XSRF-TOKEN`	Stops another site from submitting forms as you. Required.	Session
`remember_web_*`	Set when you tick "remember me" when signing in, and every time you sign in with a social account.	Long lived, cleared when you sign out
`cookie_consent`	Remembers the choice you made in the cookie banner. You are not asked again.	1 year
`appeal_email`	Set only when you lodge an appeal at /appeal. Holds the email address you gave. The link in the confirmation email reads it to open the appeal.	30 days

All five are strictly necessary or are a direct record of your own choice. No analytics cookie is set and no analytics script is loaded. No analytics measurement id is configured, so nothing is sent anywhere. If that ever changes, the analytics cookies would only be set after you accept them in the banner, and this section and the Cookie Policy would be updated before it happened.

Blocking the first two cookies in your browser will stop you from signing in.

4. Who else handles your data

Hosting. The site and its database run on a virtual private server rented from a hosting provider inside the European Union, which acts as a processor under a data processing agreement. The provider's name is given on request.
Email. Messages the site sends you, confirmations, ticket notifications, invoices and newsletter mailings, go out through an SMTP mail provider for the ridoco.com domain, which acts as a processor. Email you send to contact@ridoco.com arrives in that same mailbox.
Payments. Quoted work is invoiced, and an invoice is paid by bank transfer, which involves your bank and Ridoco's bank and nobody else. An order placed on this site is paid online through Mollie. Mollie B.V. in Amsterdam is a payment service provider and an independent controller for the payment data it holds. You enter your card or bank details on the provider's own payment page, and they never reach this site. This site sends the provider the amount, a description of the order and references that tie the payment to the order, one of them the number of your account on this site. Your name and email address are not sent. What comes back is the status of the payment, the amount and the provider's reference for it, and those are kept with the order. Basis: art. 6(1)(b) to take payment under the contract, and art. 6(1)(c) for the payment record Dutch tax law requires. How long: seven years, with the order, as in 2.5. What the provider keeps itself falls under its own privacy statement.
Error monitoring. When the software on this site fails, a report of the failure goes to Sentry (Functional Software, Inc., San Francisco, United States), which acts as a processor. The report is sent to Sentry's European region and stored in Frankfurt, Germany. It holds the error, the stack trace, the address of the page with any token or email address in it removed, and the shape of the database statement without the values in it. Your name, your email address, your IP address, your cookies and anything you typed into a form are not part of it. Sentry runs on the server and not in your browser. Your browser sends nothing to it. For 1 in 100 requests, a timing of the request also goes to Sentry, with the same limits.
Notifications to the owner. When an order is paid, a quote is accepted, a Care plan starts, is paid or falls behind on payment, a refund is made, a partner request comes in, a withdrawal is received, a booking, support ticket, cancellation request or bug report comes in, or a Website rental contract is signed or cancelled, the owner gets a message through Discord (Discord Inc., United States). For Website rental there is also one when your domain is live on Cloudflare, and one when it still does not point to Cloudflare 21 days after it was added. The message holds a reference, an amount, the name of the product or plan, a label such as a priority and a link to the admin screen, and for Website rental whether you rent as a business or a consumer and the dates of the contract and the domain. It never holds your name, your email address, other contact details or anything you typed. The transfer to the United States runs under the EU-U.S. Data Privacy Framework, as Discord's privacy policy states.
Partners you ask for. When you ask for a partner's service and tick the box that asks for it, Ridoco passes your request to that partner (see 2.14). The partner is not a processor for Ridoco. It decides itself what it does with your details, under its own privacy statement.
Domains for Website-huur. If you rent a website, the DNS records of your domain sit in a Cloudflare account Ridoco manages (Cloudflare, Inc., San Francisco, United States), which acts as a processor. Cloudflare holds the domain name and its records, such as the site's address and your mail records. The site itself does not run through Cloudflare.

Present in the software, and not in use. This site is built on a general purpose platform that also ships optional integrations: two further payment providers, Stripe and PayPal, a set of social sign-in buttons, and an analytics tag. None of them has credentials configured here. Without keys they cannot connect, and they receive no data.

Data is disclosed to nobody else, and it is never sold. It can be disclosed to an authority where a legal obligation or a valid legal order requires it, and to an accountant or a lawyer bound by professional secrecy where that is necessary.

5. Third-party requests, and transfers outside the EEA

Opening a page on this site makes requests to this domain only. The fonts are self-hosted, not loaded from a font network. There is no analytics tag, no advertising pixel, no embedded tracker, no CDN and no chat widget. That means no third party learns your IP address, your browser or which page you were reading, simply because you visited.

This is about what these web pages load. It does not cover the network between you and the server, or what happens after you follow a link or send an email.

Transfers outside the EEA: the server is in the EU and the processors named in section 4 store your data in the EU. Two exceptions. Sentry: the error reports stay in its European region in Frankfurt, and the company behind it is established in the United States. Its staff can reach that region to support and administer the service. That access runs under the European Commission's standard contractual clauses, and Sentry is certified under the EU-U.S. Data Privacy Framework. Discord: the notifications to the owner in section 4 go to Discord Inc. in the United States, under the EU-U.S. Data Privacy Framework. Apart from those two and the Website-huur domains below, no routine transfer of personal data outside the EEA takes place through this website. If that ever changes, this section says so first, and names the transfer mechanism used.

Website-huur: Cloudflare, Inc. is established in the United States and keeps DNS records on its worldwide network. That transfer runs under the EU-U.S. Data Privacy Framework, with the European Commission's standard contractual clauses in Cloudflare's data processing agreement as the fallback.

6. Your rights

You have the right to see your data (art. 15), correct it (art. 16), have it erased (art. 17), restrict how it is used (art. 18), receive it in a portable format (art. 20), object to processing based on legitimate interest (art. 21), and withdraw consent at any time without that affecting what was done before.

Routes that exist on this site right now:

See and take your data. Signed in, download a copy of your data as a JSON file. It contains your profile, linked accounts, orders, subscriptions and newsletter status.
Correct it. Signed in, edit your profile under Account.
Erase it. Signed in, delete your account from the profile edit screen. It asks for your password. What happens next is section 7.
Withdraw marketing consent. Use the unsubscribe link in any mailing, or the revoke consents action in your account.
Anything else, including access, restriction, objection or an erasure request without an account: email contact@ridoco.com.

A request is answered within one month (art. 12(3) AVG). If a request is complex, that can be extended by two months, and you are told inside the first month if it is. There is no charge. You may be asked to confirm who you are, and no more than that.

7. Deleting your account

Immediately. Deleting your account signs you out, closes it, removes it from the site, and revokes any linked sign-in providers so the account cannot be re-linked.
Then. The identifying fields on the record, the username, display name and email address, are overwritten so the record no longer points at a person. The row itself is kept. Orders, subscriptions, invoices and download history hang off it, and that accounting record has to survive under 2.5.
Who does that. An automatic sweep overwrites those fields 30 days after deletion, and it is switched on for this site. Ridoco also does it straight away if you email contact@ridoco.com and ask. Ask for written confirmation when it is done and you get it.
What survives. Invoicing and order records under 2.5, for seven years, under Dutch tax law. Newsletter consent records, as proof that mailings were lawful. Anything you published that others replied to may be kept in anonymised form.

8. How the data is protected

Traffic to the site is encrypted with TLS.
Passwords are stored as one-way hashes and cannot be read back, by anyone, including Ridoco.
Ticket attachments and other uploaded files sit outside the public web root with private visibility, behind an ownership check.
Pages are served with a content security policy. It defaults to this site only, runs scripts from a per-response nonce, blocks plugins outright, and confines background connections to this domain. It is inherited from the platform Ridoco builds on and it still permits a short list of outside hosts that these pages do not use: a script CDN for an editor component, Google's font servers, video and audio embed frames, and the form targets of payment providers that carry no credentials here. What these pages actually request is in section 5: this domain only.
Sign-in, password reset, ticket submission and other sensitive actions are rate limited against brute force and abuse.
Access to the administration side is limited to the one person who runs the company.

If a data breach occurs that is likely to present a risk, it is reported to the Autoriteit Persoonsgegevens within 72 hours, and where the risk to you is high you are told directly.

9. Children

Ridoco sells services to adults and to businesses. This site is not aimed at children, and personal data is not knowingly collected from a child. If you believe a child has created an account here, write to contact@ridoco.com and it is removed.

10. Complaints

If you think your data is being handled wrongly, say so to contact@ridoco.com first.

You always have the right to lodge a complaint with the Dutch supervisory authority, the Autoriteit Persoonsgegevens in The Hague (autoriteitpersoonsgegevens.nl), or with the supervisory authority in the EU country where you live or work.

11. Changes to this statement

This statement changes when what Ridoco does changes. Revisions are recorded with a date. The version that applied at a given moment can be produced. A change that materially affects you is announced.

The terms that govern the work itself are at Terms of Service.

This version has been in effect since Oct 26, 2026. Back to top ↑