How do moderation reports and support boundary receipts differ from blocking on JoinTheSwing?
Use a quiet mutual block on JoinTheSwing whenever personal preference or workplace discretion calls for two-way invisibility without rule violations, reserve formal moderation reports for non-consensual conduct, impersonation, or harassment, and use private boundary receipts to confirm safety actions without alerting the other account.
Healthy private communities distinguish everyday social boundaries from policy violations. If you spot a coworker, neighbor, or couple whose vibe simply isn't your match, applying a mutual block quietly hides both profiles from each other across supported discovery and messaging surfaces without accusing anyone of misconduct or notifying the other party.
A formal moderation report is built for community safety: non-consensual behavior, boundary pushing after a clear decline, suspected impersonation, unsolicited explicit harassment, or threats to share private media off-platform. Submitting a report routes structured context to Trust & Safety review while pairing cleanly with a block so the reported account cannot contact you.
JoinTheSwing's support boundary receipts give you a clear, private record of the protective steps you have taken — such as a timestamped block, revoked album permission, or submitted report reference — without exposing your confidential report narrative to the person you reported.
Underlying moderation integrity rests on real identity accountability paired with strict data minimization. From the current Veriff check, JoinTheSwing never receives or stores source ID images, selfie captures, or biometric templates — retaining the verification result, Veriff's session reference, a consent receipt, and non-biometric review metadata — while retired in-house verification_documents files are deleted when the account is deleted (see /legal/privacy). Digital memberships run via Apple StoreKit 2 and Google Play Billing; explore /guides/support-boundary-receipts.