subprocessors data sharing · Privacy Policy
tday.com policy finding
“ Google is an AI service recipient in the following separate processing paths: Live transcription: the hosted browser or Mac renderer sends 16 kHz PCM audio directly to Google over a live connection using a one-use, short-lived credential. The long-lived Google API key stays on the tday server. Speaker-attribution metadata is attached to returned transcript text locally and is not sent alongside that live PCM stream. Diarisation: a separate audio window is sent through tday to Google approximately every 10 seconds. Each request is limited to 30 seconds and 2 MiB. tday sends the audio inline in a request configured with store: false and does not create a Google File API object. Rolling notes: the hosted browser or Mac renderer automatically sends tday the meeting title, prior outline, and up to 200 recent final transcript segments, including timestamps and any applied speaker names. tday sends Google up to 40,000 transcript characters, speaker labels, the meeting title, and the prior outline to generate updated notes. This rolling window may be sent again as the transcript changes. The request settings described above do not state or guarantee Google's own logging, abuse-monitoring, data-residency, training, or retention practices.”
- Document
- Privacy Policy
- Captured
- 2026-09-25
- Location
- Privacy Policy › “Processing by tday and Google”
- Snapshot SHA-256
- 18244a2318b1c0210ee036a5ecaa367447d1339dee34c4c54ce116b84dffb2ed
Informational only, not legal advice. Terms change; verify the source and capture date.