Wellseen
The short version
The short answer is that this website does not use cookies. This page explains what that means, the one flag your browser does keep, and what happens when you follow a link to Stripe, Calendly or one of our social accounts.
- Cookies this site sets
- None. There is no banner because there is nothing to ask you.
- The one thing stored
- A single flag remembering you closed the premed prompt. Nothing else.
- Tracking
- No analytics, no pixels, no session recording, no cross-site tracking.
- Third parties on our pages
- None embedded. Stripe, Calendly and beehiiv are links out.
- One caveat
- Google Fonts sees your IP address when a page loads. Explained below.
This site does not use cookies
wellseenmcat.com sets no cookies at all. Not essential ones, not analytics ones, not advertising ones. That is why you have never seen a cookie banner here, and why there is nothing for you to accept or reject.
A cookie is a small file a website asks your browser to keep, so that it can recognise the same browser later. Most sites use them for logging in, for measuring traffic, and for advertising. This one is a set of static pages: there is nothing to log in to and nothing being measured about you personally, so there is nothing to store.
One thing your browser does keep, and it is not a cookie: if you close the small
premed prompt in the corner, we store a single flag, ws-nudge-closed, in
your browser's own storage so the prompt does not come back at you next time. It
records that you closed something. It does not record who you are, it never leaves
your browser, and clearing your site data removes it.
Beyond that we do not use the things that get used instead of cookies: no fingerprinting scripts, no tracking pixels, no session recording. You can check: open your browser's developer tools on any page of this site and look at the storage tab. That one flag is all that is ever in it.
What happens when you leave the site
In short: the moment you click through to Stripe, Calendly or one of our social accounts, you are on their site under their rules, and they will almost certainly set cookies.
Apart from our host's visit counter, described below, everything on this site that involves another company is a plain link out, not an embedded frame or widget. Nothing else loads outside code onto our pages, so nothing of theirs runs while you are here. Once you follow one of those links, though, their cookie policy applies and not ours:
| Where you land | Why you would go there | Their policy |
|---|---|---|
| Stripe | Paying for the programme | stripe.com |
| Calendly | Booking the discovery call | calendly.com |
| beehiiv | Subscribing to the newsletter | beehiiv.com |
| TikTok, Instagram, YouTube, Facebook | Our social accounts | Each platform's own policy |
One thing that is not a cookie
This site is set in Plus Jakarta Sans, which it loads from Google Fonts. That does not place a cookie, but it does mean Google's servers see your IP address and which page requested the font whenever a page loads. Google states that it does not use Google Fonts requests to build advertising profiles.
We think you should know about it anyway, because from your side of the screen a third party learning your IP address is the same kind of fact as a cookie, whatever the technology is called. If you would rather that did not happen, a content blocker will stop it and the site will fall back to the closest font on your own machine.
We are looking at serving the font from our own domain, which would end the request to Google entirely.
Visit counting
We count visits with Vercel Web Analytics, which is built into our host. It does not set a cookie and does not write anything to your browser's storage. To tell one visit from another it uses a code made from the incoming request, which is thrown away after 24 hours, so it cannot follow you from one day to the next or onto other websites.
For each page view it records the page, the referring page, your approximate location, your browser, operating system and device type, and the time. We only ever see these as totals, such as how many people read a given page. Nothing in it is tied to your name, your email or your IP address.
Server logs
Our host, Vercel, keeps ordinary server logs for every request: the IP address, the page asked for, the referring page, the browser and device type, and the time. This is how any web server works and it is not done with cookies. We use these logs to keep the site running and to spot abuse, and they are deleted within 30 days.
How to control cookies anyway
There is nothing here to switch off, but if you want to manage cookies across the whole web, every browser lets you:
- Chrome · Settings → Privacy and security → Third-party cookies
- Safari · Settings → Privacy → Block all cookies
- Firefox · Settings → Privacy & Security → Enhanced Tracking Protection
- Edge · Settings → Cookies and site permissions
Blocking cookies globally will break sites that need them to log you in. It will not affect this one.
If this changes
If we ever add something that sets a cookie, whether analytics, a chat widget or an embedded video, we will update this page before it goes live, and where the law requires consent we will ask for it properly, with a real reject option rather than a dark pattern.
Questions: [email protected]. See also our privacy policy, which covers everything we do with information about you.