← Back to the club

YOUR INFORMATION

PRIVACY.

How we handle information you share.
Updated October 26, 2026.

01

Article discussions

Article comments use your verified-email account and public alias. We store comment text, account ownership, review status, feedback and moderation history. Only approved comments are public; pending text and moderator feedback are visible to the contributor and administrators. Reports use a hashed account identifier to prevent duplicate reports. Account participation blocks are shared with Wall discussions. Removing a parent comment hides its replies. Article comments do not send email notifications.

02

Wall discussion and verdicts

New stories may receive two-way verdicts and moderated comments. We store verdict choices with hashed browser/account and network identifiers to limit duplicate voting and review abuse. Browser identifiers do not prove a unique human. Original Felt that reactions are retained separately. Signed-in comments use a public alias; account IDs, email, moderation feedback and report identities stay private. Public comments include the alias, text, publication date and optional country/region you provide. Country/region is self-reported, not inferred from your network location. You may edit or remove your own comments; moderation and abuse records may be retained. A separate private author link for a new anonymous story can connect it to your verified-email account, allowing follow-ups as Original poster without publishing your identity. Keep it private. Existing status links do not grant author access. Choosing to follow a discussion stores a subscription and creates in-site notifications for approved comments; no email is sent. Stop following from the story or your wall account. After Hours preference is stored in a first-party cookie for30 days and controls adult-theme browsing. Weekly picks retain a publication record and vote total; no automatic social posting or financial reward is attached.

03

Club Spite support

Private support tickets, reports and enhancement requests are associated with your signed-in Clerk account and verified primary email. Conversations take place at clubspite.com/support. We store your messages, ticket status, the section you contacted us from and, for reports, a snapshot of the public content. Only you and authorized administrators can read your ticket. Listing owners do not receive reporter identities or ticket messages. Internal administrative notes and correction histories are restricted to administrators. We retain support and moderation records to resolve requests and address abuse. Resend may send necessary ticket-update notifications using your address and a sign-in link, without including ticket text. These messages do not subscribe you to marketing. Do not send passwords or sensitive personal information. Use a support ticket for access or deletion requests. If you cannot sign in, contact @JoinClubSpite on X.

04

Built out of spite directory

Listing submissions include a private maker contact email, public maker name, supported platforms and product description. You may upload up to three optional app screenshots with descriptions. Screenshots are resized, converted and stripped of image metadata, stored privately until approved, and published with approved listings. Remove customer data and other private information before uploading. Abandoned, unattached images are eligible for deletion after seven days. Only approved listings and recommendation reviews are public. Private review notes, contact emails and email delivery records are available to authorized administrators. We use Resend to send listing receipts and moderation updates, sharing the recipient address and message with that provider. These transactional messages do not subscribe you to marketing. Private drafts save with your account, excluding consent declarations. Drafts are never public and can be discarded. Verified owners may publish moderated maker responses and release updates, including optional screenshots. Updates do not reset reviews or enter the new-listings digest. When you choose maker-response notifications we store your verified account email privately and use Resend to notify you after an approved response. Disable these notices in My account; they are separate from the daily digest. In-account response notices also remain available. Clerk manages sign-in for listings and reviews. We store your Clerk account ID to establish ownership and prevent duplicate reviews, and use your verified primary account email for private listing updates. Account IDs and email addresses are not public. Your dashboard shows your own submissions, reviewer feedback and editing controls. You can pause or remove your listings there. Their public pages, screenshots and reviews become unavailable; private moderation records remain. This does not delete your account or erase stored records. Sharing a listing with X or your device’s share menu is your choice and sends its public link and selected public text to the destination you choose. Old private listing links no longer grant access. We retain listing changes, reviewer feedback and administrative decisions for moderation. Reviews include your chosen public name, optional comparison and affiliation disclosure. One review per account per product and hashed network identifiers help limit duplicate reviews and submission abuse; they do not independently verify that you used the product. Open a support ticket at clubspite.com/support to correct or remove a listing, review or private contact information.

05

Daily listings digest

Signing up for the Built out of spite daily digest is optional and separate from listing administration. We store your email, subscription status, confirmation time and unsubscribe status. You must confirm your email before receiving new approved listings, at most once a day. Resend processes the address and email content to deliver these messages. Unsubscribe using any digest email; no login is needed. We retain unsubscribe status to prevent further sends. Unsubscribing does not stop necessary messages about your own listings. Open a support ticket at clubspite.com/support to request deletion.

06

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.

07

Website analytics

We use Google Analytics to understand visits to our public homepage, rules, privacy and Built directory pages, including referral sources, public listing views and clicks on our X links and product websites. We also record when a listing form is started or previewed, successful new listing/review submissions and digest signup/confirmation events using sanitized public page addresses. Search terms, form text, email addresses, account IDs, private links and account/admin page views are excluded. 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.

08

Draft recovery in this tab

To help recover unsent writing after refresh or browser history, this browser tab may keep story, listing and review draft fields in session storage. Recovery expires after 30 minutes; expired records are discarded when read. These tab copies are not published. Connected listing drafts also save privately to your account. Restoring a tab draft requires you to confirm the required declarations again; story feature permission is not restored.

09

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.

010

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.

011

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.

012

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.

013

Contributor credit

Submissions are anonymous by default. You can optionally publish a country/region or use a community alias from a signed-in, verified-email account. 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.

014

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.

015

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.

016

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, open a ticket at clubspite.com/support. If you cannot sign in, contact @JoinClubSpite on X. 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.

Questions or privacy requests? Open a support ticket or contact @JoinClubSpite on X

We will update this page when our data practices change.