Privacy

Updated 31 August 2026

What this site does with your data, in plain words. It is short because the site does very little with it, and the little it does is all here.

Who is behind this

This site is mine, Iñaki Marzo, a creator based in Bangkok. I am a private individual, not a company: there is no shop here, no account to open, no passwords to keep. Anything to do with your data comes straight to me, at hola@inakimarzo.com, and I answer it myself.

What this site does not do

No cookies, no third party pixels, no ad networks, no profiling, and nothing that gets sold or handed to anyone. There is no dashboard where I can see who came in, because that data does not exist. (The newsletter email does carry a pixel, and it has its own section further down.)

This page in particular loads nothing from anywhere else

The document you are reading is a plain HTML file with its stylesheet, both served from this same domain. No scripts, no Google fonts, no counter. Opening it tells nobody about your visit, not even me. It is built that way on purpose: a legal page has to stand on its own on the day someone opens it because they want to complain about something.

How I count visits to the home page

The home page does carry a counter, and it is mine: it lives on this domain, at /api/hit. Once per visit it sends the page address, where you came from and the campaign tags on the link. It sets no cookies, writes nothing into your browser and creates no identifier that lasts.

To tell whether two visits are the same person, the server computes a one way hash from your IP and your browser together with a salt that is thrown away and replaced every day. Neither the IP nor the browser is ever stored raw anywhere, and what stays in storage is a mathematical count (a HyperLogLog) that is incapable by construction of saying whether you were there. The next day the salt changes, and the same visitor is already someone else. It tells me how many people read a page, never who.

There is a second note, at /api/visita, which happens once per browser tab: it records the campaign tags on the link and the domain you arrived from (the domain, not the page, and never your email or your IP). It stays in the function logs, and it tells me which link on which network brought people in.

The fonts and the little figure on the home page

The home page loads its typefaces from Google Fonts, so Google sees the request and with it your IP, the same as on any site that uses them. It also loads the Nomms, the figure that moves, from nommeros.com, which is another domain of mine: it serves the drawing and nothing else, sets no cookies and sends me no data about you.

The newsletter, if you sign up

Visiting the site never puts you on any list. That only happens if you type your address into the form: I then send you an email with a link, and until you click it you are not subscribed and nothing else reaches you. It is double confirmation, and if you never click, that address stays half way and receives nothing.

Once you confirm, your address sits in an audience of mine at Resend, which is the provider I send with. Depending on which form you signed up from, the list is either this site's or the Nommeros one, which is another brand of mine with its own account: they are kept apart on purpose and they do not mix. Every email carries an unsubscribe link that works on its own, in one click, with no explanation owed to me.

Those emails also carry an invisible one pixel image, served from links.inakimarzo.com, which tells me whether the email was opened. I use it in aggregate, to know whether a subject line worked so the next one is written better. The links inside the email are not rewritten and not measured: they go straight where they say they go, without passing through any redirector of the provider's. If you would rather not have the open counted at all, tell your mail app not to load images and it stops being recorded. Unsubscribe and nothing is measured any more.

The short links I post around

When I share something on social media I use links in this shape: inakimarzo.com/r/something. Clicking one takes you where it should and counts the click along the way, because it is the only metric that does not depend on a platform deciding to give it to me. The same rule applies as with the visit counter: no IP, no browser, no cookie. Only how many clicks there were per link and per day.

What gets stored in your browser

Four things, and none of them leave your device:

• im:idioma, the language you chose, so that next time it opens in it.
• im:aviso, a note that you already saw the banner offering you the other language, so it is not offered every time.
• visita_logueada, a marker that lasts as long as the browser tab and keeps the same visit from being recorded twice. Closing the tab removes it by itself.
• altas_local, which only exists if you have used the newsletter form: it keeps a copy of what you sent in case the network failed at that exact moment. It is yours, it is in your browser and nobody else reads it.

Clearing this site's data removes all four, and the site keeps working exactly the same.

Keeping the form from being flooded

Every signup that gets accepted costs a real email to whatever address was typed in, so the form has a brake. For that I count attempts per time slot alongside a one way hash of the IP, never the IP itself, and those counts delete themselves after forty days. There is no email address in there and nothing with which to reconstruct who you were.

Where the site is hosted

On Vercel, which serves these files and keeps its technical logs, IP included, in order to deliver the site and protect it from abuse. Those are their logs and they run under their terms: I have no dashboard there that says who comes in.

What you can ask me for

To see what I hold about you, to correct it, to take a copy away, to have it deleted or to tell me to stop using it. An email to hola@inakimarzo.com is enough, and I answer within the month. If you think I have handled it badly, you can go to the data protection authority of the country you live in.

When this changes

If any line here stops being true, this page changes and the date at the top moves. No previous version is kept anywhere: what you read is what the site does today, and the git history is the receipt.