Cookie Policy
Every cookie the platform sets, what it is for and how long it lasts.
Last updated October 17, 2026
1What a cookie is
A cookie is a small file the site stores in the browser so it can recognise it on the next request. Without them there is no way to keep a session open or to hold a cart between two pages.
This policy describes every cookie Krgo's platform sets, and those set by the measurement services it loads. It is the complete list: it is generated from the same registry the platform's code uses, so a cookie that is not here cannot be set at all.
2Which cookies we use
The lifetime is the one the cookie carries when it is set; for the Google Analytics, Meta pixel and PostHog cookies it is each service's default. “Browser session” means it is deleted when the browser closes. “Server only” means no script on the page can read it.
Besides cookies, the platform keeps the last three word searches made in the browser, never a link, in the browser's storage, to offer them again in the search field. They never leave the device, and they are removed with “Clear” in the search field or by clearing the site's data.
When someone makes a gift card before signing in, the browser keeps what they wrote (the design, the amount, the recipient's name and email, the signature and the message) for up to 24 hours, so it is still there after signing in or confirming the email in another tab. It is removed when the purchase is created or once that time passes, and Krgo stores none of it until the purchase is created. When someone opens the link of a card they received, the browser also keeps its code for up to an hour, so it is still there if they create their account in another tab; it is removed once the card is redeemed or that hour passes.
| Cookie | What it is used for | Lifetime | Access | Type |
|---|---|---|---|---|
| better-auth.session_token · __Secure-better-auth.session_token | Keeps you signed in after you enter your account. | 7 days | Server only | Essential |
| krgo_visitor | Identifies the browser with a random value, so the cart survives a reload, usage limits can be applied and the help centre counts one answer per page when it asks whether the page helped. It says nothing about who the person is. | 365 days | Server only | Essential |
| krgo_ship_to | Remembers the chosen destination province, so the delivery cost can be shown without asking again. | 365 days | Server and browser | Preference |
| krgo_checkout | Remembers the address chosen during a purchase in progress, so a reload does not lose it. | Browser session | Server only | Essential |
| NEXT_LOCALE | Remembers the language the site is preferred in. | Browser session | Server and browser | Preference |
| krgo_utm | Remembers the campaign the visitor arrived from, taken from the link's “utm” parameters, so it is known which campaign brought an order. Krgo writes it. | 30 days | Server only | Advertising |
| krgo_console_rail | Remembers whether the console's menu was left collapsed. It is written only for Krgo's staff. | 365 days | Server and browser | Preference |
| _ga · _ga_* | Set by Google Analytics, which Krgo loads on every page, to tell one browser from another and measure visits and what is done on the site. | 730 days | Server and browser | Measurement |
| _fbp · _fbc | Set by the Meta pixel, which Krgo loads on every page, to measure which visits and which purchases come from the ads on Facebook and Instagram, and to show those ads to people who have already visited the site. | 90 days | Server and browser | Advertising |
| ph_krgo | Set by PostHog, which Krgo loads on every page, to recognise the browser between visits and measure how the site is used: which steps of a purchase are completed and where it is abandoned. It does not record the screen. | 365 days | Server and browser | Measurement |
3Measurement and advertising
To measure how many people use the platform, what they do on it and which campaigns bring purchases, Krgo loads three external services on every page: Google Analytics, the Meta pixel and PostHog. Each sets the cookies the table above lists and receives the pages viewed and the steps of a purchase.
They load for every visitor from the first page, without a consent notice: this policy and the privacy policy are the notice. Anyone who does not want that measurement can block it from their browser, as the section “How to control them” explains.
When an order is paid, Krgo reports the purchase to those three services from its server, with the order's identifier and its amount. For an account holder it also sends Meta the email address and the account's identifier turned into an irreversible code (a hash), the IP address and the browser, so Meta can recognise the purchase even when the browser has blocked its cookie.
PostHog does not record the screen. Vercel, which hosts the platform, also measures page performance without setting cookies.
Pending decision
Whether Law 8968 allows this measurement without asking the consent of someone who visits the platform without creating an account has to be confirmed by the lawyer.
4Third-party cookies
Besides the three measurement services, one other external service may set its cookies when the customer uses it:
- ONVO Pay, whose payment component is loaded inside the purchase page so the card can be charged.
5How to control them
Every browser lets you see, delete and block a site's cookies from its settings.
Blocking the necessary cookies makes it impossible to sign in, to hold a cart and to complete a purchase. Blocking the preference ones only means the platform asks again for the language and the shipping destination.
Blocking the measurement and advertising ones changes nothing about using the platform. Besides the browser, Google offers an add-on to opt out of Google Analytics, and Meta lets you choose which ads are shown from the settings of your Facebook or Instagram account.
6Changes to this policy
Krgo may update this policy. The version in force is the one published on this page, with its last-updated date.