PRIVACY
Privacy Policy
How Foreskin Online minimizes and handles site, commerce, and community data.
Data minimization
Foreskin Online collects data needed to operate education, research records, commerce pages, accounts, the text community, moderation, security controls, and support. It does not use advertising pixels, session replay, public member directories, community uploads, or DMs.
Accounts and community
WordPress stores private email/login data, password hashes, pseudonymous display names, adult self-attestation, policy versions, text topics/replies, reports, appeals, warnings/suspensions, and moderation records. Community email is not public. Discussions are member-gated and noindex. Private moderator notes are restricted.
Contact and support
The Contact form stores name or pseudonym, email, category, subject, message, status, and timestamps in a restricted first-party admin inbox. It does not accept files. Rate controls use short-lived pseudonymous keys. Do not submit highly sensitive information.
Commerce and cookies
WooCommerce uses cookies/session data needed for cart, checkout, and accounts and may process billing, shipping, order, payment-status, and technical security data after direct commerce is activated. Payment-card data should be handled by the selected payment provider, not stored by this site. Direct checkout is currently blocked.
A dedicated transactional transport is not yet verified. When configured, operational email may cover password reset, privacy requests, moderation/appeals, support alerts, and WooCommerce order events. No automatic marketing subscription exists.
Infrastructure
Cloudflare provides delivery and security services and may process ordinary request data such as IP address, request headers, and security signals. Hosting and web-server logs follow operational retention rather than community activity tracking.
Retention, export, and deletion
Community export and anonymizing deletion use WordPress privacy tools and the authenticated account workflow. Resolved moderation data is scheduled under the documented lifecycle; open matters and holds are retained. Support-message retention requires final owner/legal approval. Backups are historical snapshots and are not rewritten immediately after deletion; they expire under the backup lifecycle.