subprocessors data sharing · Privacy Policy
tday.com policy finding
“ Model-usage records keep the associated actor or user, model and provider, operation and category, token counts, cost, and timestamps. They do not contain the prompt, transcript, or generated note content. The hosted tday application also loads PostHog, Databuddy, Vercel Speed Insights, and Cloudflare Web Analytics on Meeting Assistant routes when those services are enabled for the deployment. They may receive standard technical and usage metadata, such as network and browser details, route or occurrence references, navigation, interactions, element attributes, performance measurements, and errors. PostHog session replay is enabled. tday marks the standup workspace for PostHog content masking, sanitizes Meeting Assistant pageview and exception locations, and omits standup-review API requests from PostHog network capture. These controls do not mean that every analytics provider receives identical fields or applies the same retention practices. When configured in a deployed build, Sentry receives client error reports and structured client logs through a first-party tday endpoint. Its error-triggered session replay is sampled for every captured error, with all text masked and all media blocked. Idle sessions are not sampled for replay, and default PII transmission is disabled. These controls do not prevent an error report or masked replay from carrying other technical context permitted by the Sentry configuration. The embedded Mac Chromium renderer loads the same hosted routes as a browser. ”
- Document
- Privacy Policy
- Captured
- 2026-09-25
- Location
- Privacy Policy › “Usage Metadata and Operational Logs”
- Snapshot SHA-256
- 18244a2318b1c0210ee036a5ecaa367447d1339dee34c4c54ce116b84dffb2ed
Informational only, not legal advice. Terms change; verify the source and capture date.