Last updated: 29 September 2026.
About this Policy
Octanist B.V. uses cookies, local storage, identifiers and scripts on its website and platform to support account functions, security, preferences, measurement and enabled tracking features. This Policy also explains how Octanist tracking on customer websites differs from our own website. Contact: support@octanist.com or +31 85 004 78 67.
Cookies and identifiers may contain or be linked to personal data even when they do not contain a name. First-party storage is not automatically anonymous or exempt from consent requirements. Our Privacy Policy explains related personal-data processing.
Technologies and purposes
Authentication and account storage
Purpose and scope: Maintains sign-in, sessions and requested account functions on Octanist. The current application session lifetime is 180 days and may be refreshed during continued use; a session lifetime is not a retention limit for account data stored on our servers.
Interface preferences
Purpose and scope: Remembers choices such as lead-table columns and page size. The Octanist app uses local storage, including octanist:leads-preferences. These preferences can persist until cleared or replaced and do not have the same lifetime as a session cookie.
Cloudflare security and Turnstile
Purpose and scope: Helps protect requests and forms against automated abuse. The technologies used depend on the security checks applied to the request.
PostHog
Purpose and scope: Supports product-usage measurement and error analysis, including account and organisation context where the user is signed in. Browser identifiers or storage may be used to associate events.
Google Tag Manager
Purpose and scope: Loads configured website tags. The container is not itself a complete description of the cookies or processing performed by an individual tag. Each enabled tag has its own purpose and settings.
Octanist tracking and dynamic number insertion
Purpose and scope: Associates visits, sessions, campaign information and submitted leads, and supports assignment of call-tracking numbers where enabled. Storage and data flows depend on the deployment and enabled features.
Embedded or linked third-party services
Purpose and scope: Booking, media or other external services may receive device/request information and use their own storage when accessed. Their notices explain their processing.
Session storage generally lasts for the relevant browser session. Persistent cookies have their own expiry and may be renewed when used. Local storage can remain until cleared or changed by the application. Clearing browser storage does not by itself delete records already held by Octanist or another provider.
Your choices
You can use your browser's site-data controls to inspect, block or delete cookies and local storage. Blocking storage needed for sign-in or security may prevent those functions from working. Browser blocking does not necessarily prevent every server request, and deleting storage does not prevent it from being created again on a later visit.
Where consent is legally required for optional tracking, it must be obtained before that tracking is used and must be capable of withdrawal. This Policy and continued browsing do not themselves constitute consent. You may contact support@octanist.com about tracking, to object to processing or to withdraw consent previously given to Octanist. Withdrawal does not affect processing that was lawful before it was withdrawn. We do not describe browser controls or an email request as a replacement for any prior-consent control required by law.
Octanist on customer websites
Customers deploying the Octanist pixel, form capture or dynamic number insertion determine their purposes and must provide their own accurate notices and required consent controls. Their website, tag-manager configuration and other scripts determine which technologies run there. The customer is responsible for connecting and configuring its consent system appropriately.
A recorded consent flag or a feature toggle does not by itself prove that valid consent was obtained. Recording and transcription requirements are separate from website analytics or advertising consent.
Subscription cancellation does not automatically remove an installed pixel or stop incoming lead submissions. Customers can stop website collection by removing the Octanist pixel. API, form and integration sources must also be disabled if they continue sending leads. Organisation owners can delete their organisation through the dashboard, which also ends collection into that organisation. Support is available for assistance. Retention and deletion are explained in the Privacy Policy and DPA.
Contact and updates
Contact support@octanist.com for information about the technologies relevant to a particular Octanist page or deployment. We will update this Policy to reflect material changes. Where a changed use requires new consent, updating this Policy alone does not provide it.
See our Privacy Policy and Subprocessor Register.