Cookies Cookies

1. First-party cookies

This site sets two first-party cookies. The first, kj_lang, 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 only holds «es» or «en», it lasts a year and it goes to no third party.

It's a technical preference cookie, the kind the law exempts from consent because it answers a choice you made. If you never touch the switcher, it isn't stored: the language you first see the site in is worked out by the server from what your browser already announces on every request.

The second, kj_consent, stores your answer to the consent notice («granted» if you accept, «denied» if you reject) for a year, so we don't ask on every page. It stores the answer, not who you are, and it doesn't leave kujira.so either.

You can delete both from your browser whenever you like, like any other.

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. Meta advertising measurement

If you accept it in the consent notice, we load the Meta pixel, from Meta Platforms Ireland Ltd. It tells us how many visits come from our ads on Facebook and Instagram, and it lets Meta show Kujira ads to people who have already visited the site.

The pixel sets the _fbp cookie on kujira.so, which tells your browser apart from one visit to the next, and the _fbc cookie if you arrive from an ad, which stores that click's identifier. Both last 90 days. If you're logged in to Facebook or Instagram, Meta may also read its own cookies, such as fr, and link the visit to your account.

With every page you open, the pixel sends Meta that page's address, your IP address, your browser details and those identifiers. Kujira and Meta are joint controllers for collecting and transmitting them (CJEU judgment C-40/17, Fashion ID). What Meta does with them afterwards is decided by Meta as controller, under its privacy policy, and may include transferring them to the United States.

If you don't accept, the pixel doesn't load and your browser doesn't contact Meta. It doesn't load either if you browse without JavaScript: the fallback code Meta suggests for that case isn't used on this site, because it would report the visit without asking you.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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 kj_lang and kj_consent cookies, the platform's session cookie and the anti-robot filter's are technical or strictly necessary, and the article itself exempts them.

Meta's cookies are not. That's why they're only turned on if you accept them in the consent notice, which lets you accept or reject with the same effort. The site works the same either way.

The data the pixel sends to Meta is processed on the basis of your consent (article 6.1.a of the GDPR). You can withdraw it at any time, without affecting the lawfulness of the processing carried out before (article 7.3 of the GDPR).

The browsing data our own analytics collects 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.

9. How to withdraw consent, turn them off, and opt out of the count

To change your answer about Meta's cookies, use the Cookie settings button at the top of this page. If you withdraw consent, we delete _fbp and _fbc from kujira.so and the pixel stops loading. The cookies Meta keeps on its own domain, such as fr, are out of our reach: you can delete them from your browser or manage them from the ad settings of your Meta account.

You can block or delete any cookie 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.

10. Changes to this policy

If in the future we add another 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.

11. Contact

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