Cookies & website technology

01

Public pages today

The inspected public website does not currently include analytics or marketing trackers, or embedded third-party players/services. A clean public-page visit did not set cookies or populate browser storage. This describes the inspected website, not a guarantee about every future release.

02

Account security

Existing platform code defines the techademy_session cookie for authenticated access: HTTP-only, same-site Lax, secure in production. A clean anonymous policy-page visit does not create it.

Verify the actual authentication lifecycle and expiry inventory before release; the policy must match the deployed service.

Confirm the strictly necessary classification and final cookie wording against the enabled authentication service.

03

Learner draft recovery

Learner activity code uses localStorage for recovery of unsaved work. This is browser storage, not an analytics cookie, and is confined to the learner activity flow rather than these public policy pages.

Review its necessity, retention/clearing behaviour, shared-device implications and final explanation before releasing that flow.

04

Analytics and marketing

No analytics or marketing trackers are introduced by this feature.

Any future analytics/marketing choice needs an approved inventory and implementation strategy.

Assess consent requirements before enabling non-essential technologies and implement consent management if needed. No consent banner is added for absent trackers.

05

Third-party services and choices

Opening an email application or following an external service link is distinct from embedding that service in a public page. Services introduced for course delivery may have their own technology and notices.

Audit any future embedded services and disclose actual cookies/storage before enabling them.

Browser settings can help manage cookies and site storage; blocking account technology may affect authenticated features. For questions use the privacy contact below.