Cookie policy
How ClickNBook uses cookies, browser and device storage, and how you can control them.
Last updated
2. Sign-in and payment storage
ClickNBook uses authentication cookies to keep you signed in and protect account access. Session storage under "paid-booking-attempt" holds a booking fingerprint and retry key for the current tab so a payment request can resume safely. The fingerprint includes the booking details, including the customer email and any supplied name. Blocking sign-in or payment storage may prevent those functions from working.
3. Interface preferences
Local storage under "sidebar" remembers whether the sidebar is open until you clear it. Clearing this preference resets the sidebar view and does not prevent sign-in or booking.
4. Payment services
Stripe may use cookies and similar technologies to operate checkout, authenticate payments and prevent fraud. See Stripe's privacy information for its payment technologies.
5. Analytics and advertising
ClickNBook records booking and operational signals on its backend. When configured, PostHog receives selected events with salted identifiers for measuring booking conversion and provider setup. Optional browser and mobile usage analytics start only after you allow the Usage analytics category. They measure page or screen visits and selected checkout interactions. The separate Session recordings selection enables masked session replay on public discovery screens to help investigate navigation problems. Account, authentication and checkout screens are excluded from recordings. We do not enable advertising tracking or automatic capture of form contents. Analytics preferences lets you allow or deny each optional category independently, or withdraw your choices. JavaScript analytics identifiers stay in memory rather than persistent analytics cookies. Native session replay can store SDK identifiers and buffered recordings on the device while preparing delivery.
Storage under "clicknbook-analytics-consent-v4" saves your choice and the time it was made in browser local storage or mobile device storage. We ask again after 180 days. You can change the choice or clear the storage sooner. Each browser and the mobile app have their own choice; allowing analytics in the app does not enable it in browser checkout. The web PostHog SDK also saves its consent status under "__ph_opt_in_out_<project key>" in local storage until it is changed or cleared. This records a choice, rather than an analytics identifier.
6. Your choices
You can decline optional analytics and still use accounts and bookings. Use Analytics preferences to change your choice or withdraw it at any time. Withdrawal stops new optional client collection and discards web events still waiting to be sent. Native events and recordings already collected with consent may remain queued for delivery. Withdrawal does not delete previously collected events or stop selected backend operational events. Contact support about deletion of information already collected.
You can clear cookies and local storage or change browser settings. This may sign you out or remove saved preferences. You can use your browser's help menu to manage site storage. Disabling optional storage should not be required to use the service; storage needed for sign-in and checkout may affect those functions if blocked. Clearing the saved analytics choice means we ask again before starting optional analytics. On mobile, you can clear app storage through your device settings.
7. Policy updates
We update this policy when the storage used by the service changes. The date above shows the latest revision. Where consent is required for new optional tracking, we will ask before using it.
8. Contact
For platform support, privacy requests or billing questions, email support@clicknbook.app. Include your booking reference where relevant. Never send card details or verification codes.