SEE · LOOK AGAIN / YOUR ONLINE EXPERIENCE

Cookie Policy

A clear guide to the cookies and similar technologies that may support your SEE account, learning experience and secure purchases.

Last updated: 21 October 2026
🔐

Secure access

Understand how sessions help protect your account and course access.

⚙️

Know the purpose

See the difference between essential, optional and third-party technologies.

🧭

Stay in control

Learn about consent, browser settings and your available choices.

Cookies, explained simply. SEE uses a member-based learning platform, so some browser storage is important for security and access. Other technologies, if introduced, may require your consent or an easy way to object. This policy explains the distinction.

01Understanding cookies

Cookies are small pieces of information a website can ask your browser to store and return on later visits. Similar technologies include browser storage, embedded scripts, pixels and device identifiers. They can help a service recognise a logged-in session, remember choices, or measure usage.

This policy covers see2.net, The Observation Lab, courses, assessments, games, quizzes and digital materials. It should be read with our Privacy Policy and Terms of Use.

02Essential cookies and sessions

SEE uses a PHP-based account system. Session technologies may be necessary to keep you signed in, validate requests, apply account permissions, protect against misuse and deliver the learning experience you request.

Account access

Session identifiers allow a signed-in member to move between dashboard pages without re-entering credentials on every request.

Security

Security-related storage may help with session integrity, request validation and prevention of unauthorised access.

Course and game access

Session data can support access checks for paid courses, materials, quizzes and games.

Checkout continuity

Essential checkout-related storage may keep a transaction secure and connected to the right user.

Where storage is strictly necessary to deliver a service you request, consent may not be required, but we still explain its purpose.

03Types of cookies and technologies

CategoryWhat it may doConsent / control
Strictly necessaryAuthentication, account sessions, security and essential checkout functions.Generally exempt when genuinely necessary for the requested service.
PreferencesRemember a display or interface choice.Depends on purpose and applicable exception; some uses require consent or an objection option.
StatisticsMeasure site visits and usage patterns.May qualify for a limited UK statistical exception if all conditions are met; otherwise consent is required.
MarketingTrack advertising campaigns or activity across services.Requires consent before use.
Third-partySupport payment, video, embedded content or external services.Assessed by purpose, not merely by who sets it.

Listing a category here does not mean SEE currently deploys every category.

04Cookies and storage used by SEE

SEE uses PHP-based session technology to support secure member sign-in, request validation and account access. Session identifiers help associate your browser with your active SEE session; account records and learning progress are handled by SEE's server-side systems.

Payments are processed through Stripe, which may use cookies or similar technologies for payment security and fraud prevention. Other technologies may be involved when you interact with external services or choose optional features.

The names and lifetimes of individual cookies can vary according to the technology and service involved. You can inspect and remove cookies through your browser's site-data or privacy settings.

05Cookies in The Observation Lab

SEE's member platform offers free quizzes, paid body-language courses, game sessions, course assessments, progress records, achievements and diplomas. Session technologies may help associate your browser with your authenticated account and enforce access permissions.

Your assessment results, course completions, game scores and certificates are generally account records managed by SEE's server-side systems, rather than being stored entirely inside a browser cookie. Read the Privacy Policy for how account records and personal data are handled.

06Purchases and Stripe checkout

When you purchase a course or downloadable learning material, SEE uses Stripe for payment processing. Payment pages or embedded payment elements may use cookies or related technologies for secure checkout, fraud prevention and transaction continuity.

Some technologies may be strictly necessary for secure checkout, while other uses are subject to applicable consent requirements. Stripe describes its own practices in its Privacy Policy and related cookie information.

SEE's Cookie Policy does not change the purchase, cancellation or refund provisions explained in our Terms of Use.

07External services and embedded content

SEE may link to or embed services operated by others, such as payment pages, video platforms or social networks. If an external page opens, that provider's privacy and cookie practices may apply. An embedded service can sometimes store or access information without you leaving SEE.

Embedded content or external services may use their own cookies or similar technologies. Non-essential tracking and advertising technologies are subject to the consent rules described below.

09Manage cookies in your browser

Most browsers let you view, delete or block cookies and clear site data through their privacy settings. You may also be able to block third-party cookies or limit tracking.

Blocking essential cookies may prevent login, account verification, protected course access or secure checkout from working. Clearing cookies can sign you out of SEE.

10How long cookies last

Session cookies normally expire at the end of a browser session or according to server-side session rules. Persistent cookies remain until their configured expiry or until you remove them.

Cookie lifetimes vary according to their function and provider. Your browser’s privacy or site-data settings may show individual cookies and allow you to delete them.

11Security and cookie handling

Authentication sessions rely on secure browser and server-side controls. Session identifiers are used to recognise a session; authorisation and access permissions are checked on the server. Passwords and payment-card information should not be stored in readable cookies.

12Changes to this policy

We may update this policy when SEE changes website functions, payment integrations, analytics, advertising or other technologies. The date at the top will show when the policy was last revised. Where additional consent is legally required, it applies before the relevant technologies are used.

13Questions and complaints

If you have questions about cookies, your privacy or the technologies used by SEE, contact accounts@see2.net or use our contact page. You can also read our Privacy Policy for details of personal data rights and complaints.

↑ Back to top