Política de cookies de SlotFlo

Cómo SlotFlo utiliza cookies, almacenamiento del navegador, consentimiento y controles de seguimiento opcional.

Última actualización 28 April 2026

Versión 1.0

Esta versión se proporciona para comodidad. La versión inglesa es la versión legal de referencia, salvo que la ley obligatoria disponga lo contrario.

Controller and scope

KRASYLNYKOV OLEKSANDR, trading as SlotFlo, Autónomo, Spain. Address: Carrer del Vallespir, 169, 3-3, 08014 Barcelona, Spain. Privacy contact: privacy@slotflo.com.

This Cookie Policy covers the SlotFlo website, owner or admin app, public booking pages, embedded chat pages, authentication flows and Stripe checkout redirection surfaces.

English is the reference legal version. If a translated copy differs, the English version prevails unless mandatory law requires otherwise.

Cookie categories

Strictly necessary cookies and storage are always active because they are required for security, authentication, booking, checkout, consent storage and abuse prevention.
Preference cookies and storage remember choices you request, such as language, admin theme or optional Google sign-in state.
Analytics cookies are used only when you consent to analytics.
Marketing cookies are used only when you consent to marketing and a marketing pixel is configured.

Strictly necessary cookies and storage

Supabase auth or session cookies keep authenticated owner, staff and admin sessions working.
Supabase PKCE or code verifier storage supports secure OAuth and email sign-in flows.
`easystart_auth_flow` protects the short-lived authentication flow context.
`slotflo_cookie_consent` stores your cookie choices for 12 months.
reCAPTCHA may be used on public booking submission for security, fraud and abuse prevention when configured.
Stripe Checkout may set cookies on Stripe-hosted pages during payment or subscription checkout.

Preference cookies and browser storage

`slotflo_locale_preference` remembers your selected language.
`slotflo_admin_theme_preference` remembers the admin theme.
Legacy locale cookies may be read only to clean up or migrate older browser preferences.
`g_state` may be set by Google Identity Services if you explicitly use a Google sign-in button. Google sign-in is optional and booking can be completed without it.

Analytics and marketing

Analytics and marketing are off by default.

GA4 cookies such as `_ga` and `_ga_<container-id>` are permitted only after analytics consent.

Meta Pixel cookies such as `_fbp` and `_fbc` are permitted only after marketing consent and when Meta Pixel is configured.

SlotFlo does not use Google Tag Manager for the MVP.

Consent and withdrawal

SlotFlo stores consent in a first-party cookie named `slotflo_cookie_consent` for 12 months.

Optional analytics and marketing consent is off by default. The first consent layer offers Accept all, Reject non-essential and Configure with equal prominence.

You can reopen Cookie Settings from the footer or legal pages to update or withdraw consent. Withdrawal blocks future optional tags.

Server-side consent audit logging is optional. If implemented, it must not store full IP addresses, secrets or tokens.

Google Consent Mode, reCAPTCHA and Google sign-in

SlotFlo applies a deny-first Google Consent Mode v2 foundation for optional tracking: analytics storage, ad storage, ad user data and ad personalization are denied until the relevant category is granted.

reCAPTCHA is used only as a necessary security control for public booking submission where configured, not for analytics or marketing.

Google sign-in on public booking pages is optional. There is no automatic Google autofill flow; Google Identity Services may load only after you choose the Google sign-in action where technically feasible.

AI widget storage and embeds

The embedded AI chat may store a local visitor identifier and recent chat history in browser storage to keep the chat usable. This storage is functional and is not used for analytics or marketing.

AI widget local visitor or history TTL is up to 2 months.

Embedded chat does not load GA4, Meta Pixel or GTM by default.

Browser controls and international processing

You can also control cookies through your browser settings. Blocking necessary cookies may prevent authentication, booking, checkout or security checks from working.

Some providers used for necessary or optional services may process data internationally. Optional analytics and marketing remain off unless the relevant consent category is granted.

Contact

Questions about cookies can be sent to privacy@slotflo.com.