Who is responsible
Pavel Mihutski, a self-employed professional (autónomo), NIF Z0725496N, Alameda 65, Valencia, Spain. The site rnd.energy is mine, and I am personally responsible for the data on it. For any question about data, write to me at pavel@rnd.energy, on Telegram, WhatsApp or through the contact form. More about the owner of the site: Legal notice (aviso legal).
In short
I do not sell data, I do not show ads, and I do not pass your data to anyone other than the services the site runs on and the channel you chose for my reply. The tools calculate in your browser. There are no cookies for advertising, tracking or statistics on this site.
When you just read the site
- The site’s hosting (Cloudflare) receives your IP address and browser details: a page cannot be delivered without them, and the hosting also uses them to protect the site from attacks.
- My own visit counter counts views and visitors per day: which page was opened and which site you came from (the site’s name only, never the full link). Your IP address and browser are used only so you are not counted twice in one day and the count cannot be inflated: the site mixes them with a random code that changes every day and turns them into a mark (a hash). The IP address itself is not stored, and the day’s code and the marks are deleted the next day. After that, a mark can no longer be linked to you or to other days. Only the numbers per day remain. If you opened the site through my personal link with a tag like ?from=p126, the counter records that tag with the views in that tab: that is how I see that a link I sent to a particular person was opened and which pages were read through it. The tag holds no name, only a number from my address book; what remains are numbers per tag, page and day.
- Umami, a statistics service without cookies, receives the page address without parameters, the address of the page you came from, the page title, your browser’s language and screen size, which browser, system and kind of device you use, and event names such as “tool result shown”. An event name may include the kind of business, the tool tab or the decision topic you picked, but never your numbers or texts. From the IP address and the browser details Umami makes a mark that changes every month, so it can tell repeat visits apart within one month. It uses the IP address to tell the country, region and city and, by its own description, does not store the address itself.
- Neither my counter nor Umami counts the private case review pages. They count the private Founder Camp programme page like any other page, without the invitation number.
- Fonts load from Google Fonts, so Google sees your IP address when the page loads.
Legal basis: my legitimate interest in keeping the site working and protected, and in seeing which materials people read. You can object at any time: open rnd.energy/?stats=off in this browser, and neither my counter nor Umami counts it any more. To turn counting back on: rnd.energy/?stats=on.
Calculations in the tools and the decision record
The tools calculate in your browser, and the numbers you enter go nowhere until you send the form with the calculation yourself (see below). Decision records are kept in your browser on this device, the latest hundred at most, and in any files you download yourself. You can delete one record with “Delete” in “My decisions”, or all of them by clearing the site’s data in your browser.
The ball (no longer on the site)
Until 18.10.2026 the home page had a decision ball. It is no longer on any page of the site: nobody can throw it, type a question for it or mark reasons any more, so none of that reaches me now. While it was on the site it worked like this, and what it counted remains as numbers per day:
- The question you typed for the ball stayed in your browser. It went further only if you pressed “Tell me about your situation”, “Discuss taking part in a venture” or “write the decision down yourself”: then the question, the ball’s answer and the reasons you marked were carried over in that tab into the contact form, the form on the ventures page or the decision record. The form went only when you sent it.
- When you pressed “Lock in my answer”, the site counted which reasons were marked, without you and without your texts. Only the numbers per day remain, for example “fear of missing out: 3”. I look at the reasons for a day when at least five people marked them, and otherwise for a week, again only from five people, so nobody’s answers can be recognised in them. So that the count could not be inflated, one IP address added no more than twenty answers a day: for that the site made a mark of the day the same way the visit counter does, and deleted it the next day.
- My counter also counted the ball’s steps per day: how many people opened the home page and threw the ball, how often it landed on YES and NO, how many people locked in an answer and followed the links in it, and how often. To tell people apart within one day, the site made marks of the day the same way the visit counter does, separate from its marks, and deleted them the next day. Only the numbers per day remain.
- Umami received event names only: whether the ball was thrown, whether it landed on YES or NO, whether a question was typed (never the question itself), whether you pressed “Lock in my answer”, which topic you picked and which link you followed. Which reasons you marked, Umami never received.
Legal basis is the same as for statistics: my legitimate interest in seeing what people base their decisions on, which is the subject of my research. It switched off the same way: rnd.energy/?stats=off.
When you press “Send”
What goes: your name, the reply channel and contact you chose, your message, what you picked in the form (for example a service or your role), the page you wrote from, and the tags of the link you came through (utm or my personal from tag), if there were any. On tool pages the form has a box “Attach the calculation shown below”. It is ticked from the start: while it stays ticked, the calculation shown in the form goes too, as a separate part. Untick it if you do not want to send it.
Your name, a reply channel with a contact, a message and consent are required: without them I cannot reply. Everything else is optional.
All of it is stored in a database on the site’s hosting (Cloudflare). I get a Telegram notification with the whole request: name, contacts, message and calculation. I move the request into my own work system on my computer and reply through the channel you chose.
Why: to reply to your request and, if we agree, to start the work. Legal basis: the consent you give with the box in the form, and the steps before a contract that you asked for yourself. No newsletter and no passing it on to anyone else. If you do not want your request to go through Telegram, email me directly instead.
Booking a call in Google Calendar
Many pages, and the message after you send a form, have a link to book a call. Booking happens on a Google Calendar page: you enter your name, email and time there. The booking lands in my calendar and mailbox, which Google runs for me. I use these details for the call you asked for and keep the booking the same way as a request. Legal basis: the steps before a contract that you asked for when you picked a time.
Case review
If I sent you a private link to a case, the form there sends your name, contact and reply channel, your role and company, your answers and corrections, your decision on how the case may appear, a written review, and a video or a link to one if you add them. All of it, the video included, is stored on the site’s hosting (Cloudflare). I get a Telegram notification with your whole answer, without the video file itself. This is so the case is published only in the form you agreed to. Legal basis: your consent. If you withdraw it, I take the case off the site and stop using your materials.
The private Founder Camp page
I open the Founder Camp programme by personal invitation: a personal password that I send myself. The password tells me whose invitation it is. When you ask for the details on the open page, the site at once makes the next invitation number and a password for the request. The database keeps the number, its link to the request, the name on the request and hashes of the password; the password itself comes only to me in Telegram with the request, and I forward it to you if I invite you. When the password is accepted, I get a Telegram notice with the invitation number, the name I gave it to and the page language, so I know the invitation arrived. That notice has no password in it. So that you are not asked again, your browser keeps a cookie for 30 days. A request sent from that page is handled like any other request. Legal basis: my legitimate interest in knowing that an invitation I sent personally was opened.
New materials by email
Your email, language, the page you subscribed on and your role, if you gave it, are stored separately from requests and used only to write about new materials. I get a Telegram notification about each new subscription. Legal basis: your consent. To unsubscribe, reply to any email or write to me.
Spam protection
So the request forms and video uploads cannot be flooded, and the password of a private page cannot be guessed by trying again and again, the site counts attempts from one IP address per hour. What is kept is not the IP address itself but a hash of it, for no longer than two days. Legal basis: legitimate interest in protecting the site.
Who else sees data
- Cloudflare: hosting, database, video storage and page delivery.
- Telegram: my notifications about requests, case reviews and subscriptions come through it, with their contents, and so do notices that a personal Founder Camp invitation was opened.
- Umami: visit statistics without cookies.
- Google: fonts, call booking in Google Calendar, and my email, when I reply to you by email or write about new materials.
- WhatsApp, Telegram or LinkedIn, if you chose one of them for my reply: I answer you there, and our conversation goes through that service under its own terms.
Cloudflare and Google are in the United States and work under the EU-US Data Privacy Framework, for which the EU has an adequacy decision. Telegram, Umami, WhatsApp and LinkedIn may store data outside the EU. Apart from these services, nobody sees the data, and it is never used for advertising.
How long it is kept
- A request and a call booking: while we talk and work together. If no work starts, no longer than two years after the last contact. If we worked together, I keep the correspondence and work documents for as long as Spanish accounting and tax rules require.
- A case review: while the case is published, or until you ask for it to be deleted. If the case is never published, no longer than two years after the last contact.
- A notice that a Founder Camp invitation was opened: like a request, no longer than two years after the last contact.
- A subscription: until you unsubscribe.
- Marks of the visit counter and the ball: until the next day. The numbers per day remain, and they hold nothing about you.
- Spam protection: up to two days.
- Umami statistics: six months, then Umami deletes them.
- Cloudflare’s technical logs and Google Fonts requests: under the rules of these services.
Your rights
You can ask to see what data of yours I have, to correct it, to delete it, to restrict or stop its processing, and to get it as a file. You can withdraw consent at any time: from then on I stop using the data for that purpose, and what was done before stays lawful. Write to me at pavel@rnd.energy, on Telegram, WhatsApp or through the contact form, and I will reply within a month, usually sooner. If you believe I have breached your rights, you can complain to the Spanish data protection agency (AEPD, aepd.es).
Automated decisions
The site makes no automated decisions about you and builds no profiles.
Cookies
Exactly what the site keeps in your browser is listed on the page Cookies and browser storage.
Co-Manager Light
It is a separate service with its own data terms. Read them on the service itself before uploading any chats.
Changes
If the site starts handling data differently, I will update this page. The date of the last update is at the bottom.