Safety Center

U.S. venue focus & supported state-ID verification — still call 911 first for emergencies.

What you can do in the app

• Report: use the in-app Report controls wherever we surface them (typically on vibe cards or matched-profile surfaces). Screens shift by version route through the flows shown in-product—those paths create a moderation ticket we can correlate with server logs.
• Block: use Block (or equivalent wording) inside the flows we expose. Blocking is designed to promptly stop reciprocal discovery or repeated exposure consistent with shipped implementation—we treat it seriously for trust.
• Withdraw discoverability: toggle discovery off anytime the product affords it—which immediately reframes what others reasonably infer.

Combining these picks up most everyday friction before escalation—but always escalate to onsite staff first if someone is visibly unsafe offline.

Emergencies come first

If anyone is injured, threatened, intoxicated dangerously, exhibiting weapons, harming minors—or if you hesitate whether it qualifies—invoke local emergency services immediately. Afterwards you may additionally inform us (admin@irlapp.org) with non-urgent follow-up specifics we can correlate with moderation logs.

In-app safeguards (by design)

• Venue-bounded discovery: presence features aim to correlate with physically sharing a venue context—not roaming an entire metropolitan map.
• Verification gating: discoverability ordinarily requires satisfying identity checkpoints described inside the app.
• Anonymity before mutual interest: identity surfaces escalate only along reciprocity pathways defined product-side.
• Structured coordination: instead of unrestricted chat loops, cues stay intentionally narrow encouraging face-to-face resolution.
• Automatic session endings: discoverability intends to lapse when leaving a venue perimeter or after maximum windows—see in-app explanatory copy.

Blocking (what persists technically)

Blocking—as described above—suppresses reciprocal discovery promptly within product rules. Blocking does not silently erase lawful historical server logs investigators may rely on afterward for audits or subpoenas—we retain only what statute and responsible safety practice demand.

Reporting users or behavior

Submit in-app reports using the category selectors we ship, a factual narrative (who/what/when), approximate timestamps, venue names when applicable, and screenshots only when it is safe—you may email supplemental context to admin@irlapp.org with your account identifiers so we can correlate tickets. Redact other people's sensitive data when attaching files.

Moderation timelines (what to expect)

Acknowledgments: we aim to acknowledge substantive reports within a few U.S. business days; anything suggesting imminent harm jumps ahead in the queue as soon as staffing allows.

Initial review: for typical cases we target first-pass human or assisted review within about fourteen (14) U.S. business days unless complexity, third-party verifier delays, subpoena coordination, holidays, or investigative depth reasonably require more time. We may extend when facts are genuinely unclear—measured enforcement beats rushed mistakes.

How moderation decisions are made

Humans plus assisting automated classifiers weigh proportionality—investigating spoofing versus misunderstanding, patterns across devices, and escalation to law enforcement when warranted. Repeated low-grade friction can still yield enforcement even if any single incident seemed minor.

Sensitive imagery & illegal content

Child sexual abuse material mandates reporting pipelines—never re-forward illegal images; supply descriptors only unless law enforcement directs otherwise aligned with mandates. Similarly credible violent threats—we treat seriously and may preemptively suspend pending investigation communicating minimally to avoid tipping harassers dangerously.

Doxxing & off-platform escalation

Using discovered identity to bombard alternate channels unsolicited violates guidelines—tell us patterns connecting on-platform facilitation to harassment elsewhere when evidence exists.

Venues can help offline

Quietly engaging staff separates parties in physical space faster than asynchronous digital review sometimes—coordinate practical safety first always.

Ongoing commitments

Transparency improves iteratively—we publish foundational policies publicly (Privacy, Terms, Guidelines) and revise as product realism shifts.

Contact

Concerns insufficiently urgent for emergency lines: admin@irlapp.org