Cookie Policy

Last updated August 9, 2026.

This policy identifies the cookies and browser storage used by the public site, booking flow, and client portal, including which technologies are optional.

What these technologies are

A cookie is a small file a website asks a browser to retain. Local storage is a browser feature that keeps data on the device without sending it automatically with every request. Similar technologies can support security, preferences, authentication, and measurement.

Strictly necessary cookies and storage

These technologies are required to provide a feature you request or to protect the site. They are not used for cross-site advertising:

The pulso_consent cookie stores the optional-cookie decision and schema version for up to 180 days.
WordPress security and authentication cookies protect forms, administrators, and signed-in client portal sessions. A client trusted-device session can last up to 30 days unless the client signs out or access is revoked.
Short-lived security values support form integrity, payment return verification, integration authorization, rate limiting, and single-use portal authentication. A magic link expires after 30 minutes. After it authenticates a browser, reopening it in that same signed-in browser can return the client to its intended portal screen without authenticating again.
The booking flow uses local storage under the key pulsoBookingDraftV2 to restore non-file answers and progress after a refresh. It is cleared after successful completion or when the saved draft expires after 14 days. A visitor can also clear it through browser site-data controls. Files are never stored there.

Blocking or deleting necessary cookies can prevent forms, booking recovery, payment verification, or portal access from working. Stripe and other providers may place strictly necessary cookies on their own pages under their policies when you use those services.

Optional categories

Optional technologies remain off until you choose them. The preference panel provides:

Analytics, to understand aggregate page performance and where visitors encounter difficulty.
Marketing, to measure whether an advertisement or referral led to an enquiry.

Google Tag Manager loads the Pulso Labs measurement configuration, and Google Analytics 4 measures consented page views and product events such as booking progress, completed reservations, portal navigation, reviews, requests, files, and payment-method selection. Pulso Labs does not send names, email addresses, client messages, filenames, secure tokens, or internal record identifiers to these services. Analytics storage remains denied until Analytics is accepted. Marketing storage remains denied until Marketing is accepted. When Analytics is accepted, Google Analytics may use first-party cookies such as _ga and a stream-specific _ga cookie to distinguish browsers and maintain session state. Their configured lifetime can be up to two years. Google Tag Manager manages tags but does not create an advertising profile by itself. Google processes analytics data under its own terms and privacy documentation.

Manage your choice

Use the Cookie preferences link in the footer to accept, reject, or customize optional categories. Accept and reject controls are presented with equal prominence. You can also delete site data in your browser, but doing so may sign you out, remove an unfinished booking draft, and reset the consent choice.

When a browser sends a recognized Global Privacy Control signal, the site keeps optional categories off. Browser privacy settings and extensions can also block technologies independently of this site.

Changes and contact

We will update this policy before materially changing the optional technologies used. A material change can also require a new consent choice.

Questions about cookies or local storage may be sent to yoan@pulsolabs.io.