Draft notice · Updated November 13, 2026
Your information. Your choices.
This notice describes the current implementation. Operator identity, a privacy contact, jurisdiction-specific rights, and precise retention periods still require completion before public launch.
What the app stores
Accounts store a name, email address, verification status, securely managed credentials, and sessions. Reader features store saved stories, preferences, and reading history when enabled. Notification settings record consent and withdrawal. Authorized publishing tools store uploaded clips, rights information, and operational audit records.
The lounge stores your chosen display name, introduction, recognition choice, latest topic suggestion, submission time, and host approval status in your account preferences. A name used to greet you privately is not automatically published.
Article comments and advertising inquiries
Comments store an account identifier, chosen public display name, article reference, text, timestamps, and moderation status. The name and text become public only after approval. Editing a comment returns it to review. Authors can remove their own comments; deactivation hides them and account deletion removes them. Moderation audit records retain identifiers and status changes, not a copy of the comment text.
Advertising inquiries store your name, business, email, preferred placement, message, and contact consent for administrator follow-up. They are not published or added to a marketing list. Sponsor campaigns store the creative, destination, schedule, and authorizing staff identifier. A finalized inquiry retention period and privacy contact still need to be established by the operator.
Who can see a submission
Authorized staff can review introductions and topic suggestions. The public lounge displays only the chosen display name and introduction after explicit recognition consent and host approval. Payment status, email, topic suggestions, reading activity, and attendance are not included in that public display.
Saving a changed submission removes its publication approval. Turning recognition off or removing your submission removes it from future lounge responses. Copies, screenshots, search caches, and pages someone already opened cannot be recalled.
Manage your lounge submissionCookies and providers
Essential authentication cookies maintain sign-in. Vercel hosts the app; Neon stores application records; Redis supports rate limiting and real-time delivery; Vercel Blob stores uploaded media. These providers process data to run their services. External publisher and Clubhouse links lead to services with their own policies.
Direct sponsor placements count approximate daily impressions and clicks without attaching account identifiers or storing visitor-level browsing histories. The app skips these counters when the browser sends Do Not Track or Global Privacy Control. Briefly retained hashed network identifiers enforce rate limits. Approved sponsor images may load from an external image host, which receives the network request; outgoing sponsor links lead to sites with their own policies. No third-party advertising network is installed.
Your available controls
You can manage reading history and preferences, revoke sessions, change your password, deactivate your account, or request account deletion through the signed-in account controls. A staff account must have its staff grant removed by an authorized administrator before closure.
Deleting an account removes its profile, credentials, sessions, private reading data, preferences—including lounge submissions—and inbox. Uploaded media is removed from the app and queued for storage deletion after upload links expire. Failed storage deletion requires successful background retries. Audit records retain a pseudonymous identifier; backups and provider logs require a finalized operator retention policy.
Account controlsReader preferencesImportant limits
No system can guarantee absolute security. Avoid entering sensitive personal information or information about someone else without permission. This service is not designed for children, and the operator must establish and enforce its applicable age rules before public launch.
An official privacy request and complaint channel is not yet published. Do not use a discussion suggestion for confidential privacy requests. This is a launch-readiness gap, not a waiver of your legal rights.
Current disclosures and launch requirements