1. What they are
Cookies are small files that a site stores in your browser. Alongside them there are localStorage and sessionStorage, which do the same job with a different technology and are subject to the same rules. On this page we deal with all three together.
Not all of them are there to track people. Some are the only way for the site to remember that you have already signed in between one page and the next.
2. On this site
| Name | What it does | Duration |
|---|---|---|
buskara-session | Keeps the session of whoever signs in to the panel. Without it, every click would ask for the password again. | Session |
XSRF-TOKEN | Stops another site from submitting forms on your behalf. It is a security measure. | Session |
bk_consent | Stores the answer you gave to the consent request: whether you accepted or refused statistics. | 180 days |
The first two are strictly necessary, and therefore do not depend on consent under article 5 of Portuguese Law no. 41/2004. Nor does bk_consent: it is the one that stores the consent, and without it we would go back to asking on every page.
We do not use advertising or social network cookies on this site. The statistics are the ones in point 3, and only with your yes. The fonts are served by Bunny Fonts, which does not record the IP address of whoever requests them: that is why we chose it over another.
3. Statistics, only with your yes
With your authorisation, given in the request that appears on your first visit, this site uses two statistics tools:
Google Analytics 4, loaded through Google Tag Manager, so that we know which pages are viewed and what paths people take to registration and to contact;
Microsoft Clarity, so that we can understand, in aggregate form, how the pages are used.
Until you accept, neither of the two writes cookies: Google Tag Manager starts in denied mode (Consent Mode v2) and Clarity is not even loaded. If you accept, the following may be written:
| Name | Whose it is | What it does | Duration |
|---|---|---|---|
_ga | Google Analytics | Distinguishes visitors with a random identifier. | 2 years |
_ga_* | Google Analytics | Keeps the state of the measurement session. | 2 years |
_clck | Microsoft Clarity | Random visitor identifier. | 12 months |
_clsk | Microsoft Clarity | Links the pages viewed within the same visit. | 1 day |
You can change your answer at any time in "Manage cookies", in the footer of any page. Withdrawing your yes makes the tools stop writing; the cookies already written expire on their own or can be deleted in the browser.
4. In the search layer installed in customer shops
When you visit a shop that uses Buskara, the search layer may store the following in your browser:
| Name | Where | What it does | Duration |
|---|---|---|---|
buskara:sid | sessionStorage | Random identifier for the search session, to link the searches and clicks of the same visit. | Until you close the tab |
bk_sid | First-party cookie | The same identifier, so the shop can link an order to the search that led to it. | 30 days |
buskara:recent | localStorage | The most recent searches made in this shop, shown when the box is opened. They never leave your browser. | Until you clear your browser |
None of these contains a name, an email address or any other data that identifies you directly: they are random character strings.
The bk_sid respects the shop's consent configuration. If the shop has consent on, nothing is written before you give it.
5. How to refuse or delete
The statistics on this site can be refused in the consent request itself, or later in "Manage cookies", in the footer. For everything else, you can block or delete cookies in your browser settings; each browser's documentation explains where. You can also browse in private mode, where everything is deleted when you close the window.
Blocking the necessary cookies prevents you from signing in to the panel. Blocking the search layer ones does not stop the search from working: you lose the list of recent searches and the link between the search and the order.
6. Changes
Whenever we start using a new cookie, it appears in the table on this page before it is used. The date of the last update is at the top.