Privacy & participation
Updated 3 October 2026
About Press Floor
Press Floor is an independent public discussion forum, not a government service. Reading public sources and discussions does not create an account.
Google account and forum identity
Participation uses Google sign-in or an explicitly chosen guest name. Better Auth manages a necessary secure browser cookie and a session lasting up to seven days. Signing out revokes that session. A returning Google account uses the same chosen forum name and code-generated avatar. Signing in is not proof of a unique human.
Earlier guest records are retained. Retired guest cookies do not authorise production participation; new guest access uses a separate secure cookie for up to seven days and guest records are not automatically linked to Google accounts.
Google sign-in
When configured by the operator, Google sign-in identifies an account for participation. The only requested permissions are openid, email and profile: a Google account identifier, email address and basic profile information. They do not grant access to Gmail messages, Google Drive files or contacts.
We store your Google account identifier, email address, basic profile name and any supplied profile image URL privately, together with authentication accounts and sessions. Google profile images are not displayed. Google access, refresh and identity tokens are not retained after sign-in. Session records can include an IP address and browser user agent. Public contributions use the separate forum identity, never the email or Google account identifier.
Contributions and moderation
New contributions are private to their author and moderators until the display name and text pass review. TypeSafe AI (Jev) provides the first review; uncertain decisions and service failures keep submissions private for moderator attention. We send the chosen nickname, contribution text and contribution type to TypeSafe AI, without Google profile or email. Approval does not verify facts. Do not submit sensitive or confidential information. Public contributions can be copied by other readers.
Data, cookies and service providers
We store authentication records, forum and earlier guest identifiers, contribution text, moderation decisions and operational records using Cloudflare. Technical request information may be processed by Cloudflare for service delivery and abuse protection. We do not run advertising trackers.
When you first register with Google, we send a welcome email to the verified email address supplied by Google. Cloudflare Email Service processes the recipient address and a message that can include your Google profile name. We retain a private sending record to avoid repeated welcome emails. The welcome message contains no tracking images and does not subscribe you to a marketing list.
The session cookie is necessary for signed-in access. Drafts can be kept in this browser’s session storage. Pixel fonts load from Google Fonts, which receives the font request. Google handles authentication when configured. Guests can still participate when Google sign-in is unavailable. Clearing or losing a guest cookie loses access to private guest submissions; signing in later does not link them to the Google account.
Removal and retention limits
Moderators can remove contributions from public view. That action is not a promise of immediate erasure from operational records or backups. Authentication sessions expire after seven days; expiry does not erase account or contribution records. Account records are retained while the account exists; contribution and moderation records remain until the operator removes them. There is currently no automatic deletion schedule.
To request a correction or removal, follow the Contact page. Include the public link and the requested action. Keep account details and private documents out of the message.
Translations
Content translations are provided for convenience and may contain errors or omissions. The original remains available. Please refer to the original text.