Privacy

Chronicle uses Umami, a self-hosted analytics tool, to understand how the app is used. No third-party trackers are involved; the analytics data lives on the same infrastructure as Chronicle and never leaves the operator's control.

What's always collected

Public pages (this one, the landing page, sign-in, sign-up, password reset) record:

• Page views — pathname, referrer, time, approximate geography from your IP
• A daily-rotated session hash (IP + browser fingerprint), so a visitor isn't counted as a new person on every page view
• Sign-up and sign-in attempts as named events, with a "reason" property when something fails. Your email and password are never sent.

This data is anonymous in the GDPR sense — there's no stable identifier linking it back to an account.

What's collected only if you opt in

At sign-up (and any time in Settings) you can choose to allow analytics on the authenticated parts of the app. If you do, additionally:

• Page views on the dashboard, roster, adventures, feats, and settings pages.
• Your internal account ID (an opaque integer) is attached to those events so multi-session activity correlates rather than counting as new visitors each time.

Your email is never sent to the analytics tool. The internal ID is meaningless outside Chronicle. Turning the toggle off in Settings stops new identified events from being recorded.

How this data is useful

Anonymous data alone shows the visitor side — who's hitting which page — but can't tell whether the same person is coming back across sessions, which features actually get used after sign-up, or where existing users get stuck. Identified data answers those questions and informs what's worth building next. Concrete examples:

• Are GMs completing adventures, or abandoning them mid-session?
• Does the inline "+ New feat..." path get used, or do GMs always pick from the existing list?
• Do new sign-ups come back the next week?

Cookies

Umami is cookieless — it does not set any cookies. Chronicle itself sets two: chronicle_session for your sign-in, and chronicle_active_campaign remembering which campaign you last viewed. Neither is shared with the analytics tool.

Retention

The analytics data is kept for as long as the operator chooses to keep it; there is no fixed schedule. Account data (your characters, adventures, feats) is kept as long as your account exists.

Your rights

• Opt out of identified analytics at sign-up or in Settings. Anonymous public-page analytics keeps running either way.
• Request deletion of your account or your analytics data by emailing privacy@chronicle.balana.dev.
• Export your data — email privacy@chronicle.balana.dev.