Privacy Policy
Version: 2026-11-08 Last Updated: November 8, 2026
[CYPHRAPASS LEGAL ENTITY NAME, LLC — TO BE INSERTED UPON FORMATION] ("CyphraPass," "we," "us," or "our") operates the CyphraPass mobile application and website (collectively, the "Platform"). This Privacy Policy explains how we collect, use, disclose, and protect your personal information when you use our Platform.
By using the Platform, you acknowledge the data practices described in this Privacy Policy.
1. Information We Collect
1.1 Information You Provide
| Data Type | When Collected | Details |
|---|---|---|
| Account Information | Registration and profile setup | Name, email address, phone number, username, profile photo(s), bio, city and state, and interests. Attendees also provide date of birth (to confirm they are 18 or older) and gender. Organizers also provide an organization name, logo, and event types. |
| Payment Information | Ticket purchase or subscription | Payment card details and Apple Pay tokens. These are processed and stored by Stripe; we do not store full card numbers. |
| Organizer Financial Information | Stripe Connect onboarding | Banking details, government-issued ID, and tax information. These are collected, processed, and stored by Stripe. |
| Event Content | Event creation | Event titles, descriptions, photos, cover images, venue details, ticket pricing, and age requirements. |
| User-Generated Content | In-app activity | Reviews (ratings for Music, Venue, Safety, Value, and Overall, with an optional comment and an anonymous option), gallery photos and videos, event posts, event chat messages, and direct messages. |
| Communications | Support inquiries | Emails, in-app reports, and feedback you send us. |
1.2 Information Collected Automatically
| Data Type | Purpose |
|---|---|
| Device and App Information | Device model, operating system, app version, and a push notification token, used to run the app, diagnose problems, and deliver notifications. |
| Location Data | Your device's location (latitude and longitude), collected only while you are using the app and only if you grant location permission. We use it for distance-based event sorting, finding events that are happening near you, discovering nearby organizers and people, and — only for events whose Organizer has enabled it — sending an arrival photo prompt when you are at the venue. |
| Usage Data | Screens viewed, features used, and key actions (for example, steps in the checkout and payout setup flows), collected through our product analytics provider. |
| Log and Diagnostic Data | IP address, crash reports, and error logs collected through our servers and our crash-reporting provider. |
1.3 Information from Third Parties
| Source | Data | Purpose |
|---|---|---|
| Stripe | Payment confirmation status, subscription status, refund and chargeback events | Processing transactions and managing Organizer payouts |
| Spotify | Playlist metadata (track names, artist names, album artwork) | Displaying setlists on event pages when linked by Organizers |
| YouTube | Video embed metadata | Displaying embedded video setlists on event pages |
| Supabase Auth | Authentication tokens | Secure sign-in and session management |
2. How We Use Your Information
We use the information we collect to:
- Operate the Platform: Create and manage your account, process ticket purchases, facilitate escrow payouts to Organizers, and deliver digital tickets with QR codes.
- Show Relevant Events: Sort and surface events near you, trending events, events happening now, and events your friends are attending.
- Enable Social Features: Display mutual friends attending events, manage follow and friend relationships, and facilitate direct messaging under our messaging rules (Organizer-to-Organizer messaging is allowed; Attendee-to-Organizer messaging is allowed with no follow required; Organizer-to-Attendee messaging is blocked unless the Attendee messages first; and Attendee-to-Attendee messaging requires a mutual follow).
- Process Payments: Charge buyer service fees, hold funds in escrow, calculate platform fees, and execute automated post-event payouts via Stripe Transfers.
- Ensure Safety & Moderation: Run automated content screening (see Section 4), process user reports, and enforce blocks and account actions.
- Send Notifications and Transactional Emails: Deliver push notifications (for example ticket confirmations, event reminders, review window reminders, friend requests, and direct messages) and transactional emails (for example account confirmation, password reset, receipts, and refund notices).
- Improve the Platform: Analyze usage patterns, diagnose technical issues, and improve features and performance.
- Comply with Legal Obligations: Respond to legal requests, enforce our Terms of Service, and protect against fraud.
3. How We Share Your Information
We do not sell your personal information. We share information only in the following circumstances:
3.1 With Organizers
When you purchase a ticket, the Organizer of that event can see your name, profile photo, ticket tier, and ticket status in the guest list used for door entry. Organizers do not receive your email address, phone number, or payment details.
3.2 With Other Users
- Your public profile (name, handle, profile photo, interests, join date) is visible to other users unless you set your profile to Private.
- Private profiles are excluded from Discover search and require manual approval of follow requests.
- If you hold a ticket to an event, your profile appears in the "Who's Going" list visible to other ticket holders for that event.
- Reviews you post are visible to other users. If you choose to post a review anonymously, your name is not displayed with it.
3.3 With Service Providers (Subprocessors)
We share data with the following third-party service providers who help us operate the Platform:
| Provider | Data Shared | Purpose |
|---|---|---|
| Stripe | Payment details, Organizer banking and identity information | Payment processing, escrow, payouts, and subscription billing |
| Supabase | Account data, event data, messages, uploaded files | Database hosting, authentication, and file storage |
| OpenAI | The text of chat messages, direct messages (DMs), reviews, event titles and descriptions, and event posts, sent for automated safety screening before delivery or publication | AI content moderation (see Section 4) |
| Google (Gemini API) | Images (such as gallery photos, event post images, and video thumbnails) sent for automated safety screening; and event details an Organizer enters when using the AI description helper (title, theme, draft notes, venue, date) | AI image moderation and AI-assisted event description writing |
| Resend | Your email address, name, and the content of the transactional email being sent (for example, ticket receipts and password reset messages) | Sending transactional emails |
| Expo | Push notification tokens and notification content | Delivering push notifications |
| PostHog | Usage events and pseudonymous user identifiers | Product analytics |
| Sentry | Crash reports, error diagnostics, and pseudonymous user identifiers | Crash reporting and performance monitoring |
| Discord | Alerts sent to our internal team channel about safety reports and blocked content, which can include a short excerpt of blocked content and the usernames of the people involved (see Section 4.3) | Internal safety and operations alerting |
We also use cloud hosting and caching providers to run our servers. We do not authorize these providers to use your information for their own marketing purposes.
3.4 For Legal Reasons
We may disclose your information if required by law, subpoena, court order, or government request, or if we believe disclosure is necessary to protect the rights, safety, or property of CyphraPass, our users, or the public.
3.5 Business Transfers
In the event of a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change.
4. AI Content Moderation and Third-Party Processing of Private Communications
We screen your messages with third-party AI services — including private direct messages. Please read this section carefully.
4.1 What We Screen and Who Processes It
Before content is delivered or published, our servers automatically send it to an AI moderation service to check for harmful material (for example harassment, hate, violence, self-harm, sexual content, and illegal activity):
| Content | Screened by |
|---|---|
| Direct messages (DMs) — private one-to-one messages | OpenAI (text) |
| Event chat messages | OpenAI (text) |
| Reviews (comments), event titles and descriptions, and event posts | OpenAI (text) |
| Gallery photos, event post images, and video thumbnails | Google Gemini (images) |
This means that the full text of every direct message and event chat message you send is transmitted to OpenAI, a third party, for screening before it reaches the recipient. Only the content to be screened is sent; we do not include your name, email address, or account ID in the screening request. However, the content itself may contain personal information if you type it into a message.
4.2 Automated Decisions
If the screening service flags content, it is blocked and not delivered or published, and you will be told that it was not sent. Blocked messages are not saved to your conversation. Our screening is designed to "fail closed": if the screening service is unavailable, content may be temporarily blocked until screening can be completed. Screening is automated and can make mistakes. If you believe content was blocked in error, contact support@cyphrapass.com.
4.3 Human Review of Flagged Content
When content is blocked, we record the reason (for example, a category such as harassment or hate) and send an alert to our internal team channel (hosted on Discord) so we can review it. That alert can include the first 80 characters of the blocked content, the channel it was sent in (for example "Direct Message"), and the username, name, and account ID of the sender and (for DMs) the recipient. We may also review content that is reported by users. We may take action on accounts as described in our Community Guidelines and Terms of Service.
4.4 How the Providers Handle This Data
OpenAI and Google process this content on our behalf through their business API services and under their own terms and privacy policies, including their own retention and abuse-monitoring practices. We do not use your messages to train our own AI models. We do not sell your messages.
5. Data Retention
We retain your personal information for as long as needed to provide our services and for the purposes described in this Policy. Specifically:
- Account data: Retained while your account is active. When you delete your account, your profile fields (name, email, phone number, photos, bio, and similar) are anonymized and your authentication account is removed.
- Ticket and transaction records: Retained as needed for financial, tax, fraud-prevention, and dispute purposes (generally at least seven years), even after account deletion, in anonymized form where possible.
- Direct messages: When you delete a conversation, it is hidden from your view; it is not immediately erased from our systems and the other participant's copy is unaffected. When either participant deletes their account, all direct messages involving that account are permanently deleted for both participants.
- Public content (reviews, event posts, event chat messages, and gallery items): Retained until removed. After you delete your account, public content you posted may remain, attributed to an anonymized "Deleted User" account.
- Blocked content: Content blocked by automated screening is not saved to the conversation or published. A short excerpt may remain in our internal alert channel, which we maintain under our internal practices.
- Log, analytics, and crash data: Retained for as long as needed for debugging and platform improvement, and subject to our providers' retention settings.
6. Your Rights & Choices
6.1 Account Deletion
You may delete your account at any time from Settings > Delete Account within the app. Upon deletion, we will:
- Cancel any active subscription.
- Refund tickets for upcoming events.
- Delete your follows, blocks, saved events, notifications, direct messages, and similar activity data.
- Anonymize your personal data (name, email, phone number, photos, bio replaced with anonymized placeholders).
- Remove your authentication account.
Organizers with upcoming events that have sold tickets, or with a remaining payout balance, must resolve those first before their account can be deleted.
This process is designed to comply with Apple App Store and Google Play Store account deletion requirements.
6.2 Data Access & Portability
You may request a copy of your personal data by emailing privacy@cyphrapass.com. We will respond within 45 days.
6.3 Correction
You may update your account information at any time through the Edit Profile screen in the app.
6.4 Location Data
You may disable location services for CyphraPass through your device's system settings or the location setting in the app. Disabling location will limit distance-based sorting and nearby event discovery.
6.5 Push Notifications
You may disable push notifications through your device's system settings at any time.
6.6 Email
We send transactional emails related to your account and purchases. We do not currently send marketing emails. If we do in the future, you will be able to opt out via an unsubscribe link in each marketing email.
7. State Privacy Rights (including California and Maryland)
Depending on where you live, you may have the right to:
- Know what personal information we collect, use, and disclose.
- Access a copy of your personal information.
- Correct inaccurate personal information.
- Delete your personal information (subject to certain exceptions).
- Non-Discrimination for exercising your privacy rights.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
To exercise your rights, email privacy@cyphrapass.com or use the in-app account deletion feature.
8. Children's Privacy
The Platform is not intended for users under the age of 18. We do not knowingly collect personal information from children under 18. If we become aware that we have collected information from a child under 18, we will promptly delete that information.
9. Data Security
We implement security measures designed to protect your personal information, including:
- Encryption in transit (HTTPS/TLS) for data transmitted between your device and our servers.
- Secure payment processing via Stripe (PCI DSS compliant).
- Rotating, signed QR codes for ticket verification, using HMAC-SHA256 cryptographic signatures.
- Access controls restricting internal access to personal data on a need-to-know basis.
While we strive to protect your data, no method of electronic transmission or storage is 100% secure. We cannot guarantee absolute security.
10. International Data Transfers
Your information may be transferred to and processed in the United States, where our servers and service providers are located. By using the Platform, you acknowledge this transfer.
11. Third-Party Links & Services
The Platform may contain links to third-party services (e.g., Spotify, YouTube, Apple Maps, Google Maps, Stripe). We are not responsible for the privacy practices of these third parties. We encourage you to review their respective privacy policies.
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Each version has a version identifier shown at the top of this document. When we make material changes, we will update the version and "Last Updated" date and notify you within the app, and we may ask you to review and accept the updated policy. We keep a record of which version you accepted and when.
13. Contact Us
If you have questions or concerns about this Privacy Policy or our data practices, contact us at:
[CYPHRAPASS LEGAL ENTITY NAME, LLC — TO BE INSERTED UPON FORMATION] [MAILING ADDRESS — TO BE INSERTED UPON FORMATION] Email: privacy@cyphrapass.com