---
title: "Privacy: what data this site processes · MRC Studio"
description: "The privacy notice of the MRC Studio site: what data I process through visits, messages, calls and the tools, for how long and with whom."
url: https://mrcstudio.io/privacy/
lang: en
updated: 2026-11-21
---

# Privacy: what data this site processes

This is the privacy notice of the website of MRC Studio, the SEO, GEO and AI consultancy of Mauro Cattaneo. It tells anyone who visits the site, writes through the contact form, books a call or uses the MRC Labs tools what data I process, for what purpose, for how long and with whom. In short: for visit statistics the site uses no cookies and no scripts in the browser, and it does not keep what you write in the form, in the booking or in the tools.

Updated on 21 November 2026

## Who processes the data

The controller is me, Mauro Cattaneo. MRC Studio is my consultancy; MRC Labs is the brand under which I publish my software.

For any question about this data, and to exercise your rights, write to me at [info@mrcstudio.io](mailto:info@mrcstudio.io).

## Visits to the site

Right now the site does not count visits: statistics are switched off. Nothing about the pages you read is recorded beyond the technical logs Cloudflare keeps to serve them to you, described below under ‘Delivering the pages and protecting the site’. No analytics script reaches your browser and nothing is written to your device.

If you do not want your visits to be counted when statistics are switched on, you have three ways, described on the [Cookies](https://mrcstudio.io/cookies/) page: your browser’s Global Privacy Control signal, the Do Not Track signal, or the ‘Don’t count my visits’ button. The button already works: the cookie it sets remembers your no.

## Delivering the pages and protecting the site

The site and its service are served by Cloudflare. To send you the pages, Cloudflare receives your browser’s requests and keeps technical logs of them.

- **Purpose.** Serving the site and protecting it from abuse.
- **Legal basis.** My legitimate interest in running the site and protecting it from abuse. This also covers the request limit and Turnstile, described below.
- **Data.** Those of any request to a website. Cloudflare lists IP addresses, traffic routing data, system configuration information and other information about traffic to and from the site.
- **Retention.** Cloudflare states that it processes this data for a limited period.
- **Recipients and countries.** Cloudflare, Inc., a United States company, as processor. Cloudflare states that it processes this data in its data centres in the United States and in Europe. For transfers to the United States from the European Economic Area, Switzerland and the United Kingdom, it relies on its certifications under the EU-U.S. Data Privacy Framework, the Swiss-U.S. Data Privacy Framework and the UK Extension; should these certifications lapse, on the standard contractual clauses.

**The request limit.** To stop the contact form, the call booking and the tools from being used automatically, a Cloudflare counter counts requests per IP address in 60-second windows: for an IPv4 address it counts the whole address, for an IPv6 address its first 64 bits. The site’s service asks the counter one thing only: whether the limit has been exceeded. The site’s service does not keep the address and does not write it to its logs. Cloudflare keeps a separate count in each of its locations; its documentation does not say how long it keeps that count after the window.

**Turnstile.** The contact form, the call booking and the tools’ forms are protected by Turnstile, a Cloudflare script that tells a person from a program. It loads only on pages with a form, and only when you start using it. When it loads, your browser connects to Cloudflare, which runs its check and issues a token; the site’s service has Cloudflare verify that token and receives the outcome. The token expires after 5 minutes and can be verified only once.

To run its check, Turnstile processes signals from your browser, including the IP address, the TLS fingerprint, the User-Agent header, the site key and the origin of the page. Cloudflare states that it cannot directly identify a person from these signals. It processes them as processor to protect the site, and as controller, on the basis of its legitimate interest, to improve its bot detection. The rest is in [Cloudflare’s Turnstile privacy notice](https://www.cloudflare.com/turnstile-privacy-policy/).

## The contact form

- **Purpose.** Reading your message and replying to you.
- **Legal basis.** Taking steps at your request before a contract (pre-contractual measures).
- **Data.** What you write in the form: full name, email, address of the site, what you need.
- **How.** The form sends an email to my mailbox, through Cloudflare Email Routing. Nothing you write stays on the site. Cloudflare states that it does not store the emails it forwards and does not access them.
- **Retention.** I keep the messages for 24 months after our last exchange, unless the law requires me to keep them longer.
- **Recipients and countries.** Cloudflare, Inc., which forwards the email, as processor, with the safeguards described above. My mailbox is provided by Google: for users of Google services in the European Economic Area or Switzerland, the provider is Google Ireland Limited, in Ireland. Google states that it has servers around the world and that data may be processed outside the country where you live, including in the United States by Google LLC. The transfer to the United States relies on Google LLC’s participation in the EU-U.S. Data Privacy Framework, the Swiss-U.S. Data Privacy Framework and the UK Extension and, where a transfer is not covered by an adequacy decision, on the standard contractual clauses.

## Booking a call

From the [Contact](https://mrcstudio.io/contact/) page you can book a call with me on Google Meet, at a time when I am free. Booking works only with JavaScript enabled: without it, the page offers the contact form.

- **Purpose.** Showing you the free slots, arranging the call you choose and preparing it.
- **Legal basis.** Taking steps at your request before a contract (pre-contractual measures).
- **Data.** What you enter in the booking form: full name, email and, if you enter them, the address of the site and what you would like to talk about. Then the time you choose.
- **The free slots.** To show them to you, the site’s service asks Google Calendar only at which times I am busy. This request contains none of your data.
- **What goes to Google Calendar.** When you confirm, the site’s service creates the event for the call in Google Calendar, with a fixed title, ‘Call · MRC Studio’, the start and end time and the Google Meet link, and invites you with your email address. Only your email address and the time of the call go into the event, and therefore to Google Calendar: not your name, your site, your message, the page you book from, the language or your IP address.
- **What you receive.** Google sends the invitation to the address you entered, from the account the calendar belongs to. The invitation has the fixed title, the time and the Google Meet link, and no text written by you.
- **What reaches me.** Your name, email, site and message, if you entered them, and the time of the call reach me in an email to my mailbox, which is provided by Google, through Cloudflare Email Routing, like the messages of the contact form. You do not receive this email. The site’s address, [info@mrcstudio.io](mailto:info@mrcstudio.io), is invited to every call as an optional guest, so a copy of Google’s invitation, with your email address and the time of the call, also reaches that address, that is, my mailbox.
- **Retention.** Nothing you write stays on the site. I delete the event from the calendar 24 months after the call. I keep the booking email and the copy of the invitation like the messages of the form: for 24 months after our last exchange, unless the law requires me to keep them longer.
- **Recipients and countries.** Google, as provider of the calendar, of Google Meet and of my mailbox, where the booking email arrives, with the same facts described above for the mailbox: for users of Google services in the European Economic Area or Switzerland the provider is Google Ireland Limited, in Ireland; Google states that data may also be processed in the United States, by Google LLC. The transfer to the United States relies on Google LLC’s participation in the EU-U.S. Data Privacy Framework, the Swiss-U.S. Data Privacy Framework and the UK Extension and, where a transfer is not covered by an adequacy decision, on the standard contractual clauses. Cloudflare, Inc., which forwards the email, as processor, with the safeguards described above.

The request limit and Turnstile, described above, apply here too. Turnstile loads when you choose a slot or select a field of the booking form. The limit also counts the requests for the free slots, which the page makes when the booking appears on screen.

## The MRC Labs tools

The tools analyse a site starting from the address you enter.

- **Purpose.** Running the analysis you ask for and showing you the result.
- **Data.** The address of the site to analyse, which is data about that site and not about you. For Entity Check, also the brand name, if you enter it.
- **Retention.** None. The address is used only for the analysis, the result is not saved and the service’s logs do not record what you enter.
- **Where the address goes.** The requests to the analysed site do not start from your browser: the site’s service makes them, so that site sees the service and not you. Before each request, the host name goes to Cloudflare’s DNS over HTTPS resolver (`cloudflare-dns.com`), which resolves it. Entity Check also sends the public Wikidata API what it needs to look up the brand’s item: the address of the analysed site and the brand name, the one you enter or, if you leave it empty, the one read on the home page; if the home page already links to a Wikidata item, that item’s identifier. Wikidata is run by the Wikimedia Foundation, Inc., in the United States. The request starts from the site’s service, without your IP address, and nothing else goes to Wikidata. The transfer to the United States is necessary to carry out the analysis you ask for. The site’s service keeps neither the address nor the name.

The request limit and Turnstile, described above, apply here too.

## Cookies

The site sets no cookies, with a single exception: `mrc_optout`, which exists only if you click ‘Don’t count my visits’ and serves to remember your no for 13 months. The reason and the button are on the [Cookies](https://mrcstudio.io/cookies/) page.

## Your rights

These rights come from the Swiss Federal Act on Data Protection (FADP), for people in the European Union from the European regulation (GDPR), and for people in the United Kingdom from the UK GDPR.

- **Under the GDPR** you can ask me for access to your data, rectification, erasure, restriction of processing and portability, and you can object to processing.
- **Under the FADP** you can ask me what data about you I process, to correct it or erase it, and to hand it over to you or transmit it to others.
- **Under the UK GDPR**, if you are in the United Kingdom: it is the European regulation in the form in which it is part of UK law, and, together with the Data Protection Act 2018, it also applies to a controller outside the United Kingdom that offers services to people there.

To exercise them, write to me at [info@mrcstudio.io](mailto:info@mrcstudio.io): I’ll reply personally.

Two things to know. For visits, I have no identifier with which to find yours: to object, the simplest way is the button on the [Cookies](https://mrcstudio.io/cookies/) page. For messages sent through the form and for bookings, I have what you wrote to me, and for a call also the event in the calendar: if you want me to delete them, just tell me.

## Supervisory authority

If you think I am processing your data improperly, write to me at [info@mrcstudio.io](mailto:info@mrcstudio.io). You can also contact the data protection authority: in Switzerland the Federal Data Protection and Information Commissioner (FDPIC), in the United Kingdom the Information Commission (ICO, ico.org.uk), in Italy the Garante per la protezione dei dati personali, in France the CNIL, and in the other countries of the European Union the authority of the country where you live.

## Updates

When a processing activity changes, I update this page and its date. For the technical details, with checks you can repeat yourself, read [How this site is built](https://mrcstudio.io/how-this-site-is-built/); for who publishes the site, the [Legal notice](https://mrcstudio.io/legal-notice/).
