Glossary

RACK

Acronym: Risk-Aware Consensual Kink Also written: risk-aware consensual kink

RACK (Risk-Aware Consensual Kink) is an ethical framework that holds that no kink is entirely without risk, and requires partners to identify and explicitly accept specific risks rather than assume an activity is simply safe.

Quick Facts

Type Framework
Risk level Low
Beginner-friendly With guidance
Related to SSC, consent, negotiation, safety frameworks

RACK stands for Risk-Aware Consensual Kink. It emerged in kink communities in the 1990s as an alternative to SSC (Safe, Sane, and Consensual), motivated by a specific critique: the word “safe” in SSC implies that an activity can be made unconditionally safe if approached correctly. RACK holds that this is inaccurate and, more importantly, potentially misleading.

The core claim of RACK

Every kink activity carries some level of risk. Rope bondage carries risk of nerve compression. Impact play carries risk of bruising or injury. Psychological dynamics carry risk of emotional distress. Power exchange carries risk of misreading cues. Even comparatively low-risk activities like dirty talk carry a small risk of saying something that unexpectedly lands badly.

RACK does not argue that these risks are large, likely, or unavoidable. It argues that they exist, and that pretending they don’t — by calling something “safe” — prevents honest negotiation. If partners believe an activity is simply safe, they have no reason to identify the specific risks involved, discuss how to mitigate them, or decide together whether the risk level is acceptable to both of them.

How RACK changes the negotiation question

SSC asks: “Is this safe? Are we both sane and consenting?”

RACK asks: “What are the specific risks in this activity? Have we both identified them, understood them, and agreed to accept them?”

The practical difference is in the depth of pre-scene conversation. A RACK framework encourages partners to name the actual risks of what they’re planning — not as a deterrent, but as a precondition for genuine informed consent. You can’t fully consent to something whose risks you haven’t considered.

The consent requirement in RACK is not just agreement to participate — it is agreement to participate with an honest picture of what participation involves. This is a higher standard than “we both said yes.” It requires that the yes was informed.

This is particularly relevant for higher-risk activities, but RACK practitioners often apply the framework to lower-risk activities as well, on the grounds that the habit of honest risk assessment scales well and prevents complacency.

For how these frameworks apply in practice — including how to structure pre-scene negotiation, assess risk levels, and build a shared safety plan — the safety hub covers both RACK and SSC in fuller context.

RACK alongside SSC

RACK and SSC are not competing frameworks in any practical sense. Most people who use RACK language also use SSC language, and most kink education resources discuss them together. The two frameworks agree on the non-negotiability of consent and the importance of safety — they differ in how they characterize what “safe” means and what the consent standard should be.

SSC is worth reading alongside this entry for the full picture of how these frameworks relate.

RACK and edge play

RACK is particularly useful as a framework for activities that are sometimes categorized as edge play — practices with higher risk profiles that require explicit, detailed negotiation. In those contexts, SSC’s language of “safe” activity can feel inaccurate in ways that undermine honest communication. RACK’s language of “risk-aware” better captures the actual situation: we’ve looked at the risks clearly, we’ve prepared as well as we can, and we’re choosing to proceed together.

Often confused with

SSC vs. RACK

SSC (Safe, Sane, and Consensual) asks whether an activity is safe and whether both partners are sane and consenting. RACK accepts that no activity is unconditionally safe and shifts the question to: have we identified the risks, and have we both accepted them? RACK is a refinement of SSC's framework, not a rejection of it.

Permission to skip safety measures vs. RACK

RACK's position is that all kink carries some risk. This requires more honest conversation about risk, not less safety preparation. Acknowledging risk does not mean accepting harm — it means naming the risk clearly so both partners can make an informed decision.

Safety note

RACK's acknowledgment of risk is not a license to skip safety practice — it is an argument for more explicit, honest risk assessment rather than less.

Take the free Yes/No/Maybe list

Map your interests and limits before the conversation. Rate 130+ activities privately, then compare overlaps with your partner — only what you both said yes to is revealed.

No signup required to start. Free to invite a partner.