Oravelin
── ── ── Legal Document / Rev. 1.1 — 2026

COOKIE POLICY

This policy explains how oravelin.info uses cookies and similar tracking technologies, what categories of cookie are in use, and how visitors can manage their preferences.

Last updated: January 2026
1

What Are Cookies

Cookies are small text files placed on a visitor's device by a website. They serve a range of functions: some are essential for the website to operate as expected, while others gather information about how the site is used, or remember preferences set during a previous visit.

Cookies do not provide direct access to a visitor's device and cannot read data stored in other cookies or from other websites. The information contained in a cookie is limited to what the issuing website places within it.

2

Cookie Categories Used on This Site

Functional Cookies Always Active

These cookies are necessary for the website to function correctly. They manage session state, remember cookie consent choices, and enable navigation between pages without loss of state. Functional cookies cannot be disabled without affecting site operation.

Cookie Name
Duration
Purpose
oravelin_consent
12 months
Stores cookie consent preference
oravelin_session
Session
Maintains session state during visit
Analytics Cookies Consent Required

Analytics cookies gather aggregated, anonymised information about how visitors navigate the website. This data is used to understand which pages are visited, how long sessions last, and where visitors enter and exit the site. No personally identifiable information is stored within analytics cookies.

Cookie Name
Duration
Purpose
_ora_anon
6 months
Anonymised session identifier
_ora_nav
30 days
Page navigation sequence recording
Third-Party Cookies Consent Required

Third-party cookies may be set by external services embedded within or linked from this website. These include font loading services (Google Fonts) and CDN-hosted JavaScript libraries. These third parties operate under their own cookie and privacy policies, which are separate from this document.

Oravelin does not control the cookies set by third-party services and recommends reviewing the privacy policies of Google and jsDelivr where relevant.

3

Managing Cookie Preferences

When visiting oravelin.info for the first time, a consent banner is presented at the bottom of the page. The banner provides three options: Accept All (accepts functional, analytics, and any third-party cookies), Accept Partial (accepts functional and analytics only), and Functional Only (accepts only essential functional cookies).

Cookie preferences can be reviewed and updated at any time by selecting "Cookie Settings" in the footer of any page. The updated preference will take effect immediately.

Cookies can also be managed directly through browser settings. The process for doing this varies by browser. Links to the relevant instructions for common browsers are listed below.

Google Chrome: Settings > Privacy and Security > Cookies and other site data
Mozilla Firefox: Settings > Privacy & Security > Cookies and Site Data
Apple Safari: Preferences > Privacy > Manage Website Data
Microsoft Edge: Settings > Cookies and site permissions > Cookies and site data
4

Opt-Out Options

Visitors who do not wish to accept non-functional cookies may select "Functional Only" from the cookie consent banner. This option restricts all cookies to those essential for page navigation and consent-state management.

Blocking all cookies via browser settings will prevent the consent preference from being stored. This means the cookie banner will reappear on each visit until a preference is recorded.

For objections or questions about specific cookies, contact Oravelin at [email protected]. Enquiries of this nature are addressed within five working days.

5

Updates to This Policy

This cookie policy is reviewed periodically and updated when changes to cookie usage or applicable regulations require it. The revision date at the top of this document indicates the most recent update.

Any material changes to how cookies are used will be communicated through an updated consent banner on the next visit to the site following the policy change.