Cookie Policy

What we use

We use one analytics tool, PostHog. No analytics is set on your device until you explicitly accept the cookie banner. If you decline, the one thing stored is the record of your decline — the consent entry described below — so that we respect your answer and do not ask you again.

A decline lasts as long as an acceptance would: the banner does not re-appear, and we do not ask you again.

The analytics follows what an individual browser does on this site across visits, including what you click, where your mouse moves, and a replay of the visit we can watch back. That is why it only ever runs with your consent. Our Privacy Policy lists everything it records.

We do not use advertising cookies, tracking pixels, or any third-party embeds beyond PostHog.

PostHog is based in the United States. See our Privacy Policy for the cross-border transfer basis (EU Standard Contractual Clauses Module 2 for EU visitors; the UK Addendum to those same clauses for UK visitors).

Cookies and storage we use

stellerj-cookie-consent — a localStorage entry (not a cookie) that records your consent choice. Its value is either 'accepted' or 'declined'. localStorage entries do not have an automatic expiry; this entry persists until you clear it manually or clear your browser's site data for stellerj.com. Clearing it treats you as a new visitor with no recorded consent.

ph_*_posthog — the primary persistent entry set by PostHog after consent. PostHog's default persistence mode is "localStorage+cookie", so it stores the same session and device identifiers twice: in a cookie of this name and in a localStorage entry of the same name. The cookie expires 365 days after it is set, which is PostHog's default; the localStorage entry has no automatic expiry and persists until it is cleared. Some other ph_* entries are session-scoped and clear when you close the browser.

The asterisk in ph_*_posthog stands for this site's public PostHog project key, so the literal cookie name you will see in your browser's devtools on stellerj.com is ph_phc_ruaMMhwXz2uVFG5Z9KBZewWtb6cgAcZXkjJsxaAvAnbB_posthog. The long string in the middle is a public project identifier shipped in our client-side JavaScript.

These entries store anonymous session and device identifiers. They do not contain your name, email, or any other directly identifying information about you.

Immediately after you accept the cookie banner, we send a single PostHog event named cookie_consent_accepted so we can measure how many visitors accept analytics. Like every analytics event, it carries the anonymous session identifier above along with the page address, how you arrived, and basic device details.

How to withdraw consent

The fastest way to withdraw consent is the button below. One click sets your consent record to "declined", removes the analytics identifiers PostHog kept in both cookies and localStorage, and stops further collection immediately.

Two things are deliberately left on your device afterwards: the record of your "no", and a marker PostHog writes to remember that you opted out. Both exist to keep analytics off — deleting them is what would let it start again.

Withdrawing consent does not automatically delete data already collected by PostHog before you withdrew. You have the right to request erasure of that data under Article 17 of the UK GDPR and EU GDPR. Email legal@stellerj.com — we will respond within the time limits Article 12(3) sets.

If you prefer to do it yourself, clearing all site data for stellerj.com is the manual equivalent. On desktop, use your browser's site settings or Developer Tools to clear cookies and site data for stellerj.com; on mobile, clear cookies and site data for stellerj.com from your browser's privacy settings. This also removes the consent record itself, so the banner will appear again on your next visit.