This Cookie Policy explains how Hypha Technologies Ltd (“Hypha”, “we”, “us”) uses cookies and similar technologies on Hypha and related features. It should be read together with our Privacy Policy.

We operate in the UK/EU and keep things minimal: we currently set two essential cookies and one functional cookie. We do not use third-party advertising cookies.

1) What are cookies?

Cookies are small text files stored on your device. We use only first-party cookies (set by Hypha). You can control cookies via your browser settings and, where applicable, via our in-product cookie controls.

2) Cookie categories we use

• Essential (strictly necessary): required to provide core features you request (sign-up, login, secure access). These do not require consent under UK/EU rules.
• Functional: improves service operation and integrity (e.g., consistent playback stats, basic anti-fraud). We seek consent where required; you can opt out in settings or your browser.

3) Cookies we set

We do not set analytics cookies. Aggregate usage metrics are collected without device-level identifiers.

4) Your choices

• Essential cookies: required for sign-up, login, and secure content access. If you block them, Hypha will not function properly.
• Functional cookies: you can opt out via our cookie controls or your browser. Core playback will still work, but view counts and some anti-fraud protections may be less accurate; we will continue to use server-side safeguards.
• Browser settings: you can block or delete cookies in your browser (see your browser’s help pages). Doing so may affect site functionality.

5) Security & use of cookie data

Cookie values are stored and transmitted securely. We do not sell cookie-derived data or allow third parties to use it for their own purposes. We use cookie data only to operate and protect the Service and to provide the features described above.

6) Updates to this Policy

We may update this Cookie Policy to reflect changes in our use of cookies or legal requirements. For material changes, we will provide notice in-product and/or by email at least 30 days before the effective date, unless a change is required sooner for security, compliance, or to fix an error.