What we record, and what you can turn off
Last updated · 2026-04-25
The short version
We use three external analytics services to learn how prepi.sh is used so we can make it better. None of them receive the contents of your worldbuilding — only metadata about which parts of the product you interact with and how the interface performs.
The tools we use
- Microsoft Clarity
- Heatmaps and session replays. Loads on both marketing and authenticated pages. Form fields and elements marked sensitive are masked by default. Disabled if you opt out from your account settings.
- Mixpanel
- Activation-funnel and feature-adoption events tied to your user id while you are signed in. We send a small set of named events (e.g. project_created, first_wiki_page_created) with non-sensitive metadata such as project ids and roles. Never loaded on public marketing pages.
- Google Analytics 4
- Aggregate marketing-page traffic. Loads only on public pages, only after you accept analytics in the cookie banner. Never runs inside the authenticated workspace.
Your controls
- Cookie banner — strict opt-in on public pages. We default to denied; Global Privacy Control and Do Not Track are honored.
- Per-user opt-out — a single toggle in your account privacy settings disables Clarity replays and Mixpanel events tied to your user id.
- Data deletion — email privacy@prepi.sh and we’ll remove your account and associated analytics records.
What we never send
The bodies of wiki pages, outline nodes, whiteboard documents, comments, dialogues, and uploaded files are never transmitted to analytics providers. Server-side events carry only the minimum metadata required to understand product flow.