Verlant Cookie Policy

Cookies and local storage.

This policy explains how Verlant uses cookies and similar browser storage technologies, including the sign-in cookie and local storage used to keep the app working smoothly.

Last updated: 13 June 2026

Current status: Verlant uses essential authentication storage, functional local storage, and optional analytics. Optional analytics loads only after consent and is used for aggregate visitor counts, page views and bounce rate.

1. What cookies and similar technologies are

Cookies are small files stored on your device by a website. Similar technologies include local storage and other browser storage that can save information on your device or read information from it.

UK rules distinguish between strictly necessary technologies and optional technologies such as analytics or marketing cookies. Strictly necessary technologies are needed to provide the service you request. Optional analytics or marketing technologies usually require consent before they are used.

2. What Verlant currently uses

Technology

Purpose

Duration

Type

Choice

verlant_session

Keeps signed-in users authenticated and lets server routes verify Firebase session state.

5 days, unless you sign out or clear cookies sooner.

Strictly necessary HTTP-only cookie

Always on for signed-in use.

verlant-theme

Stores your light/dark theme preference.

Until changed or cleared in your browser.

Local storage preference

User-requested preference storage.

Interview draft and job state keys

Keeps in-progress interview answers and presentation job state available after refreshes.

Until the session state is overwritten, cleared by the app, or cleared in your browser.

Functional local storage

Used to support active practice flows.

verlant-cookie-consent-v1

Records whether you accepted or rejected optional analytics.

Until changed or cleared in your browser.

Consent preference local storage

You can accept or reject optional analytics.

verlant-visitor-id-v1

Counts aggregate unique visitors when optional analytics is accepted. The server stores a hashed identifier, not the raw browser value.

Until cleared in your browser.

Optional analytics local storage

Only used if you accept optional analytics.

verlant-visit-session-id-v1

Counts aggregate visits, page views and bounce rate during a browser tab session when optional analytics is accepted.

Current browser tab session.

Optional analytics session storage

Only used if you accept optional analytics.

3. Strictly necessary cookies

The `verlant_session` cookie is used to keep you signed in and protect server-side routes. It is set by Verlant's authentication endpoint after Firebase verifies your sign-in token. It is HTTP-only, which means JavaScript in the browser cannot read it.

This cookie is required for signed-in features such as Interview AI, Speech Coach, Language Coach, CV review, billing, settings, and organisation dashboards.

4. Local storage

Verlant uses local storage for user-requested preferences and active practice flows. This includes theme preference and temporary interview draft or job state so that a page refresh does not immediately lose your in-progress work.

Local storage is stored in your browser. You can clear it through your browser settings, but doing so may remove theme preferences or in-progress practice state.

5. Analytics and marketing cookies

Verlant uses optional analytics only after consent. This includes Vercel Analytics and a first-party aggregate visitor session counter for admin reporting.

We do not currently use advertising, retargeting, or behavioural marketing cookies in the repository evidence reviewed. If advertising or behavioural tracking is added later, Verlant should update this policy and ask for consent where required before loading those technologies.

6. Managing your choices

You can accept or reject optional analytics using the cookie banner. If you reject optional analytics, Verlant will not load the optional analytics component or record first-party visitor session analytics from this browser.

7. Related documents

You can also review Verlant's Terms and Conditions. A public Privacy Policy should be published before full production launch and should be read alongside this policy.