DATA & CONSENT
What this browser shares.
Dreadtok uses one required consent for the profile cookies and research signals that make the feed, comparisons, and live algorithm work.
Profile and first-party signals
After you provide a nickname and consent, Dreadtok sets one Secure, HttpOnly, SameSite=Lax cookie named __Host-dtok_session. It expires after 180 days. The server stores only a hash of its random token.
The profile connects your nickname to feed impressions, playback, progress, completion, skips, reactions, comments, shares, downloads, pairwise comparisons, and recommendation history. Comments and nicknames are visible to other participants.
Required Bread analytics
After you accept the unified consent, Dreadtok loads Bread standalone v0004 from files.bread.net.ai with behavioral, WebMCP, and session-replay capture. That can include page context, clicks, scrolling, key activity, browser metadata, and a replay of the page session sent to ingest.bread.net.ai.
This collection is part of Dreadtok's required research instrumentation rather than a separate preference. The interactive application does not operate without that consent.
Public dashboard
The dashboard requires the same profile cookie as the rest of Dreadtok. It publishes aggregate artifact and interaction totals, not raw viewer identities.
Your controls
If you do not agree, do not enter the application. Clear Dreadtok site data in your browser to remove the local session cookie; using the application again requires accepting the unified consent again.