TRUST & SAFETY ARCHITECTURE

How safety works on CyphraPass, step by step.

This page documents the exact technical controls behind tickets, venue addresses, messaging, reviews, user blocking, and payouts—including where platform or OS limits exist—so advisors, parents, and attendees can evaluate the system plainly.

01 · Tickets Can't Be Faked

30-second rotating QR codes and single-use door entry

Every active ticket signs its QR payload using a per-ticket cryptographic secret and a time-based one-time password (TOTP) window that rotates every 30 seconds. Static photos or forwarded screenshots expire quickly rather than acting as permanent passes.

When scanned at the door, validation performs an atomic state transition from active to used. Cancelled or refunded tickets are rejected, concurrent or duplicate scans are blocked, and offline door scanners verify against the same per-ticket secret with conflict resolution on sync. Repeated invalid or duplicate scan attempts trigger organizer/admin anomaly alerts.

Honest platform distinction on screenshots

While the ticket screen is open, screen-capture protection is active: Android blocks screenshots and screen recording at the operating-system level. iOS does not allow apps to prevent screenshots system-wide. On iOS, the 30-second rotating code and atomic first-scan lock are what stop screenshot sharing—any captured code expires within seconds.

AUTHENTICATION CYCLEHMAC-SHA256 • 30s
Payload formatticketId:signature
Code windowRegenerates every 30s
Door state transitionactive → used (1x)
Screen-capture protection by OS
Android
OS-level capture lock prevents screenshots and recordings on the ticket screen.
OS Blocked
iOS
Apple does not permit apps to block screenshots. 30s rotation + single-scan lock invalidate captured images within seconds.
Time-Gated
02 · No Scalping by Design

Mutual-friend transfers with no resale marketplace

CyphraPass is built around one ticket per person—not bulk inventory speculation. If plans change, a ticket can only move once directly to a mutual friend in-app, at no markup.

  1. STEP 01

    Limit one per person

    Checkout purchases one ticket at a time and blocks buying a second active ticket while you already hold one for that event. No secondary resale market exists.

  2. STEP 02

    Mutual friends only

    Transfers are restricted to accounts that already follow each other (accepted follow in both directions). Strangers cannot send unsolicited tickets.

  3. STEP 03

    One transfer, 7-day window

    Each ticket may be transferred at most once, before the event starts and before scanning. The recipient has 7 days to accept before the invitation expires.

  4. STEP 04

    Sender QR voided immediately

    Once accepted, ownership moves to the recipient, the sender’s QR code is permanently cleared, and a fresh ticket secret is issued to the recipient.

LOCATION VISIBILITY0.25–0.50 MI FUZZ
Public pin (fuzzed center)Exact venue(ticket holders only)
Before purchase
“Secret Location”
City/state & fuzzed area only
Active ticket holder
Venue & street address
Unmasked for confirmed holders
03 · Location Privacy

Exact venue addresses stay hidden until you hold a ticket

Public event listings, search results, and unpurchased event pages do not expose where an event takes place. Server-side location masking strips the venue name, street address, and postal code—replacing the address label with Secret Location alongside the general city/state and a deterministically fuzzed map point offset 0.25 to 0.5 miles from the real address.

Full street-level venue details are included in API responses only after a user holds a confirmed active or used ticket for that event (or is the event's organizer).

04 · Messaging Boundaries & Pre-Delivery Screening

Who can message whom, and how content is screened

Direct messaging enforces four role-based permission rules on the backend so neither random attendees nor organizers can cold-message someone uninvited.

Attendee → Attendee
Mutual follow required

Both users must hold accepted follows in each direction before a direct message thread can open.

Attendee → Organizer
Allowed directly

Attendees can ask an event host logistical or safety questions without waiting for a follow back.

Organizer → Attendee
Blocked unless attendee messaged first

Hosts cannot initiate unsolicited DMs to attendees. Replies unlock only inside an attendee-started thread.

Organizer → Organizer
Allowed directly

Event hosts can coordinate directly with other organizer accounts.

AI screening runs before delivery

Every message sent in event chat or direct messages is checked synchronously for safety before it is saved or broadcast.

1 · SUBMITTED
Message received by API

Text is intercepted prior to database insert or real-time delivery.

2 · SCREENED
Synchronous safety check

Moderation evaluates the content synchronously and fails closed if an error occurs.

3 · OUTCOME
Blocked before anyone sees it

Flagged content is rejected with a policy notice and never written or sent.

05 · Verified Reviews

Ticket-gated feedback within a 72-hour post-event window

Only accounts holding a valid ticket for an event can submit a review—capped at one review per user per event and open strictly for 72 hours after the event concludes. Written comments pass through AI moderation, and reviewers can toggle an anonymous option so their name and handle are stripped from public view.

Scope of the ticket check

Reviews require a valid ticket (active or used), not a door-scanned one—so someone who bought a ticket and didn't end up attending can still leave a review.

Five structured review categories1–5 Rating Scale
01Overall Experience
Headline event rating across the night.
02Music / Vibe
How well the sound and pacing matched expectations.
03Venue / Atmosphere
Space quality, layout, crowd comfort, and logistics.
04Value for Money
Whether the experience matched the listed ticket price.
05Safety & Organization
Door entry flow, crowd handling, and host communication.
06 · Blocking & Reporting

What blocking actually changes—and what it doesn't hide

Blocking is designed to break personal connections, hide discovery surfaces, and prevent private messages. We document its exact boundaries below rather than overstating its reach.

Enforced immediately when you block
  • +Removes mutual follows: deletes follow links in both directions immediately.
  • +Hides from Discover: removes both accounts from nearby people and organizer discovery.
  • +Hides blocked organizers' events: filters out their listings and denies direct event access.
  • +Prevents attendee DMs: breaking the mutual follow blocks direct messages between attendees.
  • +Harassment spike alert: accounts blocked by 3 or more users automatically trigger an admin safety alert.
Known limits of a block
  • −Shared event chat: blocking a user does not filter their messages out of a shared event's group chat room.
  • −Public event reviews: blocking does not hide public reviews previously posted on event pages.

Reporting abuse & 5/day anti-spam creation limit

Submitting a report logs the target resource and reason for moderation triage and immediately notifies administrators via real-time safety alerts and email. Across all tiers, organizers are also capped at 5 event creations per day so discovery stays free of automated feed spam.

Read Community Guidelines
07 · Financial Protections

48-hour post-event escrow keeps refund funds available

Ticket payments are settled to the CyphraPass platform account first—not pushed directly to the host at checkout. Organizer payouts unlock only after the event finishes and 48 hours have passed without cancellation. Once tickets sell, organizers cannot delete the event or pull it back to draft; cancelling runs automated event-level refunds (ticket face value plus the $1.29 + 5.5% buyer service fee) back to original payment methods, and the 48-hour buffer ensures funds remain on hand if an event is fraudulent or fails to occur.

POST-EVENT ESCROW TIMELINEHOURLY PAYOUT CHECK • 48H HOLD
1T-0 · Checkout

Funds collected on platform

Stripe charges stay held by CyphraPass instead of transferring immediately to the organizer.

2Event Ends

Attendance & review window opens

Post-event end time triggers the 48-hour hold clock (and opens the 72-hour review window).

3+48 Hours

Payout hold window completes

Hourly settlement releases net proceeds to the organizer only after 48h pass without cancellation or hold.

If cancelled before payout (or flagged as fraudulent)

Held funds stay available for automated event-level full refunds (ticket price plus the $1.29 + 5.5% buyer service fee).

Full Refund Path