Privacy Policy

This Privacy Policy explains how Pàdéyá collects, uses, shares, and protects personal information when you use our marketplace for events, ticketing, hosting, fan identity, and related services. We do not sell your personal data as a standalone product.

Related documents: Cookie Policy, Terms, and Safety.

Pàdéyá is a technology platform and marketplace for event discovery, ticketing, host tools, fan identity, support, and related services.

Unless expressly stated otherwise:

• Pàdéyá is not the organizer, host, promoter, venue, performer, sponsor, security provider, transport provider, or food/drink provider for events listed by third-party hosts.
• Hosts are independent organizers. They are responsible for listing accuracy, event safety, venue readiness, permits, crowd control, age restrictions, accessibility arrangements, emergency planning, and compliance with applicable rules.
• Hosts are responsible for communicating event changes, cancellations, entry rules, venue rules, and refund terms where those apply to their events.
• Fans and buyers are responsible for reviewing event details, policies, and requirements before purchasing or attending.
• Pàdéyá may moderate, restrict, remove, or suspend listings or accounts where safety, fraud, abuse, legal, or platform-risk concerns arise.

Related: Terms, Ticket Policy, Refund Policy, Safety, and Community Guidelines.

When you register or update an account, we may process:

• Name, email, phone (when provided), and login credentials
• Profile preferences, notification settings, and role context (fan/host)
• Security signals such as session and device information

Guest buyers provide contact and purchase details needed to complete checkout, deliver tickets, prevent fraud, and support refunds — even without creating an account first. Claiming tickets later may link that order history to an account you control.

We process order references, ticket types, amounts, statuses, check-in state, and related fulfilment records so tickets can be issued, scanned, transferred (where enabled), and supported. Tickets are issued only after verified payment or confirmed free reservation.

If you buy for someone else or enter attendee fields, we process the names and details you supply so hosts can manage entry and so we can deliver access. Provide only information you are authorized to share.

Hosts provide business/profile details, event content, team member invites, payout-related information, and operational records needed to run Event Studio, check-in, merch, Ambassadors, sponsorships, and finance tools. Team tools are designed to limit exposure of buyer secrets at the door.

Fan Passport defaults toward private controls. Public or directory visibility is based on settings you choose. Public serializers are designed not to expose email, phone, payment amounts, hidden venues, or locked Vault media.

Fan Connect is optional. Discovery and connection requests depend on your Connect settings. Shared context uses public-safe signals (such as shared upcoming events you both surface) — not private ticket internals, payment data, or locked content. Removing or blocking a connection limits further messaging according to product rules.

Message content is processed to deliver conversations between permitted participants. Notifications use limited preview copy. Reports you submit (abuse, fraud, safety) are reviewed by authorized staff. Do not include passwords, OTPs, full card numbers, or QR secrets in reports.

Event location fields may be partially hidden until purchase or a host reveal rule. Optional features such as nearby discovery or “near me” may use approximate location only with your consent or device permission. You can decline device location; some discovery features will be limited.

Card and checkout data are handled by payment partners.Pàdéyá stores payment references and statuses needed for orders, refunds, payouts, and fraud prevention — not full card PANs for you to paste into chats. Never send payment secrets through messaging.

We send transactional notices (tickets, claims, security, support) and, where you opt in, product updates. Control preferences in account settings where available.

Support conversations include the details you submit so we can help with orders, accounts, and reports. Keep sensitive secrets out of ticket bodies; share order references instead.

Authorized staff may access operational records to review reports, prevent fraud, handle refunds, and keep the Platform safe. Internal staff notes are not shown to other users. We do not publish private message bodies, QR secrets, or payment secrets on public pages.

We use cookies and similar browser storage (including localStorage and sessionStorage) for sign-in state, security, preferences, ambassador referral attribution, and privacy-conscious analytics where enabled. Sign-in is stored in localStorage and sent via API Authorization headers—not traditional login cookies. Details are in the Cookie Policy.

We share personal data only as needed to operate the Platform, including:

• Hosts / door teams: purchase and attendee details required to run entry, fulfilment, and legitimate event operations — not unrestricted dumps of payment secrets or QR secrets.
• Processors: payment, hosting, email/SMS delivery, analytics, and similar vendors under contracts that limit use.
• Legal / safety: when required by law or necessary to protect users, rights, or the Platform.

• Update profile, Passport, and Connect privacy settings.
• Manage notification preferences where offered.
• Request access or deletion via Support where applicable under local law and operational limits (for example, records we must keep for fraud, taxes, or disputes).

We retain personal data as needed to provide services, resolve disputes, meet legal and financial obligations, and maintain security. Retention periods vary by record type (accounts, orders, support, audit).

We apply access controls, monitoring, and operational practices designed to protect personal data. No method of transmission or storage is perfectly secure. Report suspected account compromise through Support promptly.

Privacy questions: Support or Contact. For safety emergencies, contact local authorities first, then report on-platform via Report.