This page forms part of the Bookedtify legal terms. It is written for transparency and should be read together with the other Bookedtify policies that apply to your use of the platform.
1. What Are Cookies?
Cookies are small text files stored on your device when you visit a website or use an online service. Similar technologies include local storage, session storage, scripts, SDKs, and device identifiers.
In this Policy, we use the word “cookies” to refer to cookies and similar technologies used by Bookedtify.
2. Why Bookedtify Uses Cookies
Bookedtify uses cookies and similar technologies to keep users logged in, protect accounts, remember consent choices, support device and session security, operate booking and provider tools, support maps and location features, and enable payment or security workflows.
Bookedtify’s current codebase does not include Google Analytics, Meta Pixel, TikTok Pixel, Plausible, PostHog, or Sentry tracking scripts. If these tools are added later, this Policy should be updated before they are enabled.
3. Strictly Necessary Cookies
Strictly necessary cookies are required for Bookedtify to work properly. These cookies cannot usually be disabled through the Bookedtify cookie banner because the platform needs them for authentication, security, and core account features.
- session: an HTTP-only authentication cookie used to keep you logged in and validate account access. It is set on login, uses SameSite=Lax, is Secure in production, and lasts 1 day by default or 365 days if “remember me” is selected.
- device_id: an HTTP-only device identifier used for known-device recognition, security events, and session/device protection. It uses SameSite=Lax, is Secure in production, and lasts up to 365 days.
The session cookie is cleared on logout, account deletion confirmation, invalid session checks, and logout-all flows. The device_id cookie may remain so Bookedtify can recognise the device for account-security purposes.
4. Local Storage and Session Storage
Bookedtify also uses browser storage for interface preferences and temporary state. These are not HTTP cookies, but they store information in your browser.
- bookedtify_cookie_consent_v1: localStorage entry that stores your cookie consent choice, including necessary=true, analytics preference, marketing preference, and the date the choice was saved. It remains until you clear browser storage or Bookedtify changes the consent storage version.
- bookedtify.navbarUser: localStorage entry used to cache basic navbar account display information, such as name and role, so the UI can update smoothly. It is removed on logout from relevant UI flows.
- bookedtify.explore.mapState.v1: sessionStorage entry used by Explore map views to remember temporary map center and zoom during the current browser session.
5. Functional Cookies and Preferences
Functional storage helps Bookedtify remember choices that improve the user experience, such as cookie consent state, navbar account display state, and temporary map state.
At the moment, Bookedtify does not appear to store separate language, accessibility, calendar-view, or saved-filter cookies in the codebase. If those features are introduced later, this Policy should be updated.
6. Analytics Cookies
The cookie banner lets users choose whether analytics cookies may be used, but the current codebase does not include an active analytics provider such as Google Analytics, Plausible, PostHog, or similar tools.
If analytics tools are added later, Bookedtify should use the stored consent choice before loading optional analytics scripts where consent is required by law.
7. Marketing and Advertising Cookies
The cookie banner lets users choose whether marketing cookies may be used, but the current codebase does not include active advertising pixels such as Meta Pixel, Google Ads, or TikTok Pixel.
If marketing or advertising tools are added later, Bookedtify should use the stored consent choice before loading optional marketing scripts where consent is required by law.
8. Payment and Fraud Prevention Technologies
Bookedtify uses Stripe for payment-related features such as booking checkout, provider payouts, subscriptions, billing portal sessions, invoices, refunds, disputes, and Stripe Tax-related workflows.
Stripe may use cookies, scripts, device signals, or other technologies for payment security, fraud prevention, Strong Customer Authentication, checkout sessions, billing portal sessions, connected-account onboarding, subscriptions, and compliance. Some Stripe technologies may be strictly necessary for payment functionality.
9. Security Challenge Technologies
Bookedtify uses Cloudflare Turnstile on flows such as login, signup, password reset, email-change, restore, and guest booking forms. Turnstile helps prevent automated abuse, spam, and fraudulent submissions.
Cloudflare Turnstile may process device, browser, interaction, and challenge data according to Cloudflare’s own privacy and security terms. These technologies are used for platform security and fraud prevention.
10. Map, Location, and Address Technologies
Bookedtify uses Mapbox for Explore maps, provider location previews, map interactions, and geocoding/address-related features.
Mapbox may process map interactions, approximate location, entered address or place search terms, coordinates, browser/device information, and related technical data according to Mapbox’s own terms and privacy policy.
Some location features require user action or browser permission before precise geolocation is used.
11. Third-Party Providers
Some technologies may be placed or operated by third-party providers that help us run Bookedtify.
- Stripe: payment processing, billing, subscriptions, provider onboarding, refunds, disputes, tax and invoice workflows, and fraud prevention.
- Cloudflare Turnstile: anti-abuse and bot-prevention challenges.
- Mapbox: maps, geocoding, map rendering, map controls, and location features.
- Hosting, email, database, and infrastructure providers may process technical logs or operational data needed to deliver the service, even if they do not set visible browser cookies through Bookedtify pages.
Third-party providers may process data according to their own privacy and cookie policies. Bookedtify does not control every cookie or technology used by third parties, but we aim to use established operational providers and provide choices where required.
12. Cookie Consent
When required by law, Bookedtify asks for your consent before using optional cookies, such as analytics, marketing, advertising, or certain third-party cookies.
The current Bookedtify cookie banner allows you to accept all, reject optional cookies, or manage analytics and marketing choices. Necessary cookies remain active because they are required for platform functionality.
Your choice is stored in localStorage as bookedtify_cookie_consent_v1. Clearing browser storage will remove this choice and may cause the banner to appear again.
13. How to Manage Cookie Preferences
You can manage cookies through the Bookedtify cookie banner when it appears, through your browser settings, and through your device settings.
Most browsers allow you to view, delete, block, or clear cookies and site data. If you block all cookies, some Bookedtify features may not work properly, including login, bookings, payments, provider dashboard, account security, and map features.
If a persistent Cookie Settings control is not visible in your version of Bookedtify, you can change your choice by clearing Bookedtify site data in your browser and revisiting the site, or by contacting Bookedtify for help.
14. Do Not Track and Browser Signals
Some browsers or devices may send “Do Not Track” or similar signals. Bookedtify may not respond to all such signals unless legally required or technically supported.
Where legally required or where supported by our consent tools, Bookedtify may respect recognised consent preference signals.
15. Changes to This Cookie Policy
Bookedtify may update this Cookie Policy when we add or remove cookies, change analytics or marketing tools, add payment or map providers, update the consent system, or respond to legal requirements.
If we make material changes, we may notify users through the app, website, cookie banner, email, or another appropriate method.