Home › Cookies
Cookie policy
Last updated: 1 February 2026. Short, because there is not much to describe.
This site sets no advertising cookies of its own and stores nothing on your device until you make a choice in the banner. There are exactly two things it can store, and one of them is optional.
1. Essential storage — always on
| Key | Type | Lasts | Contents |
|---|---|---|---|
ls.consent.v1 | localStorage | Until changed or storage cleared | A small JSON object: the choice, the two category flags, and the timestamp of the choice. |
It exists so the banner does not reappear on every page. Without it the site cannot remember a refusal, and a refusal that is forgotten is not a refusal. It holds no identifier and no personal data beyond the choice itself.
2. Marketing storage — optional
If, and only if, you accept marketing, the Meta Pixel loads from connect.facebook.net. Meta may then set its own cookies — typically _fbp, lasting about ninety days — and will see:
- which pages of this site were viewed and when,
- the browser and device characteristics sent by any browser,
- a hashed identifier of the browser, not of your address book,
- the fact that the trial button was clicked, without the card details.
Meta uses that to attribute advertising and to build audiences. It does not receive your card number, your postal code or mail content. If you reject, nothing loads and the page is a little lighter.
Codes in use
Two conversions are sent server-blind, from the browser: a page view on load, and a trial-start when the checkout form is confirmed. No value beyond $0.50 and the currency code travels with them.
3. What is not used
- No Google Analytics, no Tag Manager, no hot-jar or session-replay tool.
- No A/B testing framework with its own storage.
- No cross-site identifiers of this site's own making.
- No cookie wall — rejecting leaves every page fully usable.
4. Changing your mind
Use in the footer at any time, on any page. The banner reopens with your current choice already reflected; change it and save.
To clear everything at once, empty site data for this domain in the browser settings. The banner will reappear on the next visit, which is the correct behaviour and not a fault.
5. Browser-level blocking
If you run a blocker, the site still works unchanged. The banner will show and your choice is stored, but the pixel request is dropped before it leaves. There is nothing to fix.
Two browser switches worth knowing, because they apply everywhere rather than only here: "block third-party cookies" and Firefox's Total Cookie Protection both reduce what any pixel can stitch together across sites.
6. Legal footing
Under PIPEDA, a cookie that is not strictly necessary needs consent, which the banner takes. The essential key rests on the same consent because it merely records it. Where the pixel transfers data outside Canada, the transfer and the contractual protection are described in the privacy policy.
Questions about any of this: hello@lasikiewicz.com, with "Privacy" in the subject line.
See also the privacy policy and the terms. Assistance service, not an antivirus.