Incident Reporting
Off The Traxx — ott-dungeon.com
This page is for anyone — member, guest, anyone in the local scene, anyone at all — who needs to tell us about something that's happened. Consent violations. Boundary violations. Coercion. Behavior at events that concerned you. Something that happened outside of our events that you think we should know about. Concerns about a member, a non-member, an applicant in vetting, or someone you've heard about in the community.
If you're not sure whether something belongs here, send it. Sorting it out is our job, not yours.
To file a report: use the structured form at ott-dungeon.com/report. The form supports identified, pseudonymous, and fully anonymous submission and walks through the same fields described below. You can also email
For an imminent emergency at one of our events, call 911 and tell whoever is at the door.
Who handles reports
Reports go to a small response team: the lead vetter and one or two designated others. They're trained for this work, distinct from the broader vetter group, and the same people every time. Reports do not get forwarded around or discussed beyond the response team without a clear reason and (where possible) the reporter's input.
The response team can escalate to the broader vetter group when a decision needs more eyes — bans, revocations, anything where two vetters disagree, anything where the response team has a conflict of interest. They never share more information than the escalation requires.
What kinds of reports we take
Anything that happened at one of our events. Consent violations, ignored safewords, coercive behavior, harassment, capacity-policy violations, DM calls you disagreed with, incidents during cleanup or in parking lots — all of it.
Behavior outside our events that bears on member safety. Things you saw or experienced with a member at their home, at another venue, in the broader local scene, or online. We don't have authority over what happens at other people's parties, but if a member is doing things elsewhere that we'd want to know before our next event, tell us.
Things involving non-members. A non-member partner of a member. Someone in the local scene who isn't a member. Someone who applied to us once and didn't get in. Someone who hasn't applied yet but might. We accept these reports too. For non-members with no current operational relationship to us, we usually file the report rather than launching an active investigation we don't have the standing for — the report becomes part of our record and surfaces if and when that person ever applies for membership or shows up as a plus-one.
Reports about people you don't have a name for. A description, a context, a partial scene name — send what you have. We may not be able to act on it now, but it may match something else later.
First-person reports (something happened to you), third-person reports (something happened to someone you know, or you witnessed something happen between others), and pattern reports (you've noticed something across multiple interactions, not one specific incident) all go to the same place. Different shapes of report get handled a little differently — see "What happens after you file" below.
How to file
Use the form at ott-dungeon.com/report, or email
- Who you are (or aren't — see anonymity below)
- Who or what the report is about
- When and where it happened (approximate is fine; exact dates aren't needed)
- What happened, in your words
- Witnesses, if any
- What outcome you're hoping for, if you have a preference
- Whether we can contact you, the subject, witnesses, and the affected person (if different from you)
You don't have to give us all of this. The only thing we actually need is some description of what happened — the rest helps us follow up but isn't required to take the report.
Anonymity and contact
You have three options for how identifiable you are:
- Identified: real name and contact info. Easiest for us to follow up; standard for most reports.
- Pseudonymous: a contact method we can reach you through (a burner email, a Signal number, a throwaway account) without your real name. We can ask follow-up questions, you stay anonymous to us. This is what most "anonymous" reports actually look like in practice and is usually the right choice if you want privacy without losing the back-and-forth.
- Fully anonymous: no name, no contact info, no way for us to follow up. We will still take the report. Honest caveat: we may not be able to act on a fully anonymous report the same way we could with a follow-up channel, especially if the report needs clarification. If there's any way you can give us a contact method while keeping your identity protected, that materially helps us do something with what you've told us.
Filing via the form
The form at ott-dungeon.com/report asks you to pick one of the three anonymity modes above. Identified and pseudonymous reveal a contact section; fully anonymous hides it. Choosing pseudonymous and providing a burner email gets you the same back-and-forth as a regular email exchange, with the response team only ever seeing the pseudonym you chose.
Filing via email
You can also email
- Identified: email us from any address. Include your real name in the message body if your email address doesn't already make it obvious.
- Pseudonymous: create a burner email (ProtonMail, Tutanota, or any free service used only for this purpose) and email us from there. Use a pseudonym in the message. Reply from that same address; we'll reach you there.
- Fully anonymous: create a one-time email account, send the report, and don't check that account again. Or use a service like AnonAddy that masks your sending address. Be aware that we have no way to come back to you with questions, and the report content itself is the only thing we'll be working from.
Whatever you choose, we don't share the reporter's identity with the subject of the report unless you've explicitly authorized it. Sometimes the subject can guess from context who reported them — we can't prevent that — but we don't tell them, and the doc you're reading right now is the only place where the existence of an anonymity option is publicly stated, so simply having reported anonymously doesn't itself disclose your identity.
What happens after you file
Within 24 hours of receipt: the response team acknowledges your report. If you gave us a contact method, you'll hear from us. The acknowledgment may be brief ("we received this, here's what happens next, here's roughly when you'll hear from us next") — that's intentional, not dismissive. Every report gets acknowledged before any decision-making happens.
For first-person reports (you're reporting something that happened to you):
If the subject of the report is a member scheduled for an upcoming event, we pause their access to that event right away. We tell you that we're doing this before the pause goes into effect, so you're not surprised when the subject reaches out asking what's going on. The pause is not a decision; it's a hold so we can talk to you properly without an event happening in the meantime.
We then schedule a real conversation with you. Not a form, not a back-and-forth over email — an actual conversation, in whatever medium works for you, at whatever pace you can handle. We listen. We ask what happened, what you'd like to happen now, what you're worried about. We do not lead, and we don't push you to escalate beyond what you've asked for.
For third-person reports (you're reporting something that happened to someone else, or that you witnessed):
We pause the subject's access after the response team talks to you, usually within 24–48 hours of receipt. The conversation establishes credibility — not "do we believe you" so much as "do we understand the report well enough to act on it." We're trying to figure out whether what you've told us, taken at face value, describes something the venue should respond to. The bar is deliberately low.
We will also try to reach the affected person, but the pause does not wait on that contact. If the affected person is reachable and wants to participate, the rest of the process incorporates their input. If they're unreachable or don't want to participate, the investigation continues with the information we have.
For any report describing imminent risk — a named subject, a named affected person, a specific upcoming event, specific behavior we have reason to expect at that event — we pause the subject's access immediately, regardless of whether the report is first- or third-person. We do this because the alternative is letting an event happen that we've been specifically warned will produce harm.
Then we investigate. This means talking to people: the reporter, the subject, the affected person if different from the reporter, witnesses, DMs who were on shift, anyone else with relevant information. We don't surprise the subject with accusations they can't respond to — they get told what's been said about them in general terms, and they get a real chance to respond.
Then we decide. Outcomes range from:
- No action, with reporter informed and given options. Sometimes this is right. We tell you why.
- Conversation with subject, plus a note in their record. The subject is told the concern, hears the reporter's perspective in general terms, and the conversation itself becomes part of their ongoing record at our venue. Future incidents weigh against this context.
- Conditions on continued membership. Probationary period, no private play arranged through the venue for some time, mandatory conversation with a specific person, attendance at non-play events only for a stretch.
- Revocation. Membership ends. Subject is informed of the decision and the general reasoning.
Bans and revocations require panel review (the response team plus additional vetters) — never a single person's call.
Then we close the loop with you. You hear what was decided and why, within the limits of what we can share without compromising other people's privacy.
Reports about non-members and applicants
Special cases worth being explicit about:
A report about someone currently in vetting: the report becomes part of the vetting decision. The applicant has a right to respond to the substance of the report (without the reporter's identity disclosed unless the reporter has consented), and the vetting decision incorporates the report along with everything else.
A report about someone who's never been a member and has no current connection to us: we file it. The report is logged in our records and surfaces if and when that person applies for membership or attends as a plus-one. We usually do not launch an active investigation in these cases — we don't have standing or operational reach to investigate someone who has no relationship to our venue, and pretending we do would be dishonest. The report still matters, just on a delayed timeline.
A report about a former member: depends on context. If the former member could plausibly come back as a guest or applicant, the report is treated like a non-member report (filed, surfaces if they return). If they're long gone and unlikely to return, we may still log the report for cross-venue safety alert purposes (see below) but won't take individual action.
How long this takes
Most reports are resolved within 2–4 weeks. Some are resolved much faster (the report is clear, the subject is honest about what happened, an outcome is reached in the first conversation). Some take longer (witnesses are hard to reach, the subject contests the account, the situation is genuinely complicated and warrants more time).
If your report is going to take longer than usual, you'll hear from us at the two-week mark with a status update. You should never feel like you've been ghosted; if more than two weeks have gone by and you haven't heard anything, email
Reporting to police
You can report to police whether or not you also report to us. Our process is independent of any police process — we don't wait on a police investigation, we don't change our outcome based on what police do or don't do, and we don't require you to choose one or the other.
We want to be honest about what police reporting looks like in this context, because that honesty is part of what you need to make the choice well:
Police don't always handle BDSM-context reports well. Investigations can become focused on whether the activity was consensual rather than on the violation itself. The criminal justice process is slow, public, and often retraumatizing. Many members of this community have professional, family, or immigration situations where any police record can be damaging. Sex workers, undocumented members, and members with prior records face additional risks. Conviction rates for sex-offense cases are generally low, and the path through the system is hard even when it works.
None of that is an argument against police reporting. It's the context. For some reporters, police involvement is the right call and we'll support it. For others, it isn't. The choice is yours alone, and our process doesn't pressure you in either direction.
If you do choose to report to police, we will not share your information with them unless legally compelled. Our records can be subpoenaed, and in that case we comply with what the law requires — but we don't volunteer information to police about your report, and we tell you (where legally allowed) if law enforcement has requested records about you.
Mandatory reporting
Idaho law (I.C. § 16-1605) makes essentially every adult a mandated reporter for child abuse, abandonment, or neglect. The full statute is at https://legislature.idaho.gov/statutesrules/idstat/title16/t16ch16/sect16-1605/.
What this means for you, in plain terms: if a report we receive includes information that triggers this obligation, we have to report that part to authorities. The law isn't optional and we can't promise confidentiality on something the law won't let us keep confidential.
The law's edges are real and the response team navigates them with care. If you're considering disclosing something that might involve a minor and you want to understand how we'd handle it before you disclose, ask first. We'd rather have that conversation up front than discover halfway through your report that we're about to do something with your information you didn't expect.
Privacy
Reports are stored in a system separate from regular member records, encrypted at rest, with access restricted to the response team and strictly logged. Every time a member of the response team views a report, the access is recorded.
Information from a report enters the affected member's vetting record only when an outcome warrants it (a note, conditions, a revocation). Routine investigation conversations don't propagate into the regular member record.
When a report is closed, the underlying communications (your emails to us, follow-up messages, internal notes) are kept for three years and then purged. The decision and its general reasoning stay in the record longer, both because we need that for vetting consistency and because we may need to refer back to it if patterns emerge.
If you want to know what we have on file about a report you filed, email and ask. If you want us to delete records of a report you filed, we will if we can — but if the report led to actions involving other members, some record has to stay so we can explain why those actions were taken.
Cross-venue safety alerts
If a report leads to a member being banned for behavior that poses a credible safety risk, we may share that fact (and the general nature of the concern) with vetters at other venues we have established relationships with. We don't share alerts based on declined applications, on registry hits alone, on personality conflicts, or on situations that didn't rise to a credible safety risk. The bar for sharing is high, and the affected member is informed if their information has been included in an alert.
Appeals
If you're the subject of a report and disagree with the outcome, you can appeal to the panel (response team plus additional vetters). Email
If you're the reporter and the outcome wasn't what you needed, tell us. Sometimes the right response is "we'll revisit," sometimes it's "here's why we landed where we did, even though it isn't what you hoped for," sometimes it's both. We'd rather hear that we got it wrong than have you walk away.
Things this process is not
To be clear:
- This is not a court. We don't apply criminal-law standards of evidence, and we don't claim the kind of certainty courts claim. We make community-safety decisions on the information we have, using the standards described here.
- This is not a substitute for police if police is what you need.
- This is not a guarantee. Our process is one layer of safety; the other layers are negotiating carefully, communicating with partners, looking out for each other on the floor, and trusting your gut when something is off.
- This is not optional for the response team. If a credible report reaches us, we act on it, even when acting is uncomfortable and even when the people involved are people we like.
Questions
If anything in this document is unclear, or if you want to talk through how a report would be handled before filing one, email
Last updated: 2026-05-14. We'll post a notice in the members-only section of the site when this document changes in any meaningful way.