Browser storage and tracking
CoverPilot Website Cookie Policy
This policy explains how the CoverPilot website may store small files or similar identifiers on your device and how optional technologies should be controlled.
What Website Cookies Are and How They Work
A cookie is a small text record placed by a website or service used by that website. Similar technologies can include local storage, pixels or identifiers generated by embedded tools. They may remember a preference, protect a form, measure site use or support advertising.
Categories this site may use
Strictly necessary
These support core functions such as security, load balancing, remembering a consent choice or submitting a form. Disabling them in the browser may prevent parts of the site from working.
Measurement
Analytics tools can show which pages are visited, how users arrive and where technical problems occur. Where deployed, they should be configured to minimise collected data and should follow the choice recorded in the consent tool.
Functional or embedded content
Maps, video players, chat tools or accessibility services may set their own identifiers. The provider, purpose and duration should be listed by the live consent platform before such content is enabled.
Advertising
CoverPilot does not intend to place non-essential advertising cookies without consent. Any future use should be disclosed with the relevant provider and retention period.
Managing your choice
Use the website’s cookie settings to accept, reject or revise optional categories. Browser controls can also delete existing cookies, although they may not replace consent controls for every embedded service.
Keeping the list accurate
The operational cookie inventory must be updated whenever plugins, analytics, forms or embedded services change. This narrative policy does not replace the detailed list shown by the active consent platform.
Website storage, consent and browser controls
Understand what cookies do and how to control optional use
A cookie is a small text value stored by a browser for a website or a service used by that website. Related technologies can include local storage, session storage, pixels and identifiers created by embedded tools. They may remember a consent preference, protect a form, maintain a session, measure page use or enable optional third-party content.
The important distinction is purpose rather than file format. Strictly necessary technologies support a service requested by the visitor or a core security function. Optional analytics, advertising or some functional technologies should be controlled through the consent mechanism where consent is required. Refusing optional categories should not prevent access to ordinary informational pages.
First-party cookies are set for the CoverPilot domain, while third-party cookies may be created by an embedded or connected provider. The responsible provider, purpose and retention period should appear in the live cookie inventory. Adding or removing analytics, forms, maps, video, chat, advertising or optimisation tools may change that inventory, so it must be reviewed when website technology changes.
The consent panel is the main place to accept, reject or revise optional categories. Deleting browser data can also remove cookies, but it may erase the saved consent choice and cause the panel to appear again. Private browsing, browser extensions and device-level privacy settings can change how storage works, although they do not replace the website operator’s responsibility to apply the recorded choice.
Session cookies normally expire when the browsing session ends, while persistent cookies remain until their stated expiry or manual deletion. A long expiry should be justified by the purpose. Necessary consent records may be retained long enough to remember the visitor’s choice and demonstrate that optional tools were controlled appropriately.
Blocking every cookie at browser level can interfere with form security, preference storage or other essential functions. A more precise approach is to reject optional categories through the consent panel and use browser controls for additional management. Where an embedded service cannot operate without optional storage, the feature should remain unavailable until the relevant choice is made.
This policy explains the operating principles. The detailed inventory generated by the active consent platform is the practical record of technologies detected or configured on the live website. Any discrepancy between the narrative and the live inventory should be investigated and corrected rather than assuming the policy text alone is sufficient.
- Necessary storage supports security, consent records and requested functions
- Optional analytics or advertising should follow the recorded choice
- First-party and third-party providers should be identified separately
- Purpose, provider and retention period belong in the live inventory
- Deleting cookies may also delete the saved consent preference
- Browser blocking can affect essential website features
- New plugins and embedded services require an inventory review
- Visitors should be able to revisit optional preferences later
Cookie governance is an ongoing website-control task: the consent settings, live inventory and actual technology must continue to agree.