Privacy
Your data at AI Daywire.
Responsible operator
Aleks Paramonov Grandweg 162 22529 Hamburg Deutschland
Reading and hosting
Briefings and public discussions require no account. Hosting is provided by OpenAI Sites and its infrastructure providers, including Cloudflare. They process connection and security information such as IP addresses, request times and technical headers to deliver the service. Processing can involve countries outside the EEA under the provider’s applicable contractual safeguards. OpenAI privacy information. We do not add advertising trackers, tracking pixels or third-party embeds. Theme preferences are stored locally in your browser.
Posts, votes and comments
ChatGPT handles sign-in for posts and votes. The site receives an account identifier, email and available display name. Email is not displayed in community posts. Posts store the account identifier, your chosen public name, text, attachment and moderation status. Votes store a post-specific hash of the account identifier and the current vote; individual votes are not public.
Comments require only a chosen name and text. These appear immediately and are reviewed afterward; names are unverified. Comments are not attached to your ChatGPT account. A private removal code lets you withdraw your comment; we store its hash, not the code. Do not share that code. Moderation reports store the reported content reference and your explanation. Please avoid unnecessary personal information.
AI agents process submissions and comments for moderation. An automated assessment is not proof of legality, consent or ownership. Unclear or reported material can be hidden for further review. Contact the operator to challenge a decision or request removal. Public posts and comments remain while useful or until removed. Rejected or withdrawn posts and media are deleted after 30 days by maintenance; abandoned uploads after 24 hours. Rejected comments are deleted after 30 days; resolved reports after 90 days. Necessary handling of a specific legal dispute may require separate retention.
Community popularity and abuse prevention
The community has public read and vote counts, including its separate 18+ discussion area. These counters are separate from optional audience analytics. A detail page can record a read after it has been visible for at least eight seconds. We limit repeated reads using a post-specific, daily rotating hash derived from the network address and a private server secret. Those temporary keys expire within 48 hours. They do not form an account-linked viewing history; raw network addresses are not stored in these counters. Shared networks, bots and blockers can affect the estimates. Counts are not unique people.
Daily totals per post are retained for up to 400 days. Short-lived hashed network and account counters also limit comments, reports, votes and uploads. These measures use no advertising identifiers, cross-site cookies or device fingerprinting. Hosting providers still process network requests as described above.
Optional audience analytics
Optional measurement starts only after “Allow analytics”. Declining does not restrict participation. Change your choice using Privacy settings in the footer. We respect Do Not Track and Global Privacy Control. This analytics system excludes owner activity, account pages, APIs and the entire 18+ area; community ranking counters are separately described above.
After consent, the browser sends a random page ID and tab ID, an allowlisted general page path, a coarse referral group, active seconds and whether a source or feed link was clicked. We store the daily hash of the tab ID, consent version and time. No IP address, full referrer, query, account or email is stored in audience analytics. The consent choice lasts 180 days; tab identifiers use session storage and are cleared on withdrawal or entry to 18+. Raw measurement records expire after 90 days and aggregate monthly reports after 400 days. The owner’s monthly report uses aggregates. These measurements cover only participating browsers and cannot measure all readers or AI agents.
Purposes, legal bases and your rights
Requested account and contribution functions rely on Article 6(1)(b) GDPR. Moderation, limited first-party popularity counts and abuse prevention rely on legitimate interests under Article 6(1)(f), subject to your rights. Optional analytics relies on consent under Article 6(1)(a) and §25(1) TDDDG for optional browser storage/access. You may withdraw consent, object to legitimate-interest processing, and request access, correction, erasure, restriction or portability where applicable. You may complain to a competent data-protection supervisory authority, including the Hamburg Commissioner for Data Protection and Freedom of Information. Contact the operator using the address above.
No newsletter or newsletter registration is offered. Last updated: 5 September 2026.