Cookie Policy

This policy covers orbitpage.com, including the website, login and dashboard, and explains OrbitPage's consent controls on hosted user pages at orbitpage.net. OrbitPage does not load its own Google Analytics property on hosted user pages. A page owner may enable their own analytics or external services and remains responsible for any additional notice and consent required for those choices.

Cookies are small values stored by a browser and sent with later requests. Local storage and IndexedDB keep values in the browser until they are cleared, while session storage normally lasts for the current tab. Software development kits can use comparable identifiers to maintain a session or assess abuse.

Necessary technologies operate because they are required to provide a requested login, security, dashboard, preference or consent-management function. Blocking them can prevent the relevant feature from working.

App Check and reCAPTCHA are initiated when needed for protected actions such as authentication or submitting an AI-guide message. Those security requests are distinct from optional analytics and may be subject to Google Privacy Policy and Google Terms. Selecting a language or a requested interface preference does not authorise unrelated tracking.

After Allow analytics is selected on an OrbitPage-owned platform page, the open-source FingerprintJS library reads browser and device characteristics and computes a pseudonymous visitor identifier locally. OrbitPage disables the library's optional usage monitoring, sends the identifier only to its own same-origin API and stores only a purpose-bound server-side hash. When the visitor is signed in, up to ten recent hashes can be associated with the account; a signed-out lookup returns only whether that browser hash was already associated with an OrbitPage customer. The raw identifier, Firebase UID and stored hash are not sent to Google Analytics.

This signal is approximate and can change or be spoofed. OrbitPage uses it to measure returning customers, not as authentication, proof of identity or a current free-trial entitlement decision.

OrbitPage uses Google Analytics 4 only on explicitly listed platform pages on orbitpage.com, and only after the visitor selects Allow analytics. Advertising storage, Google signals, advertising user data and ad personalisation are disabled. Email addresses, usernames, Firebase UIDs, tenant IDs and page content are not intentionally sent as analytics event parameters.

Selecting Google sign-in opens Google's authentication flow. Selecting a paid plan or billing management opens Stripe Checkout or the Stripe Customer Portal. A Shop seller is redirected to Stripe-hosted connected-account onboarding and management, and a Shop buyer is redirected to Stripe Checkout. Opening a seller's Cal.com booking link opens the selected provider flow. Those providers may use their own necessary, security and fraud-prevention technologies on their domains. Their policies apply while you use those provider pages.

PostHog loads only after analytics consent. Its ph_*_posthog local-storage entry and session-storage values associate platform events with a browser session and a pseudonymous account. They are removed when consent is withdrawn or expires on a subsequent visit. The account choice is also stored server-side to control product events, including confirmed publication and subscription changes.

Selected editor recordings mask inputs, customer text and content attributes while preserving layout, bundled styles, standard icons and static navigation labels. Media and embeds are blocked. Authentication, billing, account, team, Shop, newsletter and AI panels are excluded from replay. Request bodies, headers and console logs are not recorded. PostHog remains stopped before consent, after withdrawal and when Global Privacy Control is enabled.

PostHog requests use t.orbitpage.com, our dedicated subdomain for its Cloudflare-based managed reverse proxy, and are forwarded to PostHog Cloud EU. The proxy removes the Cookie header before forwarding. This routing does not replace consent, change the optional purpose or enable tracking on customer pages. No PostHog cookies are intentionally used by our local-storage configuration. The platform choice is kept for 180 days; SDK local-storage identifiers remain until cleared or removed on withdrawal or detected expiry, and session-storage values normally last for the tab.

A page owner can add public content from independent services. OrbitPage supports social and video services such as Instagram, Facebook, YouTube, Vimeo, Loom, TikTok and Giphy; audio services such as Spotify, Apple Music, Deezer, SoundCloud and Mixcloud; and utility services such as Google Maps, Google Calendar, Calendly, Typeform and Google Forms.

Ordinary external links do not load the destination service until a visitor chooses to open them. Embedded partner content is initially replaced with a consent notice and no request is sent to the provider. The embed loads only after the visitor grants the category configured for that block, normally Preferences for maps, booking, forms and audio players or Marketing for social and video content. The page owner can change the category and is responsible for using an appropriate lawful setting.

After an embed is allowed, the external provider can receive the visitor's IP address, browser information, referring page and provider-specific cookies or identifiers. Existing sign-in state with that provider can also affect what it displays. OrbitPage does not control those technologies. The provider's own privacy and cookie terms apply.

A page owner may replace the built-in banner with iubenda, Cookiebot, CookieYes, OneTrust or an approved custom consent manager. The selected script can set its own cookies or browser values and receive consent, page and device information. The page owner is responsible for the provider contract, configuration, cookie list, legal basis and ensuring that optional content remains blocked until a valid choice.

An eligible page owner may configure their own Google Analytics tag. It is separate from OrbitPage's platform property and remains blocked until the public-page visitor grants analytics consent. The page owner is responsible for the property configuration, data retention, notices, legal basis and responses to visitor rights requests.

The first consent prompt presents optional analytics separately from essential storage. You can change or withdraw your choice at any time using Cookie settings, choose Essential only, and continue using the requested service. Withdrawal stops PostHog and its replay, removes its project-specific browser storage, updates Google Consent Mode, removes accessible OrbitPage-domain _ga* cookies, removes the current returning-customer browser hash from the signed-in account when available and reloads without analytics or fingerprinting. The account preference also controls server product events; if saving it fails, the interface shows a retry message and server withdrawal completes only after a successful update. Withdrawal does not erase earlier provider records; request their erasure through the privacy contact channels. Account deletion removes every returning-customer hash stored with that account. Provider or browser storage outside OrbitPage's domain may need to be cleared in browser settings.

Newsletter open and click measurement requires a separate, optional consent, initially unchecked. Confirmation activates only the choice expressly requested. Existing and imported subscribers have no tracking permission by default. Without permission, OrbitPage omits tracking pixels and remote images and uses direct destination links. Each campaign email contains a tracking-preference link: withdrawal stops new engagement records, including for previously sent messages, without ending the subscription. Later consent does not reactivate old messages. Where authorised, OrbitPage records the first open and click times for the recipient and campaign; reports remain until the campaign or account is deleted. Consent records include the notice version, time, source and sender privacy-policy URL. Email proxies and scanners may distort these metrics. Senders must disclose this processing and disable any independent SMTP-provider tracking unless separately authorised. OrbitPage platform marketing is blocked when its provider tracking is enabled or cannot be verified as disabled.

You can delete or block storage through browser settings. Because necessary storage supports security and requested account functions, blocking it can stop sign-in or dashboard features. OrbitPage does not use advertising cookies, sell personal data or share it for cross-context behavioural advertising. On OrbitPage-owned platform pages, an enabled Global Privacy Control signal overrides a prior analytics grant and keeps Google Analytics, PostHog and returning-customer fingerprinting denied; it does not affect necessary security or a provider page that you deliberately open. Page owners remain responsible for GPC handling by their own analytics, CMP and external services.

This policy is updated when browser storage, providers or purposes materially change. Questions can be sent to contact@orbitpage.com.