Legal

Cookie Policy

Learn how alphx.net uses essential and optional cookies and how to manage your cookie preferences.

On this page
  1. 1. What This Policy Explains
  2. 2. What Cookies Are
  3. 3. Categories Used on alphx.net
  4. 4. Cookie and Technology Register
  5. 5. Consent and Preference Management
  6. 6. Changing Browser Settings
  7. 7. Third-Party Services
  8. 8. Retention
  9. 9. Updates

1. What This Policy Explains

This Cookie Policy explains how alphx.net uses cookies and similar technologies.

It should be read together with the:

2. What Cookies Are

Cookies are small text files or identifiers stored on or accessed from a browser or device when a website is used.

Similar technologies may include:

  • local storage;
  • pixels;
  • software-development-kit identifiers;
  • server-side tags.

These technologies may support:

  • essential website functions;
  • remembering choices;
  • measuring website use;
  • enabling third-party features.

3. Categories Used on alphx.net

3.1 Strictly Necessary Technologies

These may support:

  • security and abuse prevention;
  • form sessions;
  • multi-step form progress;
  • load balancing;
  • website stability;
  • storage of privacy choices;
  • storage of cookie preferences;
  • accessibility settings required for a requested feature;
  • language settings required for a requested feature.

Where legally permitted, strictly necessary technologies may operate without optional consent because the requested service cannot function reliably without them.

3.2 Preference Technologies

These may remember non-essential choices such as:

  • display preferences;
  • interface preferences;
  • optional user settings.

Where consent is required, they should remain disabled until consent is obtained.

3.3 Analytics Technologies

These may help ALPHX understand:

  • pages viewed;
  • traffic source;
  • conversion events;
  • errors;
  • broad device information;
  • aggregate website usage.

Analytics must not be activated until:

  1. the provider is approved;
  2. data settings are reviewed;
  3. IP handling is reviewed;
  4. retention is reviewed;
  5. the Privacy Policy identifies the processing;
  6. a consent mechanism is configured where required.

3.4 Marketing or Advertising Technologies

ALPHX does not require advertising cookies for the initial lead-generation website.

They must remain disabled unless a later business need is:

  • approved commercially;
  • reviewed legally;
  • supported by consent configuration;
  • reflected in an updated Privacy Policy;
  • reflected in an updated Cookie Policy.

3.5 Embedded Third-Party Content

Embedded services may include:

  • maps;
  • videos;
  • chat tools;
  • social embeds;
  • document viewers;
  • CAPTCHA or bot-control tools.

These services may place or access identifiers.

Where feasible, use:

  • privacy-enhanced mode;
  • click-to-load mode;
  • blocked-by-default mode until consent.

6. Changing Browser Settings

Most browsers allow users to:

  • delete cookies;
  • block cookies;
  • restrict cookies.

Blocking strictly necessary technologies may prevent:

  • forms;
  • consent settings;
  • security features;
  • other requested functionality

from working correctly.

Browser-level controls do not necessarily remove:

  • server-side logs;
  • data already processed under another lawful basis.

7. Third-Party Services

Third parties may process data under their own:

  • terms;
  • privacy notices.

ALPHX should select providers using criteria such as:

  • data minimisation;
  • security;
  • retention;
  • cross-border processing;
  • contractual terms.

The final policy must identify material third-party services operating on the public website, including any approved:

  • analytics;
  • maps;
  • videos;
  • chat tools;
  • social embeds;
  • CAPTCHA;
  • CDN;
  • embedded document viewers.

8. Retention

Cookie and identifier durations must be limited to what is necessary for their purpose.

9. Updates

This policy may be updated when:

  • website tools change;
  • plugins change;
  • providers change;
  • embedded services change;
  • tracking scripts change;
  • legal requirements change;
  • consent configuration changes.