Cookie Policy

This Cookie Policy explains how Focuslyne ("we", "us", or "our") uses cookies and similar technologies when you visit or use the Focuslyne website, the authenticated web application, public booking pages, and related online services where such technologies are employed.

For how we process personal data more broadly, see our Privacy Policy. For contractual terms, see our Terms of Service.

Questions about this policy or our privacy practices may be sent to info@focuslyne.com.

Cookies are small text files placed on your device when you visit a site. They are widely used to make websites work, to keep you signed in, or to remember choices you have made.

We also refer to similar technologies, which may include:

• Local storage and session storage in your browser, which can store data for a page or session;
• Pixels, tags, or SDKs used by us or by partners for security, performance, or analytics where configured;
• other technologies that achieve comparable purposes as they evolve.

Not every technology listed above is in use in every part of the product at all times. What applies depends on the page you use, your account status, and how the service is configured.

Depending on context, we may use these technologies for purposes such as:

• Authentication and session management — for example to keep you signed in securely across requests;
• Security and fraud prevention — for example to protect accounts, detect abuse, and support rate limiting where implemented;
• Basic preferences — for example theme or interface preferences where the product stores them in the browser;
• Operating forms and booking flows — for example to submit availability checks, complete bookings, or support multi-step flows;
• Measuring product and site performance — where analytics are configured, to understand usage, performance, and reliability at an aggregate level;
• Debugging, reliability, and abuse prevention — including error reporting where enabled;
• Integrations and payment flows — where third-party providers (for example payment, calendar, messaging, or identity providers) use their own cookies or similar technologies during redirects, hosted pages, or embedded experiences.

Some technologies are strictly necessary for the service to function safely and as you expect. Typical examples include technologies needed for login and session continuity, security controls, routing, completing a booking flow, handling payment redirects, and core platform operations.

If you block or delete strictly necessary technologies, parts of Focuslyne may not work correctly — for example you may be unable to sign in, stay signed in, or complete a booking or payment flow.

Where the law treats certain “strictly necessary” technologies differently from optional ones, we aim to use non-essential technologies only where permitted and appropriately controlled.

We may use technologies to remember choices that improve your experience — for example display preferences such as light or dark theme where the app supports it, or UI state that avoids asking you the same question repeatedly.

These may not always be strictly necessary for every feature. Depending on your jurisdiction and how the product is configured, some preference or functional technologies may require consent or offer other controls. Focuslyne does not currently provide a dedicated cookie preference centre. We do not intentionally use non-essential advertising cookies as part of the core Focuslyne website or app. If we enable non-essential analytics, marketing, or similar technologies that require consent under applicable law, we will provide appropriate choices before using them.

Where configured, we may use analytics or performance tooling to understand how Focuslyne is used, how pages perform, whether errors occur, and how we can improve reliability. This is typically done with privacy-conscious configuration and without using these tools to read sensitive free-text fields from booking forms for analytics purposes.

The codebase supports optional error and performance monitoring (for example via Sentry) when a monitoring endpoint is configured for your environment. Whether and where it runs depends on deployment settings; it is not a guarantee that monitoring is active for every user or every page.

Product analytics may also be collected through server-supported event endpoints where enabled, subject to project rules on what may be stored.

Non-essential analytics technologies may require consent under applicable law and your configuration. We do not rely on this policy alone as a consent mechanism. Focuslyne does not currently provide a dedicated cookie preference centre. If we enable non-essential analytics or similar technologies that require consent, we will provide appropriate choices before using them.

When you use features that involve third parties — such as Stripe for subscriptions or optional booking payments, Google or Microsoft for calendars, Zoom for meetings, Meta / WhatsApp for WhatsApp Business messaging where connected, or email delivery providers — those providers may set or read their own cookies or use similar technologies on their domains or during hosted flows.

This happens for example during OAuth or authorization redirects, hosted checkout or billing pages, embedded widgets, or other flows where you interact directly with the provider's infrastructure.

Third-party providers process information under their own policies. We do not control their cookies end-to-end. You should read their privacy and cookie notices for detail.

Public booking pages (typically reached via a professional's link or embed) use technologies needed to show availability, submit forms securely, apply anti-abuse or rate-limiting measures where implemented, complete optional online payments via redirects to a payment provider when that flow is enabled, and show confirmation or error states.

We do not intend public booking pages to load non-essential marketing or advertising pixels as part of the core Focuslyne experience. If that posture changes, this policy and our technical configuration will be updated accordingly.

The table below summarizes categories of technologies that may appear in connection with Focuslyne. It is not an exhaustive technical inventory. Exact names, domains, and durations may vary by environment, browser, provider, and product configuration.

Where applicable law requires consent before using non-essential cookies or similar technologies, Focuslyne should request that consent in a clear way before those technologies are used. This policy does not by itself constitute such consent.

Focuslyne does not currently provide a dedicated cookie preference centre. We do not intentionally use non-essential advertising cookies as part of the core Focuslyne website or app. If we enable non-essential analytics, marketing, or similar technologies that require consent under applicable law, we will provide appropriate choices before using them.

You can also control many cookies through your browser settings. Blocking cookies may affect sign-in, bookings, payments, or integrations.

Most browsers let you see what cookies you have, delete them individually or in bulk, and block cookies from specific sites or from third parties. They also differ in how they treat local storage and similar features.

Because settings vary by browser and version, use your browser's help documentation for the current steps. If you clear storage for Focuslyne, you may need to sign in again and may lose unsaved on-page state.

We may update this Cookie Policy from time to time — for example when we add features, change providers, or respond to legal or regulatory guidance. The “Last updated” date at the top of this page will be revised when we publish substantive changes.

For material changes, we may also provide notice through the website, the app, or email where appropriate and permitted by law.

For questions about cookies or this policy, contact info@focuslyne.com.

Related pages: Privacy Policy, Terms of Service, Contact, and Data Processing.