Lyra+ Privacy Policy
Effective date: September 27, 2026 Last updated: September 19, 2026
1. Who We Are and Scope
This Privacy Policy explains how Lyra Plus, Inc., a Delaware corporation doing business as Lyra+ (“Lyra,” “we,” “us,” or “our”), collects, uses, discloses, retains, and protects personal information when you use the Lyra+ mobile application, websites, ticket marketplace, subscriptions, communications, events features, and related services (collectively, the “Services”).
It also explains the privacy choices and rights that may be available to you. This Policy applies to users, ticket buyers and sellers, Hosts, event attendees, website visitors, and people who communicate with us. It does not apply to information processed independently by a Host, venue, payment provider, app store, social network, or other third party under its own privacy policy.
Lyra Plus, Inc. is the controller or business responsible for personal information covered by this Policy unless we state otherwise.
Lyra Plus, Inc.
1111B South Governors Avenue, Suite 59189
Dover, Delaware 19904, United States
Privacy contact: support@lyraplus.com
Privacy request portal: https://lyraplus.com/privacy-request
2. Personal Information We Collect
The information we collect depends on how you use Lyra+.
2.1 Information you provide
Account and profile information. Name, username, profile photo, date of birth or age range, email address, phone number, password or authentication information, pronouns, biography, interests, general location, social links, and profile preferences.
Verification information. Information used to verify identity, age, school affiliation, eligibility, phone number, payment method, or Host status. This may include a government-issued identification document, selfie, date of birth, school email address, verification result, and fraud signals. Lyra processes school-verification communications through Resend and may use Apple, Google, Stripe, Supabase, or another provider disclosed at the time of collection to verify account, identity, age, payment, or Host information. Where possible, a verification provider processes the source document and Lyra receives only the result, document type, age or identity confirmation, and limited risk information.
Transaction and ticket information. Events viewed or purchased, tickets held, transferred, listed, or resold, order and ticket identifiers, purchase price, fees, refunds, payouts, tax information, billing address, payment status, and chargeback information. Payment providers generally process complete payment-card details; Lyra receives tokens, limited card details such as brand and last four digits, and transaction results.
Host information. Business or organization name, Event details, venue relationship, payout account details, tax forms and taxpayer information, licenses, insurance information, authorized representatives, and Host communications.
User Content and social activity. Profile material, messages, Event chats, group participation, reviews, ratings, stories, photos, videos, Memories, comments, reactions, follows, invitations, attendance, and other content or interactions. Private content is processed according to the audience controls shown in the Service, but may be reviewed when reported or when needed for safety, security, or legal compliance.
Preferences and survey information. Event interests, music or venue preferences, accessibility requests, marketing preferences, feedback, survey responses, and participation in promotions or research.
Communications. Messages and attachments sent to support, safety, legal, privacy, or other Lyra teams, along with call or chat records where notice and consent are provided as required.
Automatic Event highlights and semantic editing inputs. Lyra may automatically process photos and videos contributed to shared Memories for an Event after the Event to prepare a private highlight draft for its Host, and process that media again for Host-requested edits. AWS processes source media, analyzes quality, duplicates, subject framing, and video intervals, and renders and stores recap files. For semantic editing, OpenAI may receive a limited shortlist of resized photos and video frames, with pseudonymous candidate identifiers, to understand visible scenes, score interesting moments, and suggest their place in the recap. These results help Lyra select, trim, crop, sequence, and assemble the highlight. Resized images can still contain recognizable people or other personal information; pseudonymous identifiers do not make the images anonymous.
Private group Memories are excluded. Event highlights are independent of the account-level Cloud photo analysis for AI drafts choice: declining that caption-drafting choice does not disable highlight processing. Lyra provides any additional disclosure and obtains any explicit permission required by applicable law or platform rules before sharing personal information with a third-party AI provider. We do not use highlight analysis to identify people through face recognition or infer sensitive or protected traits. The Host reviews the draft and controls publication to the Event audience or export. Requests to OpenAI disable provider application-state storage; endpoint-specific safety and abuse retention may still apply.
AI caption-drafting inputs. If you use caption drafting, Lyra processes the instruction you enter, the unpublished caption you are editing, limited post and Event context, attachment types, and any photos you select for analysis. On supported devices, Apple Intelligence may process inputs on the device. When on-device capability is unavailable, Lyra may use OpenAI as a cloud processor. Selected photos are sent to cloud AI only after you enable the account-level Cloud photo analysis for AI drafts choice. Text-only cloud drafting may operate without that separate photo choice.
2.2 Information collected automatically
Device and network information. IP address, device identifiers, device type, operating system, browser, app version, language, mobile carrier, time zone, and network information.
Usage information. Screens or pages viewed, searches, clicks, sessions, time spent, referral source, Event impressions, interactions with recommendations, subscription status, app crashes, performance logs, and diagnostic events.
Crash and performance diagnostics. Lyra uses Sentry to collect crash reports, stack traces, app hangs and watchdog terminations, app and operating-system version, device model, performance traces, profiles, and sanitized application logs. When an error occurs, Sentry may also receive a short, error-triggered session replay and a screenshot or view hierarchy. Lyra masks all text and images in those recordings and screenshots, disables visual capture on authentication, private-message, payment, precise-location, and user-media surfaces, and does not intentionally send private-message contents, authentication inputs, payment credentials, precise coordinates, or user photos and videos. Routine sessions are not uploaded as replays. Default personal-information collection, memory introspection, network URL capture, and accessibility-identifier reporting are disabled.
Product analytics and masked session replay. Lyra uses PostHog to collect privacy-sanitized lifecycle, screen, feature, performance, and product-interaction events associated with a stable pseudonymous account identifier. Lyra does not send a user's name, email address, username, raw account identifier, search text, message contents, precise coordinates, payment credentials, or user-authored text as event properties. PostHog session replay is enabled for routine sessions at a 100% sampling rate to help us understand product behavior and diagnose issues. Because Lyra uses SwiftUI, PostHog captures masked screenshot frames rather than a DOM-style wireframe. All visible text, text inputs, images, and sandboxed views are covered by masks before a frame is enqueued. Replay is paused entirely on authentication, private-message, payment, precise-location, and user-media surfaces. Device console logs may be attached to a replay for debugging; Lyra redacts protected values and drops lines that may contain request or response bodies, parameters, prompts, transcripts, or similar content. Network-request capture is disabled. PostHog is configured to discard stored client IP data after its GeoIP and bot-detection transformations. Product analytics and masked replay are on by default and can be turned off at any time in Settings > Privacy.
Ranked-feed information. When personalization is enabled, Lyra records bounded feed-request metadata, pending recommendations, recommendations that actually become visible, their position and ranking source, and outcomes such as dwell, likes, shares, profile or Event opens, ticket clicks, dismissals, and explicit feedback. Feed-request records do not contain post bodies, media, precise coordinates, or location-derived values.
AI Memory and inferred preferences. Lyra’s AI-powered personalization system creates and updates an evolving account-linked profile (“AI Memory”) using information you provide and signals from your use of the Services. AI Memory may include stated and inferred interests, preferred music, performers, venues, Event types, locations, schedules, social settings, price ranges, likely Event affinity, content preferences, and indicators that a recommendation was useful or irrelevant. These are predictions and may be inaccurate.
Location information. Approximate location derived from IP address and, only with device permission, precise or background device location. We use location to show nearby Events, personalize discovery, support Event features, reduce fraud, and provide functions you request. Precise device coordinates used for recommendations are request-scoped and are not stored in Lyra's backend feed, AI, analytics, audit, or logging records. You can control device-location permission in your operating-system settings. Some features may not work without it.
Optional Bluetooth proximity information. If you separately turn on Recognize Hang Outs and grant Bluetooth permission, Lyra exchanges short-lived rotating identifiers with nearby Lyra devices and records coarse encounter times. Lyra uses reciprocal observations over time to suggest that you spent time with a mutual friend. The feature does not use GPS, store precise location, transmit a stable Bluetooth device identifier, award progression points, or make another person eligible for a recommendation. A single observation is not treated as a Hang Out. You can turn the feature off in Lyra's Privacy settings or revoke Bluetooth permission in device settings.
Cookies and similar technologies. Cookies, pixels, local storage, software development kits (“SDKs”), and similar tools may collect device, usage, attribution, analytics, and preference information. See Section 9.
2.3 Information from other sources
We may receive information from:
- other users who invite you, tag you, include you in content, share contacts with permission, report an interaction, or transfer a ticket;
- Hosts, venues, performers, ticketing partners, and Event service providers;
- app stores, payment processors, banks, and payout providers;
- identity, age, phone, email, anti-fraud, and security providers;
- social networks or login providers when you choose to connect an account;
- marketing, attribution, analytics, and referral partners, subject to applicable consent and opt-out requirements;
- public records and publicly available sources; and
- law enforcement, regulators, courts, and other parties responding to legal or safety matters.
We may combine information from these sources with information collected through Lyra+.
2.4 Sensitive personal information
Depending on your use, Lyra may process information treated as sensitive under some laws, including precise geolocation, account credentials, government identification information, financial account or payout information, private message contents, racial or ethnic origin or sexual orientation if you voluntarily include it in content, and biometric or face-related information used by a verification provider.
We use sensitive information only as reasonably necessary to provide requested Services, verify users, process transactions, provide safety and security, comply with law, or for another purpose with your consent. Lyra does not use sensitive personal information to infer characteristics for advertising. Do not place sensitive information in a public profile or public post unless you want it to be public.
3. How We Use Personal Information
We use personal information for the following purposes:
3.1 Provide and operate Lyra+
- create, authenticate, maintain, and support accounts;
- display profiles and provide social features according to user choices;
- provide Event discovery, search, chats, stories, groups, and Memories;
- process ticket purchases, transfers, resale, refunds, subscriptions, payouts, and taxes;
- verify identity, age, eligibility, and Host information;
- provide customer support and respond to requests; and
- send transactional messages about accounts, Events, tickets, subscriptions, safety, and policy changes.
Lyra also processes request-scoped caption instructions, unpublished captions, allowlisted Event facts, attachment types, and—when you choose—selected photos to generate Personal, Hype, and Details caption ideas. Lyra does not persist or log those unpublished drafting inputs, derived scene descriptions, or draft results, and does not use them for analytics. The published caption, if any, is ordinary User Content governed by your audience choice.
For Event highlights, Lyra uses shared Event media, technical analysis, cloud AI moment scores and scene groupings, and the Host’s editing choices to prepare and revise recaps. Drafts remain private to the Host until publication. Removing or restricting source media prevents its use in subsequent hosted highlights and may invalidate a hosted recap. We cannot recall copies already exported outside Lyra. You may also exercise the privacy rights described in Section 8.
3.2 Personalize recommendations and measure engagement
We use interests, general or permitted location, Event activity, ticket and attendance history, social connections, content interactions, and similar signals to rank or recommend Events, people, groups, and content; calculate or display Lyra+ Scores and status; measure whether recommendations are useful; and improve personalization.
Lyra’s AI learns from users and updates its memory over time. When you view, search for, save, share, purchase, attend, rate, hide, or report Events or content—or interact with people and groups—Lyra may use those actions to create or update AI Memory associated with your account. Information you directly provide, such as selected interests and feedback, may also update that memory. AI Memory helps Lyra remember preferences between sessions, adapt to changing interests, rank Events and people, reduce repetitive or irrelevant recommendations, and personalize the experience before, during, and after Events.
AI Memory can include inferences that you did not expressly provide. For example, repeated engagement with certain Events may cause Lyra to infer an interest in a music genre, venue, neighborhood, social setting, schedule, or price range. Lyra may strengthen, weaken, replace, or remove an inference as new activity occurs. AI Memory does not mean that a human continuously reviews your activity, and it is not intended to determine medical, psychological, credit, employment, housing, insurance, or legal characteristics.
You can review or change selected interests, correct personalization inputs, hide or dismiss recommendations, manage location and other permissions, reset AI Memory, turn ranked-feed personalization off, turn product analytics and masked replay off, or use Reset Recommendations through Settings > Privacy. Ranked-feed personalization and privacy-sanitized product analytics are on by default. Turning ranked-feed personalization off stops new behavioral learning and future model-training use for your account; your follows, your own content, generic recent or trending content, request-scoped proximity, safety filters, explicit feedback, and bounded repeat prevention may still shape the feed. Turning analytics off stops future PostHog product events and replay for your account. Reset Recommendations clears your account-linked feed preference profile, affinity, request, impression, outcome, and served-history records while preserving follows and explicit safety feedback. You may also exercise applicable access, correction, deletion, objection, restriction, and automated-processing rights under Section 8. Turning off or resetting personalization may make Lyra’s recommendations less relevant.
These systems generate predictions and inferences. Ordinary Event and social recommendations do not make decisions that produce legal or similarly significant effects. Where applicable law gives you rights concerning automated decision-making, profiling, or targeted recommendations, we will provide the required notice and controls.
3.3 Safety, integrity, and fraud prevention
We use information to verify accounts and transactions; detect bots, fake accounts, scams, payment fraud, ticket duplication, harassment, abuse, prohibited content, and policy violations; investigate reports; enforce our Terms and Community Guidelines; protect users and the public; and preserve evidence.
3.4 Improve and develop the Services
We analyze performance, feature usage, feedback, and aggregated trends to debug, test, research, develop, and improve Lyra+. This may include developing or evaluating ranking, recommendation, content-moderation, fraud, and support systems. We use deidentified, aggregated, or minimized information where reasonably possible.
Lyra does not authorize OpenAI, Google, xAI, or Hugging Face to use private messages, precise location, government identification documents, payment credentials, or account-linked AI Memory to train their general-purpose models on Lyra’s behalf. We configure provider data controls and contractual restrictions where available. Provider processing and technical retention vary by service and feature; we minimize the information sent and provide additional notice or obtain consent where required by law.
3.5 Communicate and market
We send service communications needed to operate your account and transactions. With consent where required, we may also send promotions, Event recommendations, offers, surveys, and product news. You can unsubscribe from marketing email or text messages using the instructions in the message, but you may still receive non-promotional account and transaction communications.
3.6 Comply with law and protect legal interests
We use information to comply with tax, accounting, payment, sanctions, consumer-protection, privacy, accessibility, ticketing, and other legal requirements; respond to valid legal process; establish, exercise, or defend legal claims; complete audits; and enforce agreements.
4. Legal Bases for Processing in the EEA, UK, and Similar Jurisdictions
Where applicable law requires a legal basis, we rely on:
| Legal basis | Processing examples |
|---|---|
| Performance of a contract | Creating your account; processing tickets, subscriptions, transfers, resale, refunds, and payouts; providing social and Event features you request. |
| Legitimate interests | Securing the Services; preventing fraud and abuse; creating and updating AI Memory for basic personalization; measuring recommendation quality and performance; improving features; defending legal claims; communicating about similar Lyra services, subject to your rights. We balance these interests against your rights and expectations. |
| Consent | Precise device location; certain marketing communications; optional device permissions; non-essential cookies or SDKs; certain sensitive information or connected-account features; and AI Memory processing where consent is required. You may withdraw consent prospectively. |
| Legal obligation | Tax and accounting records; lawful requests; sanctions screening; consumer and privacy requests; regulatory compliance. |
| Vital interests or public interest | Responding to an urgent threat to life or safety or cooperating with authorities where the law permits or requires it. |
If we rely on legitimate interests, you may request information about the balancing assessment relevant to your information by contacting us.
5. When We Disclose Personal Information
We disclose personal information only as described below. The exact recipients depend on the features you use.
5.1 Other users and the public
Profile information, public content, reviews, ratings, attendance signals, and social interactions may be visible to other users or the public according to the feature and your settings. People in a private group or chat, or people with access to Memories, can see information shared with that audience. Ticket transfers may disclose the information needed to complete the transfer.
5.2 Hosts, venues, and Event partners
We may provide Hosts, venues, and authorized Event partners with information reasonably needed to administer an Event, validate tickets, manage entry, communicate material changes, provide accessibility, address safety, issue refunds, prevent fraud, and meet legal requirements. Depending on the Event, this may include your name, ticket type, ticket identifier, transaction status, age or verification status, accessibility request, and limited contact information.
A Host or venue may act as an independent controller or business for its own uses. Lyra does not authorize them to use ticket-buyer information for unrelated marketing unless you consent or applicable law permits it.
5.3 Service providers and contractors
We send or make information available to providers that perform services for Lyra, provide an integration you request, or supply content displayed in Lyra+. Our current vendor list is also maintained on our Vendor List page.
| Vendor | Information sent, received, or accessed | Lyra usage and purpose |
|---|---|---|
| Apple | Apple account identifier and sign-in credentials, device and app information, purchase and subscription status, push token, wallet-pass information, map queries and location when used, speech or AI inputs and outputs when an Apple feature is invoked | App Store distribution, StoreKit subscriptions, Sign in with Apple, APNs notifications, Apple Wallet passes, Maps/MapKit, Apple Intelligence, speech, and device services. Some Apple processing occurs on-device; data sent to Apple is governed by the applicable Apple service terms and privacy policy. |
| Supabase | Account, authentication, profile, social, AI Memory, Event, ticket, transaction, message, moderation, device, and operational data stored or processed in Lyra’s Supabase project | PostgreSQL database, authentication, Edge Functions, Realtime, Row Level Security, cron and queues, and some storage. Supabase generally processes this information as Lyra’s infrastructure provider. |
| Amazon Web Services | User-uploaded photos, videos, media metadata, chat attachments, delivery logs, IP address, and request information | S3 media storage, CloudFront content delivery, separate private S3 storage for chat attachments, and Event highlight media analysis and recap rendering. |
| Stripe | Name, contact and billing information, payment method details, transaction and ticket information, subscription status, Host identity and business information, payout account, tax and fraud signals | Web and Event-ticket payments, subscriptions, Stripe Connect Host accounts, payouts, refunds, disputes, fraud prevention, and entitlement synchronization. Stripe may act as Lyra’s processor and, for certain payment and compliance activities, as an independent controller. |
| OpenAI | Resized photos and video frames and pseudonymous candidate identifiers shortlisted for Event highlight semantic editing, prompts and responses, minimized conversation context, pseudonymous identifiers, content submitted for moderation, caption instructions and unpublished drafts, photos selected for cloud caption analysis, text or images submitted for generation or editing, audio submitted for transcription, text submitted for speech, and content transformed into embeddings | AI chat and agents, Event highlight scene understanding and moment selection, caption drafting, embeddings, image generation and editing, moderation, transcription, and text-to-speech. OpenAI API data is not used to train OpenAI models unless Lyra expressly opts in. Caption drafting and Event highlight semantic-analysis requests use no provider application-state storage, but endpoint-specific safety and abuse systems may temporarily retain or permit review of content they flag. |
| Google account identifier and sign-in information; prompts, context, and images submitted when Gemini features are selected; GIF search terms and interaction data for Tenor | Google Sign-In, Gemini AI and image generation, and Tenor GIF search and trending GIFs. Google may act as an independent controller for Google Sign-In and Tenor and as a provider for configured Gemini services. | |
| xAI | Prompts, minimized conversation context, pseudonymous identifiers, and text or images submitted or generated when a Grok option is selected | Optional Grok chat and image-generation features. |
| Foursquare | Place search terms, map area or permitted location, selected place, and place-interaction data | Grounded real-world place search, place information, and place ratings. |
| Spotify | Track and artist search terms, selected music, playback or preview interactions, and Spotify identifiers when a user connects or invokes Spotify | Track search, metadata, embedded previews, and music selection. Spotify independently controls its own service and player data. |
| Resend | Recipient email address, verification or receipt content, message metadata, and delivery or interaction status | School-verification emails and ticket receipts. |
| PostHog | Hashed pseudonymous account identifier, device and app information, sanitized lifecycle and feature events, feature-flag assignments, fully masked SwiftUI session-replay frames, and sanitized device console logs outside sensitive surfaces | Product analytics, lifecycle measurement, masked replay, debugging, experimentation, and feature flags. Analytics and replay are on by default with an in-app opt-out. Lyra masks all text and images before replay frames are enqueued, pauses replay on authentication, private-message, payment, precise-location, and user-media surfaces, disables network capture, and configures PostHog to discard stored client IP data after GeoIP and bot-detection transformations. |
| Sentry | Pseudonymous installation and session identifiers, app and device information, crashes, stack traces, hangs, watchdog terminations, performance traces and profiles, sanitized logs, and error-triggered masked replay or visual diagnostics outside sensitive surfaces | Crash reporting, stability monitoring, performance analysis, debugging, and release quality. Lyra disables routine replay uploads, masks all text and images, pauses replay and visual attachments on authentication, private-message, payment, precise-location, and user-media surfaces, and disables default PII, memory introspection, and network URL capture. |
| Unsplash | Stock-photo search terms, selected image, attribution, device or request information, and link interactions | Stock-photo search and selection for media and flyer templates. |
| LottieFiles | Animation search terms, selected or downloaded animation, device or request information, and link interactions | Search and download of animation templates. |
| Hugging Face | Text transformed into an embedding and limited request metadata when the fallback is invoked | Emergency fallback embedding generation when OpenAI embeddings are unavailable. |
Providers may change their services and policies. Lyra evaluates new vendors before sending personal information and will update this list when a material vendor or use changes.
5.4 User-directed and connected services
When you connect a third-party account, share content externally, add a ticket to a wallet, or direct us to send information to another service, we disclose the information needed to complete your request. The recipient’s privacy policy applies to its independent processing.
5.5 Corporate transactions
We may disclose information in connection with a financing, merger, acquisition, reorganization, bankruptcy, diligence review, or sale of some or all of Lyra’s business or assets. A recipient may use the information only as permitted by this Policy unless it provides notice and any choice required by law.
5.6 Legal, safety, and rights protection
We may preserve or disclose information when we reasonably believe it is necessary to comply with law or valid legal process; respond to regulators or authorities; prevent death, serious injury, fraud, abuse, or a security incident; enforce agreements; or protect the rights, safety, and property of Lyra, users, or others.
5.7 With consent
We may disclose information for another purpose that we explain when requesting your consent.
6. Sale, Sharing, and Targeted Advertising
Lyra does not sell personal information for money, share personal information for cross-context behavioral advertising as those terms are defined by the CCPA, or process personal information for targeted advertising based on activity across unaffiliated businesses.
Disclosures to contracted service providers for analytics, hosting, payments, security, communications, and operation of Lyra are not intended as sales or sharing under the CCPA. If Lyra later introduces advertising or an integration that constitutes sale, sharing, or targeted advertising, we will update this Policy before that processing begins and provide required controls, including a “Do Not Sell or Share My Personal Information” mechanism and recognition of applicable browser-based opt-out preference signals such as Global Privacy Control.
We do not knowingly sell or share the personal information of anyone under 18.
7. Data Retention and Deletion
We keep personal information only for as long as reasonably necessary for the specific purposes below, including providing the Services, protecting users, completing transactions, meeting legal obligations, and resolving disputes. We then delete or deidentify it.
7.1 Retention schedule
| Data category | Normal retention period | Specific purpose |
|---|---|---|
| Account and profile data | While the account is active; deleted from active systems within 30 days after a verified deletion request or account closure | Operate the account, authenticate the user, display the profile, and provide requested features. |
| Public and private User Content | Until the user deletes it or closes the account; active-system deletion ordinarily within 30 days | Display and deliver content to the selected audience and operate social features. Content shared or copied by others may remain in their accounts. |
| Precise device location used for recommendations | Request-scoped only; not retained in Lyra backend feed, AI, analytics, audit, or log records | Provide nearby discovery and requested location functions without creating location history. |
| Rotating Bluetooth proximity tokens and unmatched observations | Tokens expire after 30 minutes and are deleted within 90 minutes; unmatched observations expire within 2 hours. Turning Recognize Hang Outs off purges that account's unmatched observations and tokens sooner. | Privately verify reciprocal time near an opted-in mutual friend without collecting GPS or a stable Bluetooth device identifier. |
| Confirmed Hang Out suggestions | While the account is active, unless the user marks the suggestion incorrect or deletes the account | Show the social suggestion, prevent repeated notices, and honor correction or deletion choices. |
| Raw account-linked ranked-feed requests, pending and realized impressions, outcomes, and supporting learning signals | Up to 90 days; cleared earlier when you use Reset Recommendations, and no new learning is recorded while ranked-feed personalization is off | Rank and diversify recommendations, prevent rapid repeats, measure recommendation usefulness, evaluate ranking changes, and train eligible future ranking models. Aggregated or deidentified statistics that no longer identify an account may be retained longer. |
| AI Memory, inferred preferences, generalized location, and recommendation signals | While the account is active and the memory remains relevant; individual supporting activity signals generally no more than 24 months after collection or last relevant activity; deleted or deidentified from active systems within 30 days after a verified account-deletion or AI Memory deletion request | Remember preferences between sessions, personalize discovery, adapt recommendations, measure recommendation quality, and avoid repetitive or irrelevant suggestions. Old or contradicted inferences may be weakened or removed sooner. |
| Event highlight sources, technical analysis, timelines, and recap files | Numerical analysis is cached while its source media remains available. Superseded private recap files become eligible for deletion once they are seven days old; the latest playable draft and published recaps remain associated with the Event until deletion or source invalidation. Minimal revision metadata may remain for operational measurement. Unreferenced processing files expire within one day. Cloud AI frame payloads and semantic responses are processed for the generation job and are not content-logged. | Analyze scenes and select moments, prepare private Host drafts, support semantic editing, rendering and publication, and enforce source access. |
| Caption instructions, unpublished captions, selected drafting photos, derived scene descriptions, and generated caption candidates | Request-scoped only; Lyra does not persist or content-log them. OpenAI safety and abuse systems may temporarily retain or permit review of content they flag under endpoint-specific controls. | Generate the caption ideas requested by the user, validate output, and protect the service from abuse. |
| Cloud caption-photo preference record | While the account is active and until account deletion; updated when the user enables or renews the choice | Synchronize the account choice across devices, enforce the current disclosure version, and prove that image forwarding is authorized. |
| Device, usage, analytics, and diagnostic logs, including PostHog sanitized events, fully masked session replays and console logs, and Sentry error events, traces, profiles, masked replay buffers uploaded after an error, and redacted visual attachments | Up to 24 months; security logs up to 36 months. Error-triggered Sentry replay buffers that are not uploaded are short-lived on the device. | Operate, secure, debug, measure, and improve the Services. |
| Support and ordinary communications | Up to 24 months after the matter closes | Respond to requests, maintain service history, train support quality, and resolve recurring issues. |
| Tickets, orders, subscription charges, refunds, payouts, tax, and accounting records | Up to seven years after the transaction or longer if tax or financial law requires | Accounting, tax, audits, refunds, chargebacks, payment disputes, and legal compliance. |
| Identity-verification documents | Preferably retained by the verification provider only and deleted under its schedule; if received by Lyra, no more than 30 days after verification unless fraud or law requires longer | Complete identity or age verification and investigate document fraud. |
| Verification result and limited audit trail | While the account is active and up to two years afterward | Maintain trust signals, avoid repeated verification, investigate impersonation, and prove compliance. |
| Safety, fraud, abuse, moderation, ticket-integrity, and chargeback records | Up to five years after case closure; longer for severe incidents, repeat abuse, litigation, or legal hold | Protect users, prevent repeat abuse, investigate incidents, defend claims, and cooperate with lawful investigations. |
| Marketing consent and preferences | While active and up to five years after withdrawal or the last message | Honor preferences and demonstrate compliance with communication laws. |
| Terms, privacy, and recurring-payment consent records | Up to seven years after the account or relevant agreement ends | Demonstrate the terms accepted, authorization of recurring charges, and legal compliance. |
| Privacy-rights requests and verification records | At least 24 months after completion | Respond to requests, prevent fraudulent requests, and demonstrate privacy compliance. |
| Litigation or legal-hold information | Until the hold is released and the applicable limitation period expires | Establish, exercise, or defend legal claims and comply with preservation duties. |
| Deidentified or aggregated information | May be retained without a fixed period if it cannot reasonably be linked back to a person and is not reidentified | Research, statistics, safety analysis, and service improvement. |
These periods are maximum guidelines, not a requirement to keep information for the full period. We may delete information sooner. We may adjust a period based on the volume, nature, and sensitivity of the information; the risk of harm; technical constraints; and legal requirements. If a law requires a different period, the legally required period controls.
7.2 What happens after a deletion request
After verifying a deletion request, Lyra will ordinarily erase or deidentify covered personal information in active systems within 30 days. Where applicable law permits a longer response period, we may use that period if reasonably necessary and will provide notice. We will direct service providers and contractors to delete the information as required by law.
Encrypted backups rotate out under our normal backup cycle, generally within 90 days. Until deletion, backup information is isolated from ordinary use and accessed only for security, integrity, or disaster recovery. If a backup is restored, applicable deletion requests will be reapplied.
We may deny or limit deletion where an exception applies, including to complete a transaction requested by you; provide a warranty or recall; detect security incidents or fraud; protect safety; exercise free-speech or other legal rights; comply with tax, accounting, court, or regulatory obligations; maintain evidence for disputes; or use information internally in a way reasonably aligned with your expectations and permitted by law. We will explain the basis unless prohibited from doing so.
Deletion of your Lyra account does not cancel subscriptions billed by Apple, Google, or another provider. It also cannot delete copies another user made or content independently controlled by a Host, venue, or external service.
If you request deletion or reset of AI Memory without deleting your account, we will delete or deidentify the account-linked inferred-preference profile and begin rebuilding personalization only from activity occurring after the reset, except for preferences you choose to retain and limited records that must remain for safety, fraud prevention, legal compliance, or to honor your opt-out and deletion choices. Resetting AI Memory does not delete ticket, transaction, tax, safety, or other information retained independently for the purposes and periods listed above.
8. Your Privacy Rights and Choices
Depending on where you live, you may have the right to:
- know whether and how we process your personal information;
- access or obtain a portable copy of personal information;
- correct inaccurate information;
- delete information, subject to exceptions;
- restrict or object to certain processing;
- withdraw consent prospectively;
- opt out of sale, sharing, targeted advertising, or certain profiling;
- limit certain uses of sensitive personal information;
- receive information about automated decision-making and request human review where required;
- appeal our decision concerning a privacy request; and
- complain to a privacy or data-protection authority.
You can update certain information and permissions in your Lyra settings. You may submit a request through our Privacy Request Portal, email support@lyraplus.com, or use another method required for your jurisdiction.
We will verify requests using information appropriate to the request’s sensitivity, such as account access, email or phone confirmation, transaction information, or signed authorization. We will not ask for more information than reasonably necessary. Authorized agents may submit requests where permitted, subject to proof of authority and identity verification.
We will respond within the period required by applicable law. For covered California requests to know, access, delete, or correct, this is generally within 45 days, with an additional 45 days when reasonably necessary and permitted after notice. We do not discriminate against users for exercising privacy rights, although deleting information may make features that require it unavailable.
8.1 EEA and UK rights
If the GDPR or UK GDPR applies, you may exercise the rights of access, rectification, erasure, restriction, portability, objection, and withdrawal of consent. You may object to processing based on legitimate interests and to direct marketing at any time. You may lodge a complaint with the data-protection authority where you live or work or where an alleged violation occurred.
If Lyra engages in a decision based solely on automated processing that produces legal or similarly significant effects, we will provide the notice, safeguards, explanation, and human-review options required by law. Lyra’s ordinary Event and content recommendations are not intended to produce such effects.
8.2 California privacy notice
For purposes of the CCPA, as amended by the CPRA, the categories of personal information Lyra may have collected during the preceding 12 months include:
| CCPA category | Examples | Sources | Business or commercial purposes | Categories of recipients |
|---|---|---|---|---|
| Identifiers | Name, username, email, phone, IP address, account and device identifiers | You, devices, other users, providers | Accounts, tickets, communications, security, personalization | Hosting, communications, verification, security, Event partners as needed |
| California Customer Records information | Contact, billing, payment-token, and identity information | You, payment and verification providers | Transactions, verification, support, compliance | Payment, verification, tax, support, professional advisers |
| Protected-classification information | Age, and characteristics voluntarily disclosed in a profile or content | You, verification provider | Eligibility, safety, user-selected profile and social features | Verification provider; users according to your settings |
| Commercial information | Purchases, subscriptions, tickets, transfers, resale, Event history | You, Hosts, payment and app-store providers | Transactions, support, recommendations, accounting, fraud prevention | Payment, app-store, analytics, security, Hosts and venues as needed |
| Internet or electronic activity | App usage, searches, views, clicks, interaction, diagnostic data | Devices, cookies, SDKs | Operate, secure, measure, personalize, improve | Hosting, analytics, diagnostics, security |
| Geolocation | Approximate and permission-based precise location | Device, IP address | Nearby discovery, requested location features, fraud and security | Hosting, mapping, analytics or security providers as applicable |
| Audio, electronic, visual, or similar information | Photos, videos, stories, Memories, support recordings | You, other users | Social features, Event highlight analysis and semantic editing, support, safety, moderation | Hosting and media processing, AI processors for highlights, users within the selected audience, moderation and support providers |
| Professional or employment-related information | Host role, business, authorized representative, Event operations | Hosts and business partners | Host onboarding, Events, payouts, tax and compliance | Payment, tax, verification, Event, professional advisers |
| Inferences | Event, music, social, and content preferences; risk or recommendation signals | Activity and information described above | Recommendations, discovery, safety, fraud prevention | Recommendation, analytics, safety and security providers |
| Sensitive personal information | Precise location, account credentials, government ID data, financial or payout data, private-message contents | You, device, verification and payment providers | Requested services, verification, transactions, safety and security | Providers performing those specific functions |
Lyra discloses these categories for the business purposes described in Sections 3 and 5. Lyra has not sold personal information or shared it for cross-context behavioral advertising during the preceding 12 months. Lyra does not use or disclose sensitive personal information for purposes requiring a right to limit under the CCPA. If those practices change, we will update this disclosure and provide required rights before the change takes effect.
9. Cookies, SDKs, and Device Permissions
Lyra and its providers use essential technologies to authenticate users, remember settings, prevent fraud, secure transactions, balance traffic, and maintain the Services. With consent where required, we may use analytics and measurement technologies to understand acquisition, feature use, performance, and errors.
The Lyra app may request device permissions for location, Bluetooth, camera, photos, microphone, notifications, contacts, or tracking. We will request them in context and use the resulting information for the stated feature. Bluetooth is requested only after you turn on Recognize Hang Outs. You can change permissions in device settings, although doing so may disable the related feature.
Our website provides a Cookie Settings control where required. Browser settings may also block cookies. Lyra will recognize legally required opt-out preference signals when applicable. We do not respond to legacy “Do Not Track” signals that do not communicate a legally recognized preference.
10. International Data Transfers
Lyra is based in the United States, and information may be processed in the United States and other countries where our providers operate. Those countries may have different data-protection laws.
When the GDPR, UK GDPR, or similar law requires a transfer mechanism, we use appropriate safeguards such as an adequacy decision, the European Commission’s Standard Contractual Clauses, the UK International Data Transfer Addendum or Agreement, or another valid mechanism. We also assess transfer risks and apply supplementary technical or contractual measures where appropriate. You may request information about the relevant safeguards by contacting us.
11. Security
We use administrative, technical, and physical safeguards designed to protect personal information, including access controls, encryption in transit and at rest where appropriate, logging, secure development practices, vendor review, backups, incident response, and employee confidentiality requirements.
No system is completely secure. Protect your password and devices, do not share ticket barcodes or login codes, and contact support@lyraplus.com if you suspect unauthorized activity. Where required by law, we will notify affected individuals and authorities of a qualifying personal-data breach.
12. Age Requirement
Lyra+ is for people age 18 and older. We do not knowingly collect personal information from anyone under 18. If you believe a person under 18 has provided information, contact support@lyraplus.com. We will investigate and delete the information where required.
Hosts may impose a higher age requirement for an Event. Identity or age verification for Event admission is separate from this platform age requirement.
13. Third-Party Services
The Services may link to or integrate with Hosts, venues, payment providers, app stores, maps, social networks, digital wallets, and other third parties. When a third party independently determines why and how it processes information, its privacy policy—not this Policy—governs that processing. Review third-party policies before directing Lyra to connect or disclose information.
14. Changes to This Policy
We may update this Policy to reflect changes in the Services, vendors, law, or data practices. We will post the updated version and change the “Last updated” date. If a change materially affects your privacy rights, we will provide additional notice and obtain consent where required before the change takes effect.
15. Contact and Complaints
For privacy questions or requests, contact:
Lyra Plus, Inc.
Attn: Privacy
1111B South Governors Avenue, Suite 59189
Dover, Delaware 19904, United States
Email: support@lyraplus.com
Request portal: https://lyraplus.com/privacy-request
If you are in the EEA or UK, you may also complain to the data-protection authority where you live or work or where you believe a violation occurred. We encourage you to contact us first so we can try to address your concern.