Fetlife

FetLife
Type	Social networking platform
Purpose	To connect kinksters, build community, share events, and discuss BDSM, fetish, and related topics.
Founded	2008
Founder	John Baku
Website	fetlife.com
Related concepts	OPSEC, Consent, Munches, Community

FetLife is a social networking website designed specifically for people interested in BDSM, fetishism, and kink. Launched in 2008 by Canadian programmer John Baku, it has grown to become one of the largest online platforms for the kink community, hosting millions of users worldwide. FetLife functions like a hybrid of a social network and a forum: users create profiles, join groups based on their interests or location, share writings and photos, and discover events such as munches, workshops, and play parties.

Within the framework of Risk‑Aware Consensual Kink (RACK), FetLife is a powerful tool for community building, education, and mentorship, but it also introduces significant risks related to privacy, security, and consent. Using FetLife safely requires a solid understanding of OPSEC and a cautious approach to sharing personal information.

Background

FetLife was created to fill a gap: existing social networks (such as Facebook) were hostile to kink and sexual expression, frequently removing profiles and content that violated their terms of service. FetLife explicitly permits explicit content and discussion of taboo topics, making it a safe haven for the kink community. It is free to join, with premium subscriptions offering additional features such as advanced search and ad‑free browsing.

Unlike dating apps, FetLife is not primarily designed as a hookup platform, although some users do connect romantically or sexually through it. Its emphasis is on community, discussion, and event promotion, similar to how LinkedIn is for professional networking.

Features

• User profiles: Users can list their roles (dominant, submissive, switch, etc.), fetishes, relationship status, and location.
• Groups: Thousands of discussion groups cover specific kinks, local communities, identity groups, and educational topics.
• Events: A built‑in calendar allows users to discover munches, workshops, play parties, and conferences in their area.
• Writings: Users can publish long‑form posts, similar to blog entries or essays.
• Photos and videos: Users can upload explicit media, with granular privacy controls (friends‑only, followers‑only, private).
• Friend and follower system: Similar to Facebook, users can add friends and follow others to see their activity in a feed.

Importance in RACK

For those exploring or living a kink lifestyle, FetLife is often the first point of contact with the wider community. It enables:

• Access to education: Newcomers can find groups dedicated to safety, negotiation, and technique. Many experienced practitioners share detailed guides and personal accounts of risk‑aware play.
• Mentorship and peer support: Users can connect with others who share their specific interests or challenges, reducing isolation and providing a sounding board for questions about safety, consent, and identity.
• Event discovery: Attending a local munch often listed on FetLife is the most common way for a newcomer to meet kinksters in a safe, low‑pressure, public setting.

However, the platform also presents risks. The openness that makes it valuable also means that information shared there can be screenshotted, scraped, or viewed by unintended parties, including employers, family, or law enforcement.

Privacy and OPSEC considerations

FetLife's privacy model is robust but not foolproof. Key considerations include:

• Pseudonymity: Users are encouraged to choose a screen name that is not tied to their legal name. However, over time, many users inadvertently reveal identifiable information through photos, event check‑ins, or details in their writings.
• Friends‑only and followers‑only content: These settings limit visibility, but they do not prevent a determined individual from taking screenshots or using a fake account to gain access.
• Photos and metadata: Uploaded photos may contain EXIF data (GPS coordinates, device information) unless stripped beforehand. See OPSEC for guidance.
• Data breaches: Like any website, FetLife is vulnerable to hacking. Users should assume that anything they post could eventually become public, and should never share anything that could be used to blackmail or destroy their vanilla life.
• Reporting and blocking: FetLife provides tools to report harassment, doxing, and non‑consensual content. Users should familiarize themselves with these tools.

Within a RACK framework, using FetLife responsibly means acknowledging and mitigating these risks. The decision to join, to post, and to attend events must be an informed one, and users should have a contingency plan in case their identity is exposed.

Consent and community standards

FetLife's terms of service prohibit harassment, doxing, and the posting of non‑consensual intimate media. Users are expected to respect the boundaries of others. However, as with any large platform, enforcement is imperfect, and users should be prepared to advocate for their own safety. Do not hesitate to block, report, and cut contact with anyone who makes you uncomfortable, even if they are well‑known in the community. A reputation does not excuse boundary‑crossing.

Known incidents

RACKWiki incident reports

Community‑submitted reports of privacy breaches, doxing, or harassment linked to FetLife are collected at RACKWiki Incident reports/FetLife. Editors are encouraged to contribute anonymised experiences to help others understand and mitigate the platform's risks.

See also

• OPSEC
• Consent
• Negotiation
• Community
• Munches