Cookie Policy

What are cookies?

Cookies are tiny text files stored by your browser on the device you’re reading this on. They let a website remember things between page loads — for example, that you’ve already dismissed the consent banner, or that you have an active form session that shouldn’t be hijacked. Most cookies are harmless; some are useful; a few are intrusive. We use only the first two kinds.

What cookies does ekovault.bond use?

This site sets the following:

• ekvault_sess — a PHP session cookie. Holds the anti-forgery token for the contact form so a third-party site cannot submit on your behalf. Expires when you close the browser. Strictly necessary; cannot be opted out of if you intend to use the form.
• ek_cc_v1 — a localStorage entry (not technically a cookie, but treated as one for transparency). Records your choice to accept or reject cookies so you’re not asked on every page load. Persists for twelve months or until you clear browser storage.

That’s the entire list. We do not run Google Analytics, Meta Pixel, hotjar, intercom, mouseflow, or any other third-party tracker on this site. No advertising cookies. No social-network sharing widgets that phone home in the background.

Why no analytics?

Honest answer: we don’t need the data. Our work comes from referrals and direct enquiries. A daily Google Search Console export is more than enough signal for the kind of decisions we make about this site. If that changes in future, we’ll add cookie-based analytics with a proper opt-in — never silently.

Changing your mind

The footer of every page has a "Cookie settings" link that reopens the consent banner. You can switch between accepting and rejecting at any time. Rejecting clears the localStorage entry on next page load.

You can also clear cookies and localStorage directly through your browser settings. The exact path differs by browser, but most browsers offer it under Settings → Privacy → "Clear browsing data" or similar.

Third-party content

This site embeds Google Fonts (Fraunces and Inter) over an HTTPS connection. Google may receive your IP address and User-Agent header as part of that font request. Google’s privacy documentation covers what they do with that information. If this concerns you, an ad-blocker or DNS-level blocker will neutralise that request without breaking the site noticeably.

Updates

Cookie inventory changes when we add tooling. Any change will update the “Last reviewed” date and re-prompt for consent if the addition is anything more than strictly necessary.

Contact

Questions about cookies can go to [email protected]. The broader Privacy Policy explains everything else.