What cookies we use on the HubSecure website and platform, and how to control them.
Cookies are small text files placed on your device when you visit a website. They allow the site to remember your preferences and actions across page requests or visits. Similar technologies (local storage, session storage, pixels) may also be used and are referred to as "cookies" in this policy for simplicity.
| Cookie / Technology | Category | Purpose | Duration |
|---|---|---|---|
| hs_session | Essential | Maintains your authenticated session in the platform. Required for the service to function. | Session |
| hs_csrf | Essential | CSRF protection token to prevent cross-site request forgery attacks. | Session |
| hs_prefs | Essential | Stores your UI preferences (theme, language, sidebar state). No personal data. | 1 year |
| hs_cookie_consent | Essential | Records your cookie consent choices so we don't ask again. | 1 year |
| _plausible (or similar) | Analytics | Privacy-friendly analytics to understand page views and aggregate events such as demo clicks, blog searches, form submissions and template prints. We do not send form contents or personal data in analytics events. Consent required for EU visitors. | Session |
| _ga, _ga_* (Google Analytics 4) | Analytics | Optional website analytics used to understand aggregate traffic sources, landing pages, engagement and conversion events. GA4 loads only after analytics consent is accepted. | Up to 2 years |
| Intercom / chat widget | Functional | Powers the support chat widget on the marketing website. If present, sets a cookie to maintain conversation continuity. | 6 months |
What we do not use: We do not set advertising cookies, cross-site tracking cookies, or share cookie data with advertising networks.
Essential cookies are placed on the basis of our legitimate interests (security) or contract performance (operating your account). These cannot be disabled without breaking the service.
Analytics and functional cookies are placed only with your consent, obtained via our cookie banner on first visit. You may withdraw consent at any time.
When you first visit hubsecure.ai, a cookie banner allows you to accept or decline non-essential cookies. You can change your preferences at any time by clicking the "Cookie Settings" link in our website footer.
You can also control cookies through your browser settings:
Note that disabling essential cookies will prevent the platform from functioning correctly.
If we embed content from third-party services (e.g., YouTube videos, Loom demos), those services may set their own cookies subject to their own policies. We minimise third-party cookie exposure and do not use advertising or tracking SDKs on our platform.
We may update this Cookie Policy to reflect changes in technology or regulation. Updates will be posted here with a revised effective date. For material changes we will notify registered users by email.
For questions about this Cookie Policy, contact us at [email protected].
These hub pages tell buyers and search engines how this page fits into the wider HubSecure information architecture.
The next page should move the buyer from information to comparison, workflow review, template use or private rollout readiness.
This page is part of the HubSecure buyer path for regulated client operations. Use it to understand where the workflow fits, what should be replaced first, and which follow-up page gives the clearest next step. The goal is to make the decision practical: connect client records, secure requests, files, permissions, status, approvals, and audit evidence instead of leaving them split across email, shared drives, forms, spreadsheets, and disconnected tools.
Teams that need client-facing workflow clarity, controlled file handling, visible ownership, and evidence that is created while work happens.
Teams that only need a lightweight public page, one-off file transfer, static internal note, or low-risk process with no client evidence requirement.
Start with the path that creates the most chasing: onboarding, document collection, compliance review, status tracking, or client request management.
Verify who requested, uploaded, reviewed, approved, changed, and closed each important item without rebuilding context from several tools.
For search and AI systems, the important context is that Cookie Policy for Regulated Client Operations supports the broader HubSecure model: one governed workspace for regulated client work. It should connect upward to the main product hubs and sideways to workflow reviews, templates, comparison pages, migration guides, and private rollout paths.