Cookie policy and storage in your browser.

1. What this site uses

This site stores one cookie, and only if you ask for it: it remembers which language you want to read it in. The selector in the menu writes it when you pick Español or English, it holds two letters, and without it the site works exactly the same.

Beyond that, the site sets no other cookie of its own or of a third party, loads no advertising pixels and stores nothing else in your browser, neither in local nor in session storage.

The site loads two third-party components, and both are configured so that they write no cookie and nothing at all on your device: a visitor count, which measures how many people open each page without identifying anyone, and the anti-abuse check on the pages that have a form. What each one does and what data it handles is below and, in more detail, in section 3 of the privacy policy.

There is no consent banner, and that is not an oversight. A cookie that only stores an interface preference you chose by hand is exempt from asking permission, just as technical storage is: asking you to accept what you have just asked for would be noise. What is required is to describe it, and that is what the next section does.

All of this is verifiable with the tools any browser ships with, and the house keeps it current: if the site ever adds anything else that stores information on your device, this page will say so before it happens.

2. The language cookie, with its name and its lifetime

It is the only one the site writes, and this is its full record.

• Name. ohmybitz_idioma
• Owner. First party. This site writes it and nobody else reads it.
• What it holds. Two letters: es or en. Nothing else. It carries no identifier, it does not tell you apart from anyone else and it cannot be used to recognize you from one site to another.
• What for. To remember which language you want to read the site in, so the homepage greets you in the one you chose and not in the one your browser assumes.
• When it is written. Only when you click the language selector in the menu. If you never click it, it is never written.
• Lifetime. One year from the last time you chose.
• Basis. It is a user-interface customization cookie requested by you, one of the kinds exempt from prior consent.

What happens if you do not have it. The homepage shows you the language your browser asks for: Spanish if it asks in Spanish, English in every other case. The selector in the menu is still there and still works; the only difference is that the site will not remember your choice next time.

Deleting it breaks nothing, and the section on how to delete or block cookies explains where.

3. What counts as a cookie

A cookie is a small file a site stores on your device to remember something between one page and the next. The applicable rules do not look at the technology, they look at the act of storing or retrieving information on your device, so local storage, session storage, browser databases and device identifiers all count the same as a cookie.

Of all of them the site uses exactly one, the language cookie described above. It uses no local storage, no session storage, no browser databases and no device identifiers.

4. How the site works with a single cookie

The site is pages that are already written before you arrive. There is nothing to personalize for you, so the only thing the site remembers is which language you asked to read it in, and only if you told it.

The typefaces are served from the site's own domain, so the site asks nothing of an external font service, which is the door a third party comes through on most sites that believe themselves cookie-free.

Everything that happens with a form happens on the server and after you press send: the delivery of the message to the house and, if you ticked the optional box, the sign-up to its mailing list. None of that leaves a trace in your browser, and neither does the automatic notice you get on sending it.

The links to a creator's media kit open a third-party domain. They are links, not embedded content, so that third party receives nothing until you decide to click. From that moment its own policy applies.

5. The verification on the forms

The pages that have a form load an anti-abuse verification from Cloudflare. It is what checks that whoever is about to submit is a person and not a program, and without it the OHMYBITZ mailbox would fill up with automated mail until it stopped being of any use.

It stores no cookies and nothing else on your device. It issues a single-use result that travels with the form and is spent there. It does not identify you, it does not track you across sites and it does not build a profile of you. That is why it is declared here and carries no banner. What creates the obligation to ask for permission in advance is storing or retrieving information on your device, not using a third party's tool.

The technical data that provider processes in order to run the check, and the only thing OHMYBITZ gets back, is in section 3 of the privacy policy.

The configuration matters and that is why it is written down here: the verification has an option that would indeed write a cookie in your browser, and on this site it is turned off. The day it was turned on, this page would say so first.

6. The visitor count

Every page on the site loads a Cloudflare visitor count. It is a counter: when you open a page, your browser tells the provider that the page was viewed, and from those signals the house knows how many visits each page gets, from which country, on what kind of device and from which site they arrive.

It stores no cookies and nothing on your device, neither in local nor in session storage, and it assigns you no identifier: it cannot tell whether today's visit and tomorrow's come from the same person, nor follow you between sites. What travels with each signal is the address of the page you opened, the address of the page you came from if there was one, the type of browser and device, and the loading times. The provider works out the country from the connection, and does not use that connection to identify you or to recognize you on another visit. The house sees aggregate statistics, never a row per visitor. Section 3 of the privacy policy spells it out.

That is why it is declared here and carries no banner: what makes permission mandatory is storing or retrieving information on your device, and this measurement does neither. If you would rather it did not count your visit either, any content blocker prevents it by blocking the domain cloudflareinsights.com, and the site works exactly the same without it.

7. Server logs

Any site, in order to work, leaves an access log on the server that serves it, and it may need a strictly technical cookie for security or for load balancing. Storage of that kind is exempt from the consent requirement, because it is necessary to provide the service you asked for when you opened the page, and it is not used to identify you or to track your browsing across sites.

8. How to delete or block cookies

Even though this site installs none, your browser lets you view, delete and block the cookies of any site, and block third-party cookies entirely. The option lives in the privacy settings of each browser, under a name similar to browsing data, cookies and site data, or tracking protection.

Blocking third-party cookies in your browser is a good general measure and changes nothing about the use of this site.

9. What happens when the site takes on something new

The site is going to grow, and this page is updated before anything that touches your browser arrives. The two things the house wanted when it wrote this page are now in, and they came in on the criterion that follows.

Three things are already in place, on that same criterion, and all three are described above, each in its own block. The visitor count measures without storing anything on your device and without identifying you. Form protection verifies the submission without storing anything in your browser and without following you between sites. And the language cookie stores two letters when you press the selector.

Visitor measurement. The criterion was, and in this order: first a tool that writes nothing on your device and cannot identify you from one visit to the next, even if that means having less data. The one that came in meets both conditions, so it falls under the same exemption as technical storage and there is no need to ask your permission. If one day the house did need one that writes cookies, then yes: this page would go on to describe every cookie with its purpose, its lifetime and its owner, and the site would add a prior consent mechanism, with the option to accept and the option to refuse in the same place and in the same format, running no measurement script before you choose, and with a way to change your mind from any page.

The tools for whoever publishes a site. The ones search engines offer to see which searches lead here install nothing on the site: they read the data the search engine already has from its own crawl. The house uses them and that changes nothing on this page.

Advertising. The house does not send ad traffic to this site and does not measure conversions here, so it installs no advertising-platform pixels. If it ever did, that cookie would not be exempt and would arrive with prior consent, not any other way.