data retention · Privacy Policy

tday.com policy finding

“Ordinary Chromium cache, site storage, permissions, and other profile state may therefore remain in local application data after the app closes. The app does not currently run a general profile or cache erasure during sign-out. This profile is separate from the encrypted Better Auth file and approval proof described above. Desktop approval security records are also kept on the tday server. They include the target and approving user and session references, hashes of the approval code and device nonce, the scheduled expiry, approval, consumption, denial, and revocation timestamps, and creation and update times. The raw approval code and device nonce are not stored in that database record. Expiry is derived from the scheduled expiry when the record is read and does not itself write a separate expiry timestamp or update the row. Approval, consumption, denial, and revocation update the applicable lifecycle timestamps. These records are not automatically deleted merely because the approval expires. Each successful desktop approval action also attempts to create a separate administrative audit row. It can include the acting administrator, action, target session reference, approval reference, browser session or scheduled expiry details when applicable, client IP address, and creation time. An audit-write failure does not block the approval action. These administrative audit rows have no automatic deletion period in the current system. ”

Document

Privacy Policy

Captured

2026-09-25

Location

Privacy Policy › “Browser and Mac Audio Capture”

Snapshot SHA-256

18244a2318b1c0210ee036a5ecaa367447d1339dee34c4c54ce116b84dffb2ed

Informational only, not legal advice. Terms change; verify the source and capture date.