orgasm.dev

Acceptable use

Adults only, consent first, never covertly. What every integration must do, what it must never do, and the data obligations that come with it.

orgasm.dev measures something intimate about a person. Using it is conditional on the following. Breaking them ends sessions and revokes keys.

These rules take effect on October 20, 2026. You accept them when you set up your account, and again whenever they change.

Adults only

Every person on camera is 18 or older, or older where their local law requires, and you have verified it. A self-declared birthday is not verification. Say how you verified in consent.ageVerification.

If there is any reason to think a person on camera might be a minor, do not send the video. Never build for, market to, or allow use by minors.

The person on camera has agreed to this analysis, explicitly and specifically, before it starts:

  • They know what is measured (how close they are to orgasm; its onset, peak and end; how their face reads; and in a live session their vocalizations and loudness, their contractions and movement where a body view is sent, and how each region of their face moves), who receives it, and how long it is kept.
  • They know which screens show it, and agreed to each: their own device, and any screen others watch, such as a partner's, a coach's or a stream. A screen that draws their face's movement, on a generic face, does so only if they agreed to that too; view tokens leave the face's channels out unless made with includeFace, and a creator's overlay leaves the face off unless they turn it on.
  • They can stop it at any moment, with a control that is always on screen.
  • They see when analysis is running.
  • Consent to one experience is not consent to another, and it can be withdrawn.

On the person's device, the HUD shows both the indicator and the Stop control in every layout but overlay, which, like the stream attribute, is for screens other people watch. When the person presses Stop, ending the session is yours to do.

Every request that starts an analysis attests it: consent.subjectIsAdult and consent.subjectConsented must both be true, or the request is refused with consent_required. Set them only when your product has done both; keep the record your consentRecordId refers to.

Recordings

Submit only recordings of people who agreed to this analysis of that recording. Never analyse videos of other people, scraped or downloaded content, or performers' work without each performer's explicit agreement.

Never

  • Analyse anyone who does not know, or who cannot freely refuse.
  • Use orgasm.dev to identify, track or monitor people.
  • Store or use the subject read as a person's sex or gender, or for anything but choosing detectors.
  • Treat a call as proof about a person, or attach consequences to one that the person has not agreed to.
  • Use the events in decisions about employment, insurance, credit, housing, education, immigration or legal proceedings.
  • Present the events as a medical diagnosis or treatment.
  • Sell the events, or share them beyond what the person agreed to.

Your data obligations

The events, and the video they come from, are special-category data in many places: data about a person's sex life and, for the face, biometric data. Depending on where you and the person are, laws such as the GDPR and UK GDPR (Article 9: explicit consent), Illinois's BIPA (a written release before collecting face geometry, and a published retention schedule), Texas's CUBI, Washington's My Health My Data Act and the CCPA's rules for sensitive personal information may apply. You are responsible for meeting them: a lawful basis, a privacy notice, a data protection impact assessment where required. This page is not legal advice.

Your notice must tell the people on camera that orgasm.dev processes their sessions for you, and that it may keep de-identified, aggregated statistics from them to improve its detectors. The Privacy Policy describes both, and what orgasm.dev does with your own account.

Retention and deletion

  • Video is never stored. Live media exists only inside the enclave during analysis; a recording is deleted once analysed.
  • Events stay readable for retentionDays after a session ends or a recording completes (30 by default, up to 90). With 0, nothing is kept: events are only delivered as they happen.
  • Cost attribution. A session's userReference, clientReferenceId and metadata stay with its charges for 13 months, so your finance team can see what it cost, and are then erased. The charges stay, without them.
  • On request, delete a person's data at once: purgeLiveSessionsByUserReference for every live session with their userReference, purgeLiveSession for one session, deleteRecording for a recording. A purge erases the session's references and metadata along with its events; its charges stay, as what your company was billed. Webhook deliveries already made are in your systems; delete them there.

A userReference must be an id that only you can link to the person, never their email address, phone number or name, so orgasm.dev never learns who they are (cost attribution).

Reporting misuse

If you believe orgasm.dev is being used on someone without their consent, or on a minor, write to legal@orgasm.dev.

On this page