Effective September 21, 2026
Privacy Policy
YouTube API Services
D.i.D uses YouTube API Services. Google describes its own data practices in the Google Privacy Policy. D.i.D currently accesses public, non-authorized YouTube data with a server-side API key; it does not ask users to authorize a Google account.
Data used for recorded-video scans
D.i.D retrieves the video title, channel title, publication timestamp, view count and reported comment count; and up to 500 recent public top-level comments. Retrieved comment fields can include comment ID, text, author channel ID or display name, publication timestamp, like count and reply count. View count and video publication time are fetched but are not currently placed in saved reports.
Raw samples are held server-side for about one minute. A report saved in the browser can include the video URL and ID, title, channel title, reported comment count, selected matching-comment text examples, scan time, sampling description and D.i.D-calculated measurements. Raw author IDs, raw comment IDs and individual raw timestamps are not placed in ordinary saved reports.
Data used for YouTube Live
Live observation can store the video ID and URL, title, channel title, stream start time, observation start time and public live-chat messages. Stored chat fields can include message ID, author channel ID and display name, message text, publication timestamp, reply reference and whether the text contains a link.
Live chat viewers receive anonymized account labels by default. Authorized developer accounts can view the public platform display names while testing D.i.D Live. A future Pro plan may offer the same display capability, but no Pro entitlement is currently active.
Twitch and other Live sources
Twitch observation uses Twitch OAuth with the user:read:chat scope. The access token, refresh token, granted scopes and expiration time are stored server-side in Cloudflare runtime KV so the connection can survive Worker restarts. The browser receives only an HttpOnly, short-lived OAuth state cookie; OAuth tokens are not included in browser-visible Live state. Pending authorization state expires after about ten minutes. Kick and X are shown as coming soon and their ingestion and authorization flows are not enabled.
Storage, refresh and deletion
Non-authorized YouTube API Data is retained for no longer than 30 calendar days unless it is refreshed from YouTube sooner. Recorded reports are saved only in the current browser session and expire no later than 30 days after collection. Live observation metadata, the recent message buffer and descriptive metrics are stored in a Cloudflare Durable Object for the observation. An inactive Live observation is deleted after six hours; activity and connected viewers postpone that cleanup. Any earlier 30-day YouTube-data expiry still applies. Expired reports require a fresh scan rather than presenting stale YouTube data.
Use Data controls to delete browser reports immediately. A live observation also includes a “Delete observation data” control that deletes its server-side record, including retained public chat messages and observation metadata. Deleting data does not delete the underlying public content from YouTube.
Cookies and browser storage
D.i.D uses necessary browser storage for OAuth security, privacy and cookie choices, saved reports and identifiers for Live observations created by this browser. D.i.D currently installs no analytics, advertising pixels or fingerprinting scripts. See the Cookie Policy and reopen Cookie settings from any page footer.
During the Free Beta, D.i.D assigns anonymous visitors a random opaque identifier in a strictly necessary, HttpOnly first-party cookie. The identifier is not a browser fingerprint and does not contain an IP address. A Cloudflare Durable Object uses it to enforce daily scan and Live-minute allowances atomically. Usage records contain the UTC day, consumed scan count, consumed Live seconds and short-lived scan reservations; they do not contain submitted video URLs, comments or chat messages. Daily counters reset after midnight UTC. The identifier cookie can remain for up to one year unless you clear it sooner.
Service providers and platform APIs
Cloudflare provides hosting, Worker execution, KV and Durable Object storage and may process request metadata under its own terms. D.i.D sends API requests to YouTube and Twitch when you use their related features, and embedded players connect your browser to the selected platform. Those services process data under their own policies. D.i.D does not sell or share submitted waitlist information for advertising.
D.i.D-calculated measurements
Engagement-risk scores, repetition, timing, vocabulary, reply-depth, link and confidence measurements are calculated by D.i.D from sampled API Data; they are not YouTube-provided metrics. The additional YouTube derived-metrics policy effective in 2026 requires compliance review and, for covered analytics uses, acceptance through the audit process. D.i.D does not represent that Google or YouTube has approved additional derived metrics or extended statistical-data retention.
Google-authorized data
D.i.D does not currently request Google user authorization or store Authorized YouTube Data. If that changes, this policy and the consent flow must be updated, revocation must be supported through Google security settings, and associated authorized data must be deleted when access is revoked or cannot be refreshed.
Developer test accounts
The isolated developer environment collects an invited customer's email address, a salted password hash, an internal account identifier, role, account creation time, and hashed session identifiers. These records are stored in a separate Cloudflare D1 database to authenticate the account and apply access entitlements. Raw passwords and raw session tokens are not stored in that database. Authenticated accounts in the isolated private developer environment currently receive unlimited review usage; this does not change public Free Beta limits.
Signed-in customers can delete their account and account sessions from the account page. No automatic retention period is currently configured; the owner must approve one before a public account launch.
Customer accounts
When public customer registration is enabled, D.i.D stores the submitted email, salted password hash, internal account identifier, verification status, role, account timestamps, hashed session identifiers, and hashed single-use verification or password-reset tokens in a private Cloudflare D1 database. D.i.D uses this data to authenticate the account, secure account recovery, and apply the Free Beta daily allowance. Raw passwords and raw session tokens are not stored in the database.
Verification and password-reset messages are sent only to complete the requested account action. Password reset revokes existing sessions. A signed-in customer can revoke every session or delete the account and its account sessions from the account page. Transactional email delivery is configured for account verification and password reset. An inactive-account retention schedule still requires owner and legal review.
Pro waitlist
If you join the Pro waitlist, D.i.D collects the email address you submit and your optional response about how you would use Pro. The information is stored in the private Cloudflare KV namespace dedicated to the waitlist and is used to manage the waitlist and related product updates. It is not shared for advertising, and no email-marketing provider or tracker is connected.
No automatic waitlist retention period is currently configured. To delete a submission, enter the same email in the waitlist form; an existing submission produces a removal control. You may also request deletion or correction at orion@chatisthisreal.io. The owner should set and document a retention schedule before launch.
Contact and policy ownership
Contact orion@chatisthisreal.io about privacy, access, correction or deletion. The operating legal entity and postal address remain to be supplied by the owner before final legal approval.