Legal information
Cookie policy
This policy describes the cookies, browser storage and analytics used by the PartyBookIt application and landing page.
This English version is provided for information only. If it differs from the Spanish version, the Spanish version prevails.
Necessary cookies and storage
We do not use advertising, profiling or analytics cookies. The application and landing page may use the following cookies or equivalent mechanisms because they are necessary to work:
- partybooking-admin-tenant: remembers the business selected by an authorised administrator.
- Supabase session: maintains authentication and protects access to areas that require sign-in.
- Onboarding verification challenge: securely completes the verification steps required during signup.
- partybookit-locale: the landing page keeps the chosen language for one year in a first-party cookie and, for limited functional compatibility, in localStorage.
- partybookit-portal-locale: remembers for one year the language you choose on a business's booking portal.
Analytics
The application uses Vercel Analytics and Vercel Speed Insights, which do not use cookies, for aggregated usage and performance metrics, discarding routes containing private links or credentials (/booking/*, /invitacion/*, password-recovery routes and /payment/return) and removing query strings and fragments from all other URLs. We use PostHog Cloud EU only with your consent. On the landing page it runs in always-cookieless mode: the SDK writes no cookies, localStorage or sessionStorage, and PostHog computes a rotating daily hash on its EU servers from request-header metadata such as the IP address and user agent; contact-email clicks are not measured. In the application, the SDK writes no cookies but stores in localStorage and sessionStorage, under keys starting with ph_, a random pseudonymous identifier, session identifiers and, if you are signed in to the panel or signup, your internal user identifier and your business's; if localStorage is unavailable, it keeps them in memory only. This storage is deleted when you withdraw consent. Which events and properties are sent, and which never are, is explained under “Service analytics” in the privacy policy.
Consent and withdrawal
The legal basis for PostHog analytics on the landing page and in the application is consent under Article 6(1)(a) GDPR. Without an affirmative choice, the SDK is not imported or initialized and no events are sent. Acceptance or rejection is stored for 180 days in localStorage under partybookit-analytics-consent as an object containing only version, choice and expiresAt; the landing page and the application are separate sites and each asks for and stores its own choice. The choice is requested again when it expires or the version changes. Rejecting is as easy as accepting, and you can review or withdraw the decision at any time through “Analytics settings” in the landing footer, the footer of the application's public pages or the panel's side menu. Withdrawal prevents subsequent events and deletes PostHog storage from the browser, without affecting the lawfulness of earlier processing.
How to manage storage
Use “Analytics settings” to change the analytics decision, and configure your browser to block or delete cookies and local storage. The functional language preferences partybookit-locale and partybookit-portal-locale are separate from analytics consent. If you block strictly necessary technologies, features such as sign-in, administrator business selection, signup verification or remembering the language may not work correctly.