ePrivacy mindset
PECR alignment
The role of cookies here
Cookies and analogous technologies keep consent memories honest, protect forms from simple bots, help carts persist during flaky connections, and—only after you opt in—tell us which landing experiments resonate without stalking individuals across unrelated sites.
We document categories consistent with UK Information Commissioner guidance and the Transparency & Consent Framework expectations where applicable to display partners.
Strictly necessary layer
These tools load even if you reject analytics or marketing because without them the storefront would break or violate security baselines. Examples include session continuity tokens, load-balancer affinity flags, CSRF guards on the enquiry form, fraud scoring fingerprints condensed to risk scores, and the JSON object that stores your latest consent snapshot in localStorage with a rolling thirty-day refresh.
You cannot switch this layer off via our interface; browsers may still block all cookies, but checkout or double-submit protection might fail.
Analytics layer (optional)
When you toggle analytics on, first-party or authorised vendor cookies may record pseudonymous identifiers, landing URL, scroll milestones, and conversion funnels tied to Novixa domains only. Raw IP addresses are truncated where the platform allows. Default retention follows vendor defaults—often thirteen months rolling—but we request the shortest interval that still yields trend visibility.
Aggregated dashboards feed through internal slide decks; we do not sell row-level browsing histories.
Marketing & attribution layer (optional)
Marketing cookies let us see whether creative concepts lead to enquiries without assuming medical outcomes. Pixels may measure view-through reminders, frequency caps, and creative rotations. Partners must honour the same consent string and provide subprocessors lists on request.
If you never opt in, those tags should not execute; our tag manager suppresses firing based on the consent object.
Local storage & session storage nuance
Some UX helpers (saved tab positions on lengthy policies, ephemeral draft messages before submit) rely on storage APIs instead of cookies. They follow the same necessity rules: drafts flush when you close the tab unless you explicitly save them.
Changing your mind
Re-open the cookie settings control from any footer link, withdraw marketing while keeping analytics, or reject everything optional with two taps. Updates propagate to tags on the next page load. Historical server logs may still contain past events until their retention slice expires.
Browser-level controls
Every major browser ships global blocking, per-site exceptions, and “delete on exit” schedules. NGO resources such as YourOnlineChoices.eu describe industry opt-outs for interest-based advertising. Combine those tools with our granular toggles for layered comfort.
Review cadence
Quarterly inventory reviews catch renamed cookies, new vendors, or retired tags. The live stamp in the masthead refreshes automatically each time you load the page so you always know we synchronised wording with today’s calendar reality.
These statements describe data practices, not supplement efficacy. Refer to product labels for composition facts.
Operational contact
Plaxyrondhak.world, 72 New Street, Birmingham B2 4DU, United Kingdom. Privacy & cookie mailbox: chat@plaxyrondhak.world.