What we measure — and what we don't
Wovenkeep is in an invite-only beta. The whole point of a beta is learning: which features help you run your games, and which just sit there. To learn that, we collect some usage data. This page explains — in plain language — exactly what we measure, what we deliberately don't, and how you stay in control.
The short version: we count how the tool is used, we never read what you create.
What we measure
| We measure | We do NOT measure |
|---|---|
| Page views and which GM tabs you use (e.g. "NPC tab opened") | Your campaign content: texts, notes, names, images, chat — never |
| Session duration and rough activity time | Session replays or screen recordings — we don't have any |
| Product events tied to your account: login, play session started/resumed/ended, campaign created or duplicated, NPC created, export used, AI feature used, voice interview started/completed, voice dictation used, first-time milestones | Heatmaps — none |
| Browser, operating system, interface language | Individual clicks — not unless you explicitly opt in (off by default) |
| Approximate location (country/region/city), derived from the IP address, which is then immediately discarded | Anything on your players' pages — no analytics script runs there |
| Errors: category and page type only (e.g. "save failed on the campaign page") | Your players' names, accounts, devices or locations |
| Connected players as plain numbers: how many players and devices joined a session, and a rough duration bracket | Persistent user IDs inside analytics events |
Why we measure this
With a small group of beta testers, every data point is really a person telling us something. We use this data to answer questions like: Do GMs find the NPC tools? Does anyone use the export? Where do errors pile up? Which features can we cut? That's it. The data is:
- evaluated internally only — a small internal dashboard, seen by the two people running the beta;
- never merged with marketing data, never sold, never shared with ad networks;
- minimal by design — every event we collect must answer a concrete product question, or it gets removed.
Your players
Your players are guests, not test subjects. Player pages contain no analytics script at all. Server-side, we only count how many players and devices were in a session and roughly how long — no names, no identifiers, no locations. Players see a short privacy notice on the join page before they join. Invitations happen by you sharing a link; the platform never e-mails your players.
Your control
- Opt out of base telemetry: one toggle in your GM settings switches off both the usage statistics and the product events for your entire instance. Beta participation does not depend on it (your data just helps us less).
- Ad blockers win: our analytics uses the normal, blockable script path. If your blocker blocks it, we accept that as your answer — no circumvention, no server-side fingerprinting fallback.
- Do Not Track / Global Privacy Control: respected.
- Click statistics are opt-in only: granular click events (which buttons you use) are off by default and only ever collected if you switch them on yourself. You can switch them off again at any time.
Where the data lives
Everything runs self-hosted on our own servers in Germany and the EU (IONOS data centers, Germany/France) — including our analytics tool (Umami, cookie-less, no third-party analytics service involved). Retention is short: anonymized raw telemetry 30 days, account-related product events 180 days (events of deleted accounts are removed after 30 days), GM-view web analytics data up to 12 months.
Questions?
Data controller: Adrian Bätz – Hebepunkt (sole proprietorship), Elbinger Str. 9, 91207 Lauf a. d. Pegnitz, Germany — [tax ID to follow]. Privacy contact: info@wovenkeep.com. Full legal details: Privacy Policy.