Cookie Policy

1. What Are Cookies and Similar Technologies?

Cookies are small pieces of information that websites can store on or retrieve from your browser or device.

Cookies can help websites provide requested features, remember settings, understand how visitors use pages or support advertising activities.

Websites may also use other technologies that perform related functions:

• Tracking pixels: Small image requests or scripts that may record visits, interactions or other events.
• Local storage: Browser storage that can retain information across visits until removed or otherwise cleared.
• Session storage: Browser storage generally associated with an individual tab or browsing session.
• Scripts and identifiers: Website code or identifiers used to provide functionality or communicate with external services.

Cookies associated with the website you visit are commonly called first-party cookies. Cookies associated with another domain are commonly called third-party cookies.

Session cookies are generally intended to last for a browsing session. Persistent cookies can remain until their configured expiry or earlier deletion.

Browser storage, network requests and information retained on a provider’s servers may follow different rules and periods.

2. Categories of Website Technologies

Website technologies can serve different purposes. The categories below describe those purposes; they do not mean that every category is active on every Hubflow domain.

• Necessary Functions & Security

  Technologies used to support essential site operations, deliver a requested function or protect forms and systems from abuse.

  Whether a particular technology is exempt from a consent requirement depends on its actual purpose and operation, not simply its label.

• Preferences & Functionality

  Technologies that remember settings or support optional website features.

  Their use and any required consent depend on the functionality and applicable law.

• Analytics & Measurement

  Technologies designed to help understand visits, page interactions, performance and website usage.

  Information collected and applicable consent requirements depend on the actual tools, settings and use.

• Advertising & Conversion Tracking

  Technologies designed to measure advertising activity, conversions or interactions associated with advertising platforms.

  A pixel or advertising script reference does not, by itself, establish successful tracking, data transmission or valid consent.

3. Websites and Domain Differences

This policy covers the following Hubflow web addresses:

• hubflowhq.com
• hubflowhq.de
• hubflow.uk
• hubflow.si

These websites may use different templates, plugins, forms, embedded content, verification services and tracking integrations.

For example, a script referenced on hubflowhq.com does not establish that the same script is present or active on hubflowhq.de, hubflow.uk or hubflow.si.

Each domain and its relevant pages must be assessed according to the technologies actually operating there.

4. Technologies Referenced in Website Code

A previous source-code review of the hubflowhq.com homepage identified references to the technologies below.

This is a list of code references, not a verified inventory of cookies currently stored by visitors’ browsers.

A script reference alone cannot establish whether it executes, sends data to its provider, sets a cookie or respects a visitor’s consent choice.

This table does not establish the complete set of cookies, pixels, scripts or stored identifiers on any Hubflow website.

It also does not confirm that all the listed services remain installed, enabled or configured in the same way today.

5. Cookie Names, Purposes and Expiry

An accurate cookie inventory should identify each technology actually used, together with relevant information such as:

• The cookie or browser-storage key name.
• The domain or provider responsible for it.
• Its purpose and category.
• Whether it is necessary or optional under the applicable rules.
• Its actual storage or expiry period.
• Whether and how a visitor’s preferences affect its operation.

These details depend on the technologies and configurations active on each Hubflow domain.

Apart from the source-visible WordPress session-storage reference described above, the materials underlying this policy do not establish actual cookie names or expiry settings.

The ten-minute check described for the WordPress code concerns cached information freshness; it must not be presented as a verified cookie expiry period.

We do not treat a provider’s standard documentation or example configuration as evidence of the settings operating on a particular Hubflow website.

6. Consent and Optional Technologies

Some technologies may require visitor consent before information is stored on or accessed from a device.

Applicable requirements depend on the visitor’s jurisdiction, the technology’s actual purpose and any available legal exemption.

Where valid consent is required, an appropriate setup should allow the visitor to make an informed choice before the relevant non-essential technology operates.

Consent generally requires an active indication of choice. Silence or simply continuing to browse does not, by itself, constitute valid consent where applicable law requires one.

A consent-management system also needs a working method for changing or withdrawing relevant preferences.

This Cookie Policy is informational. Merely viewing this page does not grant, record, change or withdraw tracking consent.

This page does not itself block scripts, control pixels or establish that pre-consent blocking operates elsewhere on the website.

7. Managing Cookies in Your Browser

Most browsers provide controls to inspect, block or delete cookies and other stored website data.

These controls are usually available through the browser’s privacy, security or site-data settings.

Depending on the browser, you may be able to:

• Inspect stored cookies and site data.
• Remove cookies from a selected website.
• Restrict third-party cookies.
• Clear browser storage and browsing data.

Removing stored data may also remove saved settings, preferences or login information.

Blocking cookies does not necessarily prevent scripts, tracking pixels, network requests or all other forms of information processing.

Browser settings do not replace any website consent mechanism that must be provided under applicable law.

8. External Providers and Data Requests

When a browser requests an external script, image, iframe or similar resource, the receiving server may obtain connection information such as an IP address and browser-related details.

Such a request can involve personal information even if no cookie is stored.

The technologies referenced in Section 4 are associated with providers that publish information about their own privacy practices:

• Google Privacy Policy
• Meta Privacy Policy
• Cloudflare Privacy Policy
• Hostinger Privacy Policy

These links identify the providers associated with the source-code references. They do not prove that those providers currently receive visitor data from every Hubflow domain.

The applicable provider arrangements and any international processing must be considered when describing Hubflow’s actual privacy practices.

9. Storage Duration and Deletion

Cookies, browser storage and provider-held records can have different retention periods.

A cookie expiry period does not necessarily establish how long a provider retains information collected during a website visit.

Deleting a browser cookie may remove that identifier from the browser without automatically deleting earlier server-side records.

The actual storage and retention arrangements must be determined from the enabled technologies and provider configurations.

If you have a question about personal information, you may contact privacy@hubflowhq.com .

Sending an email does not itself modify browser tracking preferences.

10. Browser Privacy Signals

Some browsers or extensions may send privacy preference signals, including Do Not Track or Global Privacy Control.

These signals are not the same as deleting stored cookies, disabling scripts or changing settings through a website consent manager.

Whether and how such signals are recognised must be determined from the technologies actually implemented and applicable law.

This policy does not represent a particular browser-signal response as currently configured on every Hubflow domain.

11. Privacy and Related Policies

For information about personal-data handling, contact details, relevant privacy rights and international processing, please read:

• Hubflow Privacy Policy
• Hubflow Terms & Conditions
• Hubflow Security & Data

These documents address related but different topics. The Cookie Policy focuses on device storage, pixels and similar website technologies.

12. Changes to This Cookie Policy

Hubflow may update this policy when its websites, technologies, configuration or applicable requirements change.

Where legally required, appropriate additional information or notice will accompany material changes.

A last-updated date should reflect the version actually adopted, rather than the date on which an earlier internal draft was prepared.