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.
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.
ticketId:signatureactive → used (1x)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.
- 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.
- 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.
- 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.
- 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.
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).
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.
Both users must hold accepted follows in each direction before a direct message thread can open.
Attendees can ask an event host logistical or safety questions without waiting for a follow back.
Hosts cannot initiate unsolicited DMs to attendees. Replies unlock only inside an attendee-started thread.
Event hosts can coordinate directly with other organizer accounts.
| Sender → Recipient | Rule | How It Works |
|---|---|---|
| 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.
Text is intercepted prior to database insert or real-time delivery.
Moderation evaluates the content synchronously and fails closed if an error occurs.
Flagged content is rejected with a policy notice and never written or sent.
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.
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.
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.
- +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.
- −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.
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.
Funds collected on platform
Stripe charges stay held by CyphraPass instead of transferring immediately to the organizer.
Attendance & review window opens
Post-event end time triggers the 48-hour hold clock (and opens the 72-hour review window).
Payout hold window completes
Hourly settlement releases net proceeds to the organizer only after 48h pass without cancellation or hold.
Held funds stay available for automated event-level full refunds (ticket price plus the $1.29 + 5.5% buyer service fee).
Read the governing documents
Every control described above maps to our published terms, privacy notice, and refund rules.
Marketplace role, 18+ eligibility, buyer service fee terms, and account deletion rules.
Data collected at signup and checkout, location handling, moderation processing, and retention.
Why individual sales are final, how event-level cancellations trigger automatic full refunds, and escrow rules.
Prohibited conduct across events, chats, DMs, and reviews, plus enforcement actions.
Step-by-step instructions to delete an account immediately in-app or submit a web deletion request.