TaleTrellis · Privacy
Privacy Notice
TaleTrellis uses an optional, first-party visitor report to understand how readers reach registration and where the journey stops. This report is off until you explicitly allow it.
What the visitor report records
- A random pseudonymous session reference, started only after consent.
- Allowlisted page categories without page slugs, query strings, fragments, or full URLs.
- Broad entry source categories (direct, search, social, or referral) and device class.
- Signup started, completed, blocked, and safe error-code events.
- Estimated active seconds while this tab is visible and recently used, and maximum page scroll depth.
What it excludes
The visitor report does not store names, email addresses, passwords, form contents, uploaded file contents or identifiers, payment details, credentials, tokens, account IDs, raw error messages, API payloads, full URLs, IP addresses, or raw referrer URLs. Admin pages, known bots, local development, and browser automation are excluded.
Consent and retention
Your granted or declined choice is remembered in a first-party cookie for up to one year. You can change it at any time below.
Declining means the TaleTrellis visitor report stores no analytics events. You can withdraw consent below at any time; new report events stop immediately. Events collected before withdrawal remain pseudonymous and are removed at the retention cutoff.
Current raw-event retention: Loading the current setting…
Platform telemetry
The hosting platform can separately enable a page-load beacon that uses a random browser identifier and counts loads. If its PostHog collector is enabled, it records page views, pseudonymous visitor and session identifiers, the raw browser user-agent string, browser, operating-system and device details, language, screen and viewport dimensions, timezone offset, scrubbed page and referrer URLs, page-view duration, and the standard UTM source, medium, campaign, content and term fields. It does not use autocapture or session replay. These platform collectors are controlled by deployment settings, not by the choice below. Their retention period is not exposed to this app and is not covered by the raw-event retention setting above; the deployment owner must confirm it. Contact the site operator for details about platform-level telemetry.
Loading your current choice…