Cookie preferences
Choose what this sitemay store.
Everything except what is strictly necessary is off until you turn it on. Nothing here is pre ticked, nothing is bundled into a single box that also agrees to something else, and turning something off is exactly as easy as turning it on.
Today this site sets no cookie of its own, loads no analytics, no advertising and no social code, and its scripts make no network request at all. Every switch below governs a category that is currently empty, and it stays that way until something is added behind it. Verifiable in your browser's network and storage panels
Your choices
Four categories,three of them yours to set.
-
Strictly necessaryNo switch, because there is nothing to switch
What it coversAnything required for the site to work at all, such as security and load balancing at the host, and the record of the choice you make on this page. Consent is not asked for this category because the site cannot be delivered without it.
In use todayNothing, other than your own choice. This site sets no cookie, and the only thing it writes to your browser is the one entry described in the next band. It holds three true or false values and a date. It holds no identifier, no name, no address and nothing that could be matched to you.
-
FunctionalRemembering something you chose
What it coversSmall preferences that make a return visit less repetitive: a notice you dismissed staying dismissed, or a view you chose staying chosen. It never identifies you and it never leaves your browser.
Your choice
-
MeasurementCounting, not watching
What it coversCounting how many people reached a page and where they arrived from, so we can tell whether a page does its job. It does not cover session recording, heat mapping, or following you to another site, and those are not categories on this page because they are not things this site will do.
Your choice
-
MarketingAdvertising and profiling
What it coversAdvertising, remarketing, and building a profile of you across sites. HUREAL has committed that nothing offered as useful on this site carries a sales sequence attached to it, and this switch is the mechanical version of that commitment rather than a restatement of it.
Your choice
What is in your browser right now, printed rather than described. Nothing is stored in your browser for this site.
One thing about the three buttons that is worth knowing. Moving a switch changes it on the page and does not write anything. It is the buttons that write: Save my preferences records whatever the switches currently show, and Allow all and Allow only what is necessary set all three and record the result in the same action. The line above the buttons tells you which of those just happened, and the line below prints the stored value in full, so there is no state you have to take on trust.
What your choice creates
One entry,in your own browser.
Saving a preference writes a single entry to this browser's local storage under the key hureal.consent.v1. It is not a cookie, it is not sent to a server, it reaches no network, and it identifies nobody. Everything below is read out of the script at the foot of this page, which you can open and check.
-
The key
hureal.consent.v1, in local storage, on the hureal.ca origin. One entry, and there is no second one.
-
The value, in full
Three true or false values, one per switch, and the date you saved them. If you allowed measurement only, it reads exactly: {"functional":false,"measurement":true,"marketing":false,"saved":"2026-09-23"}. There is no identifier in it, and no field that is not in that list.
-
When it is written
Only when you press Save my preferences, Allow all, or Allow only what is necessary. Moving a switch on its own writes nothing.
-
How long it lasts
Local storage has no expiry of its own, so the entry stays until something removes it. The date inside it records when you chose, and nothing on this site deletes it on a schedule today. What that date is eventually used for is one of the two open decisions on this page, and it is set out in full in the last band.
-
Where it does and does not follow you
It is one browser on one device, and one profile inside that browser. It does not travel to your phone, to another browser, or to a private window, and each of those is a fresh start with everything not allowed.
-
If your browser blocks storage
In a private window, or where a policy blocks storage outright, the page tests once, finds it cannot write, and says so on the page. Nothing is stored, which is the same outcome as allowing nothing, and it is the strictest one rather than a failure.
If you change your mind
- Move any switch and press Save my preferences. The new value replaces the old one.
- Or press Allow only what is necessary, which turns all three off and records it in one action.
- Or press Clear the stored preference, which deletes the entry entirely and puts every switch back to not allowed.
- Or clear your browsing data for this site in your browser, which removes it the same way.
- Turning something off has to actually stop it, not just record that you said so. Nothing is loaded behind any switch today, so there is nothing to unload; the day there is, that is the fourth commitment in the next band and it is the one to hold us to.
- You never have to come back here to say no. Everything is off until you say otherwise, on every visit, on every device.
Why local storage rather than a cookie. A cookie is attached to every request the browser makes to this domain, so it travels whether or not anybody needs it. A local storage entry stays in the browser until something reads it. For a value whose entire job is to be read by this one page, the entry that never leaves is the smaller thing, and the smaller thing is the right one. The page is still called cookie preferences, because that is what a person looks for.
What actually loads
Every requestthis page makes.
A cookie page that lists categories and never lists the actual things is the version most sites ship. This is the list. Open your browser's network panel and reload, and it should match exactly.
- This document
The page you are reading, served from hureal.ca.
- One stylesheet
assets/hureal.css, from hureal.ca, shared by every page and cached after the first one.
- Three scripts
assets/partials.js, assets/schema.js and assets/hureal.js, from hureal.ca. None of them contains a network request of any kind, and none of them writes anything to your browser.
- Two typefaces
Inter Tight and IBM Plex Mono, requested from Google's font hosts. This is the only request on the page that goes anywhere other than hureal.ca, and it carries your IP address to a domain HUREAL does not control.
- Images, where a page has them
Served from hureal.ca. This page has none.
That is the whole list. There is no analytics script, no advertising pixel, no remarketing tag, no heat map, no session recorder and no social embed anywhere on this site today.
The commitment attached to that list
- Anything added later is added behind the matching switch above, never in front of it.
- It is listed on this page by name, with what it does and who runs it.
- A new purpose asks for consent again rather than inheriting the old answer.
- The switches keep working, including the one that turns something off after you allowed it.
Not decided yet: analytics to choose host and its logs to choose The font request is the one thing on the list that would come off it entirely, by serving the two files from this domain. That is on the published list of things that are not finished rather than described here as done.
Two positions
A banner,and how long a yes lasts.
Two things this page decides rather than leaves open: whether a first visit needs a banner, and how long a recorded choice counts. Each is stated with the reason for it.
-
Does a first visit need a banner as well as this page?Position
What HUREAL doesNo banner today, and a banner the moment anything lands behind a switch. Nothing non essential is set on a first visit, nothing identifies or locates or profiles anybody, and there is no consent to collect, so a banner would be asking permission for something that is not happening. That changes the day analytics or anything else is added: at that point the thing goes behind its switch, off by default, and a first time visitor is asked before it runs rather than after.
WhyFederal privacy legislation works on knowledge and consent: a person is told what is collected and why, and agrees to it. A first visit collects nothing beyond the request that serves the page, so there is nothing to tell a visitor in a banner that this page does not already say. Quebec's legislation adds a rule for technology that can identify, locate or profile a person: they are told before it is used and told how to switch those functions on. Rather than work out which visitor is in Quebec, HUREAL applies that rule to everybody, so anything of that kind will be off until the visitor turns it on.
-
How long is a recorded choice treated as current?Position
What HUREAL doesTwelve months from the date inside the entry, then the question is asked again rather than the old answer being carried forward indefinitely. Twelve months is the number because it is the common practice in the guidance most European regulators publish and it is the interval a person can actually remember agreeing to. Nothing on this site enforces it today: the entry carries the date and nothing acts on it, which is stated plainly in the band above rather than implied.
WhyNo Canadian statute sets how long a consent stays current, so this is a policy rather than a rule being followed. The question is asked again after 12 months, or straight away when a category on this page changes, whichever comes first. The second trigger matters more than the first: a yes given to one thing is never carried over to something new.
Neither of these blocks the page. The control works, everything is off, and nothing is stored until somebody chooses. What these two positions decide is what happens on the day that stops being true.
Privacy covers what is collected and what happens to it. Terms covers using this site. How this site is built carries the same three facts about requests and storage, in the same words, with the method for checking them.