Club Spite Privacy — Updated October 9, 2026
Full policy: https://clubspite.com/privacy

Browser extension drafts
The Club Spite extension reads the current website’s domain only when you open it. Including it is optional. It does not collect browsing history, screenshots or full page addresses. Draft text and choices stay locally on your device, without cloud sync; ordinary drafts expire after 24 hours and are removed when reopened, or with Clear draft. Sending submits directly to Club Spite for private review using the same rules as the website. Network access is limited to Club Spite; Chrome and Edge use your protected website cookies to confirm X credit if selected. Firefox and Safari use a random local installation key and a short-lived connection request. After connecting X on our website, you explicitly confirm credit for that extension; an encrypted identity confirmation is then stored locally for up to 24 hours, separately from website cookies. This is not an X access token. Connection requests expire after 10 minutes. Connecting X opens its authorization page, then returns to a connection result page; draft text is not included in the authorization URL. A private retry key and pending text stay on your device until submission is confirmed, so retries can recover the same receipt without adding another story. Confirmation saves a private status link locally for 30 days, removed on the next opening or when you start another story. Anyone with that link can check status. The server stores receipt hashes and a private request fingerprint, not the receipt secret or raw retry key. Older extension versions may open a filled-in website form using a URL fragment; the browser may retain that older review address in local history.

Website analytics
We use Google Analytics to understand visits to our public homepage, rules and privacy pages, including referral sources and clicks on our X links. Google Analytics uses cookies and processes technical information about your browser and activity. We disable advertising personalization and Google signals. We do not send story text, account details or private admin page views to Analytics. You can block analytics cookies or requests through your browser settings or privacy tools.

Browsing and service data
You can browse public pages without an account. Our hosting and authentication providers may process technical information such as your IP address, browser information and security logs to deliver and protect the service.

Signing in
Clerk handles account authentication and essential session cookies. If you choose Google sign-in, Google shares your account identifier, email address and basic profile information, such as your name and profile image, with Clerk. We use this information to authenticate you and control access. We do not request access to your Gmail, Google Drive, contacts or calendar.

Content you share
Optional category suggestions are stored privately with your submission for administrators to review; they do not appear on the public wall. If you send us a story or community message, we process its text and the information needed to review and manage it. Moderation reports and related evidence are available to authorized administrators. Automated moderation can send reported community text and limited conversation context to AWS Bedrock for assessment. Private moderation tests also send the sample text supplied by an administrator to Bedrock; test text is not saved as a community incident. Google account information is not used to train our own AI models or sent to the moderation model.

Private submission links
After a website submission, we give you a private link to check its status without an account or email. Anyone with the link can check that status and, once published, open the public story. The link does not reveal unpublished text or moderator notes. We store a hash of its random secret, rather than the secret itself. Keep your saved link private; we cannot recover it if you lose it.

Contributor credit
Submissions are anonymous by default. If you choose X credit, connecting to X confirms your account identifier and handle. We use read-only permissions for a profile check; we do not post, read direct messages or request ongoing access. Access tokens are not retained. A protected browser cookie remembers the confirmed identity for up to 24 hours; the submitted account identifier, handle and verification date are stored privately with your story. Only your handle and profile link appear after approval. Credit links your story to your public identity. You can submit anonymously even with X connected, or disconnect X from the form. Older verification-post requests may still be reviewed privately.

Public content
Only reviewed stories selected for publication appear on the site. Do not include identifying details about yourself or other people in a story. Permission to feature a story outside the site is separate from permission to publish it here.

Service providers and sharing
We use Clerk for authentication and Amazon Web Services for hosting, storage and moderation processing. These providers process information needed to provide their services. We do not sell your personal information or use Google account information for advertising. We may disclose information when required by law or necessary to protect the service and its users.

Retention and your choices
Ordinary community message context expires after 24 hours. Moderation incidents and related reports are scheduled for cleanup after 30 days. Account records, submitted stories and published content may remain until they are removed; backups and provider security records can take longer to expire. To request access, correction or deletion of your information, email rick@rootsignal.io. You can also revoke Google access in your Google account settings; revoking access does not itself delete an existing Club Spite account or previously shared content.