Privacy Policy

We built this school on a simple rule: your inner life is yours. We collect only what the site actually needs to function, we tell you exactly what that is, and we never sell it. Most of the site needs no account at all — the corpus, the School and the instruments are readable without one. This page is the complete inventory — not a summary, the actual list.

• —No analytics pixels, no fingerprinting, and no advertising trackers beyond the two conversion tags (X pixel and Google Ads tag) described above
• —No member posts, comments, direct messages, circle chat, or private conversations — this site has no member-content layer, so there is nothing for us to hold
• —No follower graphs, social popularity metrics, or reading history
• —No precise location data (IP-derived country at most, via infrastructure logs)
• —No assessment of authorship — AI-assisted work is never scored or demoted
• —No sale or rental of your data to anyone, ever

To run the account surfaces that need one: sign-in and approval, the petal assessment and the archetype you set on it, the library, the admin surface, and the safety of the door (rate limits and anti-abuse counters). Your data is never used for third-party advertising or sold to data brokers. There are no behavioural advertising trackers on this site.

The platform runs on self-hosted infrastructure (Hetzner), fronted by Cloudflare for TLS and DDoS protection. Authentication is self-hosted Authentik. Operational secrets are held in Proton Pass. No third-party analytics or marketing processors. Where you connect your X (Twitter) account, X's own privacy policy governs X's side of that connection.

Almost everything on this site is published by the house, so there is no user-generated content and no moderation queue to keep. Whatis here can still be wrong. If you find a claim that does not hold, write to us and a human reads it. Corrections and withdrawals are recorded publicly in the Register of Refutations, with the reason attached — the same append-only rule the rest of the corpus is held to.

We run exactly two advertising tools, both for measurement only.

X (Twitter) conversion pixel (ID rd0uh): it tells us which X ads lead to real readers and account-holders. It does not target ads at you anywhere, and we never sell the data. What it sees: page loads, and — if you arrived from an X ad — the click identifier twclid. When a real conversion happens (sign-up, approval, assessment), our server sends X the event with a SHA-256-hashed email and coarse request metadata. Hashing is one-way; X receives no plain email from us.

Google Ads conversion tag (Google tag, ID AW-1065803635): it tells us which Google ads lead to readers and account-holders. What it sees: page loads, and — if you arrived from a Google ad — the click identifier gclid. Outside the EEA, UK, and Switzerland it sets one first-party cookie google_gcl_au (conversion linking). For visitors from the EEA, UK, and Switzerland, Google Consent Mode denies all ad storage by default — no Google ad cookie is set for you, and conversions are measured cookielessly. Neither tag profiles your reading or feeds any recommendation system here. These are governed by X's and Google's privacy policies, and standard tools (ad blockers, Google Ads Settings, X's ad settings) opt you out. Both are disclosed here because you deserve to know exactly what runs — nothing else on this site tracks you.

Contact hello@hearthandcode.dev for any of the following, and we will respond:

• ✦Access — a copy of everything we hold about you
• ✦Correction — fix anything inaccurate (your archetype is editable; anything else, write to us)
• ✦Deletion — remove your account and the assessment attached to it
• ✦Export — your account details and assessment answers in portable form
• ✦Contest — challenge a published claim; a human reviews, and the outcome is recorded in the Register of Refutations

For EEA, UK, and Swiss visitors: no tracking cookies at all. Elsewhere, the Google tag sets one first-party cookie (google_gcl_au) solely to link your ad click to your visit; X's pixel sets none on its own. We use your browser's localStorage for exactly three things: your sign-in tokens, your petal-quiz progress, and a version marker that clears stale sessions. Clearing any of it is safe and signs you out at most.

This school is not directed at children under 16. If you believe a child under 16 has given us data, contact us and we will remove it.

If this policy changes, this page changes with it — and the date above is updated. Material changes are also recorded in the Register of Refutations.

Hearth & Code · hello@hearthandcode.dev · https://hearthandcode.dev