How does JoinTheSwing handle blocking and reporting?

At launch, JoinTheSwing is designed to check member blocks across supported discovery, travel, availability, and messaging paths so either direction of a block prevents those surfaces from reconnecting the pair. A block is a product control, not a promise that every off-platform contact or future surface can be prevented.

At launch, a submitted report is planned to record the reporter, subject, reason, detail, optional urgency, and any supported target or context the member supplies, then return a moderation reference. Blocks and reports are separate records; the design does not promise that every block generates a report or that aggregate patterns are automatically surfaced to support.

At launch, a targeted message or supported thread report may preserve bounded context for review. Ordinary reports do not automatically include a full conversation, timeline, or verification file, so describe the concern clearly and identify the relevant target when the form supports it.

At launch, provider-backed identity review will give the support team another bounded signal when it investigates abuse, but it does not guarantee that a removed person cannot evade controls or create another account. Members should still use blocking, reporting, independent safety plans, and emergency services when appropriate rather than treating verification as permanent exclusion.

At any live event, report a boundary violation through the host's stated safety process and contact emergency services when appropriate. JoinTheSwing does not host or organize events. An event's own safety procedures come from its host and venue.