Cookies Cookies

1. What we do with cookies

This site installs a single cookie, and only if you ask for it: when you pick a language in the switcher we store which one, so we don't ask again and so the documentation (docs.kujira.so) greets you in the same one. It is called kj_lang, it only holds «es» or «en», it lasts a year and it is ours: it goes to no third party.

It cannot recognise you and it measures nothing. It is a technical preference cookie, the kind the law exempts from consent precisely because it answers a choice you made — which is why you will not see a banner asking for it. If you never touch the switcher, nothing is stored in your browser: the language you first see the site in is worked out by the server from what your browser already announces on every request, leaving nothing on your device. You can delete it from your browser whenever you like, like any other.

We also don't load third-party pixels or share information with third parties while you browse the site.

2. How we count visits

To count visits we use Umami, an analytics platform running on our own infrastructure. The data never leaves our domain and isn't processed by any third party.

For each visit we log the page, the referrer, the country, the browser language, the device and the screen size. Your IP address isn't stored: it's only used at the moment to work out the country and to compute a fingerprint that tells one visit apart from another. That fingerprint is renewed daily, so it doesn't let us recognize you the next day.

3. Cookies on the platform

If you use app.kujira.so, the dashboard where you manage your agents, you do need a cookie: a first-party session cookie that identifies you for as long as your connection lasts. It's strictly necessary — without it we couldn't provide the service.

4. Error diagnostics

The dashboard uses Sentry to alert us when something breaks. It doesn't set cookies or track your browsing, but when an error occurs it sends that provider the technical data needed to locate it: the IP address, the page where it happened and the software version. We include it here because, although it isn't a cookie, it does involve a third party. It's listed as a processor in the privacy policy.

5. The Enterprise calendar

On the Enterprise page you can book a meeting through a calendar provided by cal.com, another company. That calendar doesn't load when you open the page: you have to request it by clicking a button, and until then no one is contacted.

If you do request it, cal.com may set its own cookies to make the booking work, and whatever you enter into it is received by that company. It's the same rule we apply to anything external: nothing from a third party loads unless you ask for it.

6. The "I'm not a robot" check

The contact form carries a Cloudflare Turnstile challenge so robots can't use it as a spam mailbox. When it renders, Cloudflare may set its own cookie and looks at browser signals to decide whether you're human; it doesn't track your browsing around the site or serve ads.

It's one of the strictly necessary ones: without that filter the form would turn into a spam relay and couldn't be offered at all. It's the same challenge that already protects sign-up and "forgot my password" on the dashboard.

7. Legal basis and consent

Article 22.2 of Spain's LSSI-CE (Law 34/2002, on Information Society Services and Electronic Commerce) requires your consent to store information on your device or to access information already stored there, and it exempts from that duty whatever is strictly necessary to provide the service you've requested. The obligation isn't limited to cookies: it covers any browser storage mechanism.

This site's analytics doesn't store anything on your device, so it falls outside that article. The cookies that do exist — the platform's session cookie and the anti-robot filter's — are among the strictly necessary ones the article itself exempts. That's why you won't see a consent banner: there's no non-essential cookie to apply it to.

The browsing data we do collect is processed under the legitimate interest set out in article 6.1.f of the GDPR, which is knowing which pages are read in order to improve the site. You have the right to object, and the next section explains how to make that effective.

What the law does require is informing you of the existence and purpose of the cookies we use, which is what this page is for.

8. How to turn them off, and how to opt out of the count

You can block or delete cookies from your browser settings. If you delete or block app.kujira.so's session cookie, you won't be able to stay logged in to the platform.

There are two ways to be excluded from the visit count. If your browser sends the Do Not Track signal, you don't need to do anything: we honor it and no measurement is sent at all. If you'd rather opt out of just this site, save the key umami.disabled with the value 1 in kujira.so's local storage, using your browser's developer tools; as long as it's there, the script sends nothing.

9. Changes to this policy

If in the future we add a non-essential cookie, or any other system that stores information on your device without being strictly necessary, we'll ask for your consent before turning it on and update this page to reflect it.

10. Contact

If you have questions about this policy, email us at soporte@kujira.so.