Skip to content
Status

Cookies

What the site stores in your browser — cookies and local storage — and what each one is for.

Optional chat storage

Only when you choose the AI chat on public pages, the Volga widget uses browser local storage for a visitor identifier and conversation history. It lets you continue your question, including with human support. It does not depend on accepting visit measurement cookies. Closing the widget does not erase this data: you can remove it in your browser settings. Processing details and how to request deletion of messages are in Privacy, under “Optional chat on public pages”.

What we store

All the ones on this list are functional or security cookies: two remember a preference of yours and the rest hold up a purchase, a session or a defence against an attack. There are no advertising or profiling cookies, and Vercel’s visit measurement uses no cookies. The only cookies that are not necessary are Google Analytics’, which exist only if you accepted them and have their own section further down. The other third-party tags that can load are the anti-robot check on the contact page and the view of an Instagram profile you ask for on the link card, each also with its own section.

The names in this list are the cookies, exactly as your browser will show them. The ones protecting something start with “__Host-”: it is a prefix the browser recognises that forces it to send them only to this exact domain and only over HTTPS, so a subdomain cannot plant one on you. The two that only remember a preference do not carry it. What we keep outside a cookie is further down, in its own list.

  • “fl_locale” remembers your language for a year.
  • “fl_currency” remembers for a year which currency you want to see prices in: Argentine pesos or dollars. It only changes how they are shown; the charge is always in Argentine pesos.
  • “__Host-fl_checkout” stores a random identifier to retrieve your cart, which can hold up to twenty products. The cart contents are kept encrypted on our server. The cookie lasts seven days from your last change and cannot be read by page JavaScript. Carts saved before this change may keep their contents in the cookie until you change them or they expire.
  • “__Host-fl_cart_count” holds only how many products your cart has, to show that number on the cart icon. It lasts as long as the draft and is deleted with it. Page JavaScript can read it, because that number is drawn in your browser; it holds nothing else.
  • “__Host-fl_order_return” remembers, for a day, which order you just left to pay, so that coming back from the payment provider takes you to its tracking page. That way the return link carries nothing about your order. Page JavaScript cannot read it.
  • “__Host-fl_csrf” proves a form came from a page on this site and not another one.
  • “__Host-fl_session” identifies your session if you created an account and signed in. It holds an opaque identifier, never your email and never your password.
  • “__Host-fl_oauth” lasts ten minutes and exists only while you go to Google to sign in and come back. Since signing in with Google is optional and is only available if the operator has configured Google credentials, today it never gets written.
  • “__Host-fl_staff” identifies a team member’s session in the internal console. A buyer does not receive it.
  • “__Host-fl_staff_mfa” lasts as long as an internal second-factor challenge does. A buyer does not receive it either.
  • “__Host-fl_staff_search” lasts ten minutes and keeps, in an administrator’s browser, the email they searched the orders for, so that it is not written into the page address. A buyer does not receive it.

What stays in your browser

Besides cookies, the site keeps a few preferences in your browser’s local storage. The difference matters: a cookie travels to our server with every request and has an expiry date; this never travels and never expires — it stays on your device until you clear the site’s data.

We only keep preferences of yours there, and what you typed into a form so you do not have to type it again. Nothing that decides a price, a permission or who you are: the server decides those, and it reads nothing from this list.

  • “fl_motion” was kept by an earlier version of the site when you asked to reduce the background animation. We no longer use it: if it is still in your browser, the site clears it the next time you open it.
  • “fl_consent” remembers whether you accepted or declined measurement with Google Analytics, so you are not asked again. It exists only if you answered the notice.
  • “fl_trial_draft” keeps the link and the email you typed into the free trial request when the day’s quota was already full, so that the next day you only have to send it. It is cleared when you ask for the trial.

The anti-robot check

To keep out spam and abuse of the free trial, the anti-robot check on the contact form and on the free likes trial request is Cloudflare Turnstile, it loads on those two pages alone and only if the operator has configured its keys. It runs inside a frame (iframe) served by Cloudflare from challenges.cloudflare.com: it writes no cookie on this domain, and we neither read nor write any of theirs. Inside that frame, under its own domain and its own terms, Cloudflare may store data to recognise a browser it has already verified.

The view of an Instagram profile

So you can recognise your profile, when our server cannot read the Instagram profile you pasted, the link card offers a button to see it as Instagram shows it, and only if you tap it does your browser load that view from www.instagram.com inside a frame (iframe). It writes no cookie on this domain, and we neither read nor write any of theirs. That view is served by Instagram, not by us: it receives your IP address, details of your browser, the profile you asked to see and our site’s address, without the page you are on, and inside that frame, under its own domain and its own terms, it may use its cookies. We read nothing from that frame, and we pass it neither your email nor anything about your orders.