Cookie Policy

This policy describes cookies and similar browser storage observed in the current Riffparcel checkout. Cookies are small values sent with web requests; similar browser storage includes values kept locally by the browser, such as the consent preference described below. The deployed inventory remains subject to the owner and platform review items at the end of this policy.

The account and client-portal routes use authentication cookies or similar session technology so that a signed-in visitor can stay recognised and access the correct protected surface. This technology supports sign-in, session security and site functionality. This page does not assert final cookie names, durations or classifications; those details must be confirmed from the deployed configuration.

The site stores the analytics choice in the versioned first-party “riffparcel_consent” session cookie: “v1.1” means analytics is enabled and “v1.0” means it is disabled. The cookie uses Path=/ and SameSite=Lax; Secure is added over HTTPS. It has no fixed expiry. A valid saved choice records whether optional analytics is enabled; essential site functions remain on. Missing, malformed or unsupported cookie values leave optional analytics off and keep the consent notice available. If browser cookie access is blocked, the controls remain usable but the choice cannot be saved and Meta Pixel stays off.

The current site uses the app-owned Meta Pixel for page-view and related event measurement. It is non-essential analytics and is loaded only after a visitor explicitly accepts analytics or saves preferences with analytics enabled. No choice, rejecting optional cookies or saving preferences with analytics off leave it unloaded. A visitor can withdraw or change this choice through the “Cookie preferences” control or the “Cookie settings” action in the footer. The owner must confirm the final Meta provider details, purposes, retention, lawful basis, transfers and withdrawal wording under UK GDPR and PECR.

The Polsia framework may create a browser-local visitor identifier and send a page-view beacon when deployment analytics is enabled. That beacon is separate from the app-owned Meta Pixel and is framework-controlled in this checkout. This notice and the “Reject optional” choice do not claim to disable it. Its UK classification, lawful basis, retention, provider details and available control require owner and platform confirmation.

Before this policy is treated as published, the owner must compare it with the deployed cookie inventory and confirm each purpose, provider, transfer detail, duration and retention period. The owner must also confirm the UK GDPR and PECR assessment, the effective date, controller and contact details, withdrawal and complaint wording, and any final ICO-facing information. These are review requirements, not facts asserted by this page.