Last updated 27 July 2026
Cookie Policy
What happens, and does not happen, on your device when you use vedfoundry.com.
1. The short answer
We set no cookies. Nothing this site runs stores an identifier on your device or recognises you on a later visit. There is no cookie banner on this site asking for your consent, because there is nothing here to consent to. We do count page views, without cookies, and section 3 says exactly how.
2. What a cookie is
A cookie is a small piece of text a website asks your browser to store and send back on later visits. Sites use cookies to remember who you are between page loads, to keep you signed in, or to build up a profile of what you look at across the web. Similar techniques, such as tracking pixels, fingerprinting scripts, and local storage used for tracking, aim at the same thing.
3. What actually happens when you load a page here
When you open a page on vedfoundry.com, your browser requests the HTML, the styling, our self-hosted fonts, and any images from our host, Netlify. Netlify records that request in a server log, the way any web server does: your IP address, your browser's user agent string, and the time of the request. That is a log entry, not a cookie. It sits on Netlify's infrastructure, and we do not use it to build a profile of you or to follow you across visits.
Your browser also talks to somewhere other than our host. It fetches a small analytics script from eu.i.posthog.com and posts page-view events back to it: which page you opened, the site that referred you, and the coarse technical details your browser sends to every site it visits, such as browser and operating system. PostHog counts those events on our behalf. It runs in cookieless mode, so it sets no cookie, writes nothing to your browser storage, and begins every page load with no memory of the one before. Any tracker blocker stops it, and this site works exactly the same without it.
Our privacy policy explains how the logs and the page-view events are handled, and names the countries they are processed in.
4. What happens when you submit an application
If you fill in and submit one of our application forms, your browser sends what you typed, plus the technical metadata of that one request, to Web3Forms, a third party form to email service. Web3Forms emails the submission on to us. It acts on our instructions for that single request; it is not a cookie or a tracker placed by this site.
Web3Forms may set cookies or use similar technology on its own infrastructure while it handles that request. That is governed by Web3Forms' own policies, not by this one, and it applies only at the moment you submit, not while you are otherwise reading this site.
| When | What is requested | Handled by | What is recorded |
|---|---|---|---|
| Loading any page | HTML, styling, self-hosted fonts, images | Netlify, our host | A server log entry: IP address, user agent, time |
| Loading any page | An analytics script, then page-view events posted back | PostHog, at eu.i.posthog.com | Which page, the referring site, browser and operating system. No cookie, no browser storage, no identifier kept between page loads |
| Submitting an application | What you type, plus the technical metadata of that request | Web3Forms, a third party form to email service | Forwarded to us by email. May also set its own cookies, under its own policies |
5. Browser storage
We do not use localStorage, sessionStorage, or IndexedDB, the browser's built in stores for data a website can keep on your device. We do not read from or write to any of them. Your browser may still cache the static files this site serves, so that a repeat visit loads faster. That is ordinary browser behaviour, controlled by your browser, not something we set or read.
6. If this changes
Cookieless page counting is already here, set out in section 3, and this page was rewritten to say so. If we ever add anything that stores an identifier on your device, or that would let anyone recognise you on a later visit, we will say so here first. We will update this page, bump the date at the top, and, where the law requires it, ask for your consent before that code runs, not after.
7. Controlling cookies anyway
Even though this site sets none, every major browser lets you view, block, and delete cookies from its settings or preferences menu. Turning that on, or clearing cookies entirely, has no effect on this site, since we never set one to begin with.
8. How to reach us
Questions about this policy: write to us at legal@vedfoundry.com.