Beetl uses essential authentication, security, short-lived visitor binding, requested service and cookie-choice storage. Account sessions expire after seven days under current settings. The essential visitor identifier has a rolling 30-minute lifetime. Signup age-attestation storage expires after 30 minutes. Cookie choices last 180 days and are per browser and host. Actual cookie names, host/domain, duration and service purpose must be inventoried and checked in the deployed browser before publication; these functional descriptions are not a completed browser-cookie inventory.

Optional article views and search interaction analytics require an affirmative current-version choice. No choice or rejection disables that optional collection; changing preference stops subsequent collection. Search analytics may contain a normalised query and hashed/pseudonymous identifiers: normalisation is not anonymisation. Submitted feedback/questions, assessments and enrolled learning progress are requested service records, not optional browsing analytics. Optional tracking consent is separate from contract acceptance and must be as easy to withdraw as give.

No session replay SDK or promotional campaign sending is approved for launch. Marketing requires a separately approved permission/suppression/unsubscribe process and market-specific review. A service reply must not be repurposed as an advertising campaign. New tracking or changed purposes require privacy/cookie review before deployment.