Privacy policy
Effective from October 6, 2026
Who is the controller of your data
This policy explains how we process the personal data collected on the Enjoy the Process website.
The controller of personal data collected through this website is Mindful Creations Andrzej Dobrucki, operator of the Enjoy the Process website, Dyzin 15D, 05-430 Celestynów, Poland, tax number (NIP): 8371639628. For data-related matters: Andrzej Dobrucki, hello@enjoytheprocess.pl.
We have not appointed a Data Protection Officer (DPO).
Why and on what legal basis we process data
Replying to a message from the contact form. The basis is our legitimate interest in conducting correspondence (Art. 6(1)(f) GDPR) and, where the message concerns entering into a contract, taking steps at your request prior to entering into it (Art. 6(1)(b) GDPR). After replying, we keep the message for the period given below, so that we can refer to the earlier correspondence if you write again (Art. 6(1)(f) GDPR).
Booking a consultation. The basis is taking steps at your request prior to entering into a contract (Art. 6(1)(b) GDPR). A booking must be confirmed with the button in the email we send to the address you give. Until then the slot is held for 30 minutes, and the data reaches neither Google Calendar nor the members of our team. Once confirmed, the appointment is added to the controller's calendar held in Google Calendar. After the consultation has taken place or been cancelled, we keep the booking details for the period given below, to handle further correspondence about the consultation and to establish, exercise or defend any legal claims. The basis is our legitimate interest (Art. 6(1)(f) GDPR).
Protecting forms and bookings against abuse. The basis is our legitimate interest in keeping the website secure (Art. 6(1)(f) GDPR). We count how many times a given IP address has sent the contact form, booked, confirmed or cancelled an appointment, checked available slots, tried to sign in to the admin panel, recorded an analytics event, or reported a Content Security Policy (CSP) violation — once the limit is exceeded, further attempts are temporarily refused. When the number of bookings in the last 24 hours exceeds the daily limit, the administrator receives a notification that contains no data about the people booking.
Security event log. The basis is our legitimate interest in keeping the website secure (Art. 6(1)(f) GDPR). We record when a booking was confirmed or cancelled with the button in an email — the entry contains only the booking number, without an IP address, name or email address. We also record attempts to sign in to the admin panel and rejected calls to the website's automated-task endpoints (both with a hash of the IP address made with a secret key), password changes and the runs of the website's automated tasks. We also record the administrator's own actions in the panel — deleting a message or a booking, sending a reply, releasing or erasing a person's data at their request — with the number of the record they concern, or the count of records involved, never their content.
Website usage statistics. The basis is our legitimate interest in understanding how the site is used (Art. 6(1)(f) GDPR). The statistics use no cookies or other identifiers stored in your browser. Your IP address and browser (user agent) are processed only as a pseudonymised hash computed from a fixed, secret key and the current date — within one day the same hash lets us recognise a returning visitor, and without that key visits on different days cannot be linked.
The hello@ mailbox in the admin panel. When synchronisation of the hello@ mailbox with the admin panel is switched on, the panel keeps copies of messages received at that address, sent from it and archived in it — including their content, the sender's and recipients' data, the date, and the file name, type and size of any attachments (never the attachment's own content). The basis is our legitimate interest in the administrator's handling of correspondence in the panel (Art. 6(1)(f) GDPR). The originals of these messages in our mailbox at our email provider are kept separately.
Backups of the website database. The basis is our legitimate interest in the availability and integrity of the data — being able to bring the website back after a failure and to check that a backup can actually be restored (Art. 6(1)(f) GDPR).
Erasure register. To be able to demonstrate and honour an erasure carried out at your request (Art. 5(2) and Art. 17 GDPR), we keep, indefinitely, a pseudonymised hash of your email address, created with a secret key (HMAC), and the erasure date, and, for erased email messages, the same kind of hash of their technical identifier (Message-ID). Neither the address nor the content of a message can be read from this record; it exists solely so that erased data does not return to the database. The legal basis is Art. 6(1)(c) GDPR, in conjunction with Art. 17 and Art. 5(2) GDPR. If you write to us again or book an appointment after an erasure, we process that new data under the ordinary rules.
Web server access logs. The server that runs the website records, in its technical (nginx) logs, the full IP address, the requested URL and the browser (user agent) of every request, for up to 15 days. The basis is our legitimate interest in keeping the website secure and in diagnosing infrastructure issues (Art. 6(1)(f) GDPR).
The required checkbox in our forms. Ticking the required box on the contact form and the booking form confirms that you have read this notice — it is not consent within the meaning of Art. 6(1)(a) GDPR. We process the data sent through the forms on the bases described above for each purpose.
Where we store your data
The server that runs the website and its database is located in the United States — its provider is OVH US LLC. This transfer of data outside the European Economic Area rests on the European Commission's adequacy decision for the EU-US Data Privacy Framework (Art. 45 GDPR), in which OVH US LLC participates as a certified organisation; the list of participants is public at dataprivacyframework.gov.
The hello@ mailbox and our outgoing email use the service of Proton AG, based in Switzerland; the basis for this transfer is the European Commission's adequacy decision for Switzerland.
Google Calendar and Google Drive are provided by Google Ireland Limited, based in Ireland; to the extent data reaches its US parent company, Google LLC, the basis for that transfer is Google LLC's participation in the EU-US Data Privacy Framework.
For each of these transfers you can ask for information about the mechanism used, and — where we rely on additional safeguards such as standard contractual clauses — for a copy of them; write to the contact address given above.
What data we collect
From the contact form: name, email address and message body, and also the language of the site version (Polish or English) the form was sent from. With a message we also store a pseudonymised hash of your IP address, from which the address cannot be recovered without the secret key. The hash is computed from a fixed, secret key and the current date and lets us recognise a series of submissions from one source on the same day. When booking: name, email address, the chosen slot, your time zone, the topic and the language of the site version (Polish or English). With a message or a booking we store the date it was sent and the version number of the privacy policy in force at that moment. In the attempt counters used to prevent abuse — covering the contact form, bookings, confirming a booking, cancelling a booking, checking available slots, signing in to the admin panel, analytics events and CSP violation reports — a pseudonymised hash of your IP address made with a secret key, from which the address cannot be recovered without that key, and the number of attempts within a time window. In usage statistics: the event type (a page view, a contact form sent, or a booking made), the page path, language, referring source together with any UTM parameters (if the visitor arrived through a link carrying them), device type, and a pseudonymised hash of your IP address and browser (user agent), computed from a fixed, secret key and the current date, from which the address cannot be recovered without that key. In the security event log: the type and time of the event, the booking number (when a booking is confirmed or cancelled), a hash of the IP address made with a secret key (for attempts to sign in to the admin panel and for rejected calls to automated-task endpoints), and, for the administrator's own actions in the panel, the number of the record they concern or the count of records involved. In the web server's access logs: the full IP address, the requested URL and the browser. When the hello@ mailbox in the admin panel is switched on: the content of messages received at that address, sent from it and archived in it, the sender's and recipients' data, and the file name, type and size of any attachments (never their content). In the erasure register: pseudonymised hashes of your email address and of the technical identifiers of erased messages, and the erasure date.
Who we share data with
The provider of the server that runs the website and its database is OVH US LLC (United States). The hello@ mailbox and our outgoing email are handled by Proton AG (Switzerland) — that provider is where mail arriving at hello@ physically sits before a copy of it reaches the admin panel. For appointment booking we use Google Calendar, provided by Google Ireland Limited. Encrypted backups of the website database are kept in parallel on the website's own server and in Google Drive, provided by Google Ireland Limited. Each backup is encrypted on the website's server before it is sent to Google Drive, and neither provider holds the key needed to read it — they store the file but have no access to its content. Booking details — name, email address, topic and time — are also received, once the booking is confirmed, by the members of our team who take part in the consultation: in an email with a calendar invitation and as attendees of the Google Calendar event. We do not sell data and do not pass it to third parties for marketing.
How long we keep data
Contact form messages — 24 months from receipt. Analytics events — 14 months. Confirmed consultation bookings — 24 months from the date of the appointment. Cancelled bookings — 12 months from the date of the appointment. The matching Google Calendar entry is deleted together with the booking. If the Google Calendar entry cannot be deleted during a review (for example while the calendar connection is broken), the booking is deleted at the first review in which that succeeds. If a contract follows the consultation, its data is kept outside this website for the period required by accounting and tax law. Unconfirmed bookings — at most two days from when they were made. Attempt counters with IP address hashes, including for analytics events and CSP reports — at most two days. Security event log entries — 12 months. Copies of messages in the hello@ mailbox in the admin panel, when that feature is switched on — 24 months.
Messages, analytics events, confirmed or cancelled bookings, security event log entries and copies of messages in the hello@ mailbox in the admin panel are deleted during a monthly review, so after a period ends they may remain in the website database for up to one more month. These periods apply to the website database. Notification emails about messages and bookings also reach our mailboxes and those of team members, and invitations reach their calendars. We delete these copies manually, at the latest once the periods given above for messages and bookings have passed, and earlier at your request.
Backups. We make an encrypted backup of the website database every day and keep it in parallel on the website's own server and in Google Drive, for about 90 days; older backups are deleted automatically. Data deleted from the database — including at your request — remains in these backups until that period ends. We restore a backup only to bring the website back after a failure or to check that it can be restored; erasures made after the date of the backup are reapplied as part of the same restore procedure, before we consider the restore complete.
Web server access logs. We keep these for up to 15 days.
Erasure register. The pseudonymised hashes and erasure date described above are kept indefinitely — the only way to demonstrate and honour an erasure and to prevent erased data from being accidentally restored.
Your rights
You have the right to access your data, to rectify it, to erase it, to restrict processing, to data portability and to object to processing based on legitimate interest. You also have the right to lodge a complaint with the President of the Personal Data Protection Office (ul. Stawki 2, 00-193 Warsaw, Poland). On request, we will send you a copy of your data as a JSON file.
To exercise these rights, write to the contact address given above. We respond without undue delay and no later than within one month.
Is providing data mandatory
Providing data is voluntary but necessary for us to reply to your message or to book an appointment.
Profiling
We do not make decisions based solely on automated processing, including profiling, that would produce legal effects concerning you or similarly significantly affect you.
Cookies
This site uses no cookies for analytics or marketing. The only thing stored in your browser is your colour theme preference — a technical setting not linked to any person.
This is a translation. In case of any discrepancy, the Polish version is binding.