Privacy statement for Rukoo accounts

Last updated 2026-10-27. Nederlands

Who is responsible

Bart van der Meeren runs this server and decides what it does with your data. Contact: https://bvdm.ai/nl/contact.

What this service is

A Rukoo account keeps your inbox categories, the category each email got and your corrections the same on your devices that use Rukoo, the open-source mail app. If you turn it on, it also runs your booking page, where other people and their AI assistants can book time with you. Your mail, your mail passwords and your Google sign-ins never pass through this server.

What we keep

Your IP address reaches Cloudflare with every request. The server uses it to limit how often one address may try to sign in or write to a booking page, and doesn’t store it. For bookings it also counts how many came from one network that day (an IPv4 /24 or an IPv6 /64). It keeps those counts only as hashes made with a key that changes every day, and deletes them once the host’s day is over. Cloudflare may keep addresses in its own logs for a short time.

Why

We use this data to give you the account you asked for: signing in, syncing your devices and showing your devices and usage (the agreement with you, article 6(1)(b) GDPR). Rate limits and the sign-in lock protect your account and the service (a legitimate interest, article 6(1)(f) GDPR). We don’t use it for anything else: no analytics, no advertising, no profiles, and we don’t sell or share it.

Where it is kept, and who helps

The server runs on Cloudflare, a service of Cloudflare, Inc. in the United States, which processes the data on our behalf under its data processing terms. Accounts are stored and handled in the European Union. Because Cloudflare is a US company, US law applies to it, also for data kept in the EU. What it could be made to hand over is the list above: your records stay encrypted with a key Cloudflare doesn’t have. A booking page is different: what it publishes is readable, and so are a guest’s details at the moment they book (see Booking pages).

How long

We keep your account until you delete it. Delete account in Rukoo (Settings, Rukoo account) removes the account, every record and your booking page with its bookings at once. Cloudflare keeps backups of the storage that can bring back its state from up to 30 days before, so deleted data is fully gone after that. Inactive accounts aren’t deleted on their own; ask us if you want yours removed and can no longer sign in.

Your rights

You can see what is stored about you on the What’s stored and shared page in Rukoo, export everything with Export my data, change your password and delete your account yourself. For anything else, such as a copy of the data we hold or an objection, contact us. You can also complain to a data protection authority, such as the one in the country where you live. If you booked time with someone through a booking page, Booking pages below says what you can do.

Booking pages

A booking page, at an address that ends in a name the account holder picks, lets other people and their AI assistants book time with that account holder: the host. It is off until the host turns it on in Rukoo. While it is on, this server keeps what the host publishes, readable, because it has to offer times while the host’s computers are off: the host’s name, introduction, time zone and language, the meeting types with their public locations, an optional contact line, the hours the host is open and the busy times within them (to the quarter hour, without titles or other details), and when the page was last updated. The page shows the open times, never the busy times themselves.

If you book through a booking page, you are a guest. You give your name, your email address, an optional note and, when an assistant books for you, the assistant’s name. They go to the host: the host’s Rukoo puts the meeting in the host’s calendar, and the host’s calendar and mail provider, such as Google, sends you the invitation. From then on the host decides what happens with your details. The host’s Rukoo keeps its own copy, end-to-end encrypted, and deletes it 30 days after the meeting; the meeting itself stays in the host’s calendar like any other.

We handle a guest’s details to make the booking the guest asks for, on the host’s behalf (steps taken at the guest’s request, article 6(1)(b) GDPR). Limits on how often and from where bookings come protect hosts and the service (a legitimate interest, article 6(1)(f) GDPR).

This server reads a guest’s details once, when the booking is made, to seal them: it encrypts them with a key that only the host’s devices hold, and keeps only that sealed copy. A later leak of the storage, a backup or a break-in afterwards doesn’t reveal them. But the details do pass through the server readable at the moment of booking, so the operator, or someone who has broken into the server at that moment, could read them then. Next to the sealed copy the server keeps the booking’s time, meeting type and status, how it was made (the web page, the JSON API or MCP), a hash of the key in the guest’s manage link, and, while the booking is active, a hash of the guest’s email address bound to that time, so the same booking isn’t made twice.

A booking stays on this server until 30 days after the meeting. When the guest cancels, the host declines or a request lapses, the sealed details and the email hash are deleted at once; the rest goes 30 days later. When the host turns the page off or deletes their account, the page and all its bookings are deleted.

A guest can cancel the booking with the link on the page they saw after booking; that deletes their details from this server straight away. For what the host does with them, contact the host. For anything about the copy on this server, contact us.

Hosts write their own pages; we don’t check them. To report a page that pretends to be someone else or is abusive, use Report this page at the bottom of it, or contact us.

Security

Your password goes through Argon2id on your device, and your records are encrypted with AES-256-GCM before they leave it. We can’t reset your password: without your password or your recovery key, nobody can open your data, including us. The Rukoo account protocol describes exactly how it works.

Changes

When this statement changes in a way that matters to you, the date at the top changes too.