Cookies & Storage

Effective 4 May 2026

This page explains how the OHPA intake site uses your browser's storage. We try to use the minimum needed to make the form work and keep the beta secure.

What we use

Local storage (your saved progress)

While you fill in the intake form, we save your answers in your own browser's local storage so you can leave the page and come back without losing them. This data stays on your device. We do not see it until you submit or download your intake file.

You can clear it at any time using the Delete saved progress control on the intake page, or by clearing your browser's site data.

Theme preference

We previously stored a theme preference (light/dark) in local storage. The current version of the site is light-mode only, so this is no longer used.

Access cookie

When you enter the beta password, we set a signed cookie called ohpa_gate so you don't have to enter the password every time you visit. The cookie expires after 30 days. It contains no personal information; it is just a timestamp signed by us so we know it's genuine.

Vercel Analytics

We use Vercel Analytics to count page views and understand how the form is used. Vercel Analytics is privacy-friendly by design: it does not use cookies, does not track individuals, and does not build advertising profiles. It records anonymised, aggregated visit data only.

What we don't use

  • No advertising or marketing trackers;
  • No third-party social-media pixels;
  • No cross-site tracking or fingerprinting beyond the technical cookie above.

Your choices

Modern browsers let you block, delete, or be warned about cookies and local storage. Blocking the access cookie will mean you have to re-enter the beta password every visit; clearing local storage will wipe your saved intake progress.

Contact

Questions about this page? Email legal@orchidhorizon.com.

Lawyer reviewOnce you accept EU/UK users, this page should be paired with a cookie consent banner that records explicit consent before any non-essential storage is set, and the wording should be revisited for ePrivacy / GDPR alignment.