Privacy Policy

Effective date: August 10, 2026

This Policy explains how FetePass365 handles personal information across the FetePass365 mobile app, fetepass365.com, fetepass365.online and connected ticketing, event, payment, payout and check-in services.

1. Who We Are and What This Policy Covers

FetePass365 provides an event-discovery and ticketing marketplace for customers, event organizers, check-in staff and administrators. This Policy applies when you use the FetePass365 iOS app, fetepass365.com, fetepass365.online, organizer tools, ticket checkout, QR ticketing and scanning, direct-deposit onboarding, communications, and other services that link to this Policy (collectively, the “Services”).

FetePass365 is responsible for personal information under its control. Event organizers may also be independently responsible for information they collect or receive for their events. An organizer’s own privacy practices may apply in addition to this Policy.

2. Information We Collect

The information we collect depends on how you use the Services.

• Account and profile information, such as your name, username, email address, mobile number, account role, profile photo, password hash, email-verification status and account preferences.
• Social sign-in information from Google or Facebook, such as a provider account identifier, name, email address and email-verification status. We do not receive your Google or Facebook password.
• Organizer information, such as business or public organizer name, biography, contact details, website, social-media links, verification and approval status, submitted events, staff access information, sales, payout status and, where enabled, identity or business-verification information.
• Event and venue information, such as event descriptions, dates, recurrence schedules, ticket tiers, prices, quantities, extra services, FAQs, flyers, galleries, venue details and organizer contact information. Published event and organizer information is intended to be public.
• Order and attendee information, such as billing/contact details, ticket holder name, event, ticket type, quantity, price, taxes, fees, discounts, order and ticket identifiers, QR ticket token, payment status, refund status and check-in history.
• Payment and payout information. Stripe processes card payments and organizer direct-deposit onboarding. FetePass365 receives transaction, status, fee, payout and limited payment-method details, but does not store complete card numbers or complete bank-account credentials.
• Communications, including support requests, organizer-to-attendee announcements sent through FetePass365, email-delivery information and your communication preferences.
• Device and usage information, such as IP address, device and operating-system type, app version, session and security logs, crash or diagnostic information, pages or features used, referral information, cookie identifiers and approximate location derived from your device or search choices.
• Camera, photos and location information when you choose to use QR scanning, upload a profile picture, event flyer or gallery image, or request nearby events. The app requests device permission before accessing protected device features.

3. How We Collect Information

• Directly from you when you register, edit a profile, create an event, purchase or transfer a ticket, contact support, submit verification information, or configure organizer payouts.
• Automatically from the app, websites, cookies, server logs and security tools when you use the Services.
• From event organizers, venues, check-in staff and purchasers where they provide attendee or event information.
• From service providers such as Google, Meta/Facebook, Stripe, hosting, email-delivery, analytics, fraud-prevention and technical-support providers, according to your choices and their policies.

4. How We Use Information

We use personal information only for identified and reasonable purposes, including to:

• Create, verify, authenticate, secure and administer accounts and roles.
• Publish and synchronize events, organizer profiles, venues, ticket availability and public event content between the app and websites.
• Process orders and payments, calculate taxes and Processing Fees, issue invoices and QR tickets, prevent overselling, manage refunds, and maintain required transaction records.
• Validate tickets, prevent duplicate or unauthorized entry, perform check-in and provide real-time sales and attendance statistics to authorized organizers and staff.
• Approve organizer applications, verify organizer or payout eligibility, manage direct deposits and administer marketplace safety.
• Provide customer support, service notices, ticket and event updates, organizer approval notices, security alerts and material policy updates.
• Personalize event discovery, remember preferences, improve accessibility, diagnose errors, measure performance, protect the Services and detect fraud or misuse.
• Meet legal, tax, accounting, regulatory, insurance, dispute-resolution and enforcement obligations.

5. Consent and Your Choices

We seek meaningful consent by explaining important collection, use and disclosure practices in this Policy and at relevant points in the Services. By providing information or using an optional feature, you consent to the practices reasonably necessary to provide that feature, subject to applicable law.

You may decline optional device permissions, social sign-in, marketing messages or optional profile fields. Some information is necessary to create an account, complete a purchase, issue a valid ticket, comply with law or provide organizer and check-in functions. Withdrawing consent may limit or prevent those functions.

6. Google and Facebook Sign-In

If you choose Google or Facebook sign-in, you are redirected to that provider to authenticate. The provider returns a limited identity response to the FetePass365 server. Provider client secrets stay on the FetePass365 server and are not embedded in the mobile app.

You can disconnect or review third-party access through your Google or Facebook account settings. The provider’s privacy policy also applies to information it processes during authentication.

7. Payments, Orders and Organizer Payouts

Payments are processed by Stripe and connected payment infrastructure. Stripe receives payment and fraud-prevention information needed to complete the transaction. FetePass365 receives confirmation, amount, currency, limited payment-method details, transaction identifiers and status information.

Organizer direct-deposit onboarding is completed in a Stripe-hosted experience. Stripe may collect identity, business and bank information to verify an organizer and send payouts. FetePass365 receives onboarding, eligibility and payout status but is designed not to store complete bank-account credentials.

Orders from the app and website are recorded in a unified private FetePass365 order database so tickets, invoices, refunds, QR validation and account history remain synchronized.

8. QR Tickets, Scanning and Attendance

Each issued ticket may contain a unique QR token linked to the applicable order and event. Authorized organizers and check-in staff may scan that token to determine whether a ticket is valid, already used, cancelled, refunded or for a different event.

Check-in records, including scan time, validation result and aggregate attendance statistics, are retained as operational event records and may be visible to the applicable organizer, authorized staff and FetePass365 administrators.

9. When We Share Information

We do not sell personal information. We may disclose it as reasonably necessary to:

• Event organizers and authorized check-in staff, for attendee management, event communications, ticket support, safety and entry. Organizers do not receive payment-card or complete bank information.
• Service providers that support payment processing, payouts, authentication, hosting, storage, email, communications, analytics, security, fraud prevention, customer support and professional advice. They are permitted to process information for contracted services and legal obligations.
• Government, regulators, courts, law enforcement or other parties where required or permitted by law, to enforce agreements, protect rights and safety, investigate fraud or respond to lawful process.
• A successor or potential purchaser in a merger, financing, reorganization, sale or transfer of all or part of the business, subject to appropriate confidentiality and legal safeguards.

10. Public Information and Organizer Responsibilities

Published events, venue profiles and organizer profiles may be visible in the app, on the websites, in search results and when users share links. Do not publish sensitive personal information in public event descriptions, FAQs, flyers, galleries, biographies or social links.

Organizers must use attendee information only for legitimate event administration, safety, support and communications permitted by law and FetePass365 terms. Organizers are responsible for their own notices, consents, staff access and compliance where they independently control attendee information.

11. Email, Notifications and Marketing

We send transactional and service communications such as verification codes, receipts, invoices, tickets, event changes, refund information, organizer decisions, check-in notices, security alerts and material policy updates. You may not be able to opt out of messages necessary to provide a purchased service or protect an account.

Where required, we obtain consent for promotional email, push notifications or similar marketing. You can use the unsubscribe method in promotional email or device settings for push notifications. An organizer announcement is sent through FetePass365 without exposing the attendee list to the organizer.

12. Cookies, Analytics and Device Technologies

The websites and connected services may use essential cookies and similar technologies for login, checkout, fraud prevention, preferences, performance and security. Optional analytics or marketing technologies should be used according to the choices presented in the applicable cookie notice.

The app may use secure device storage for session tokens and may process a notification token if you enable push notifications. You can manage cookies in your browser and app permissions in iOS Settings, although blocking essential technologies may prevent login or checkout.

13. Retention

We retain personal information only as long as reasonably necessary for the purposes described in this Policy, including to maintain accounts, provide valid tickets, complete event and payout operations, resolve disputes, prevent fraud, enforce agreements and satisfy legal, tax, accounting and regulatory requirements.

Retention periods vary by record type. Public profile content may remain until removed or the account is deleted. Transaction, tax, refund, payout, fraud and check-in records may be retained after account deletion where required for legitimate business or legal purposes. Information is deleted, anonymized or securely disposed of when no longer required.

14. Security and Privacy Incidents

We use administrative, technical and physical safeguards appropriate to the sensitivity of the information, including encrypted network connections, access controls, server-side secrets, secure session storage, role-based authorization, payment-provider tokenization, backups, monitoring and staff access limitations.

No system is completely secure. If a breach of security safeguards creates a real risk of significant harm, we will report it to the appropriate privacy regulator, notify affected individuals and keep required records as required by applicable law.

15. Processing Outside Canada

FetePass365 and its service providers may process or store information in Canada, the United States or other countries. Information in another jurisdiction may be subject to that jurisdiction’s laws and lawful access by its authorities. We use contractual, organizational and technical measures appropriate to the information and service.

16. Your Privacy Rights

Subject to applicable law and permitted exceptions, you may:

• Request access to the personal information we hold about you and information about its use and disclosure.
• Request correction of inaccurate or incomplete personal information.
• Withdraw consent for optional processing, unsubscribe from promotional messages or change device permissions.
• Edit your profile or request account deletion through available account tools or by contacting us.
• Ask a question or challenge our compliance with this Policy. We may need to verify your identity before completing a request.

17. Children and Age-Restricted Events

The Services are not directed to children under 13. If you are under the age of majority where you live, use the Services only with permission and supervision from a parent or legal guardian where required. Organizers may impose and enforce event-specific age restrictions. If we learn that personal information was collected from a child without required consent, we will take reasonable steps to delete it.

18. Third-Party Links and Services

Events and profiles may link to organizer, venue, social-media, map or other third-party sites. FetePass365 does not control those third parties and this Policy does not govern their practices. Review their privacy policies before providing information.

19. Changes to This Policy

We may update this Policy as the Services, providers or legal requirements change. We will post the revised Policy with a new effective date and provide additional notice when a change is material. Continued use after the effective date is subject to the updated Policy, but we will seek additional consent where required by law.

20. Contact Us and Complaints

For privacy questions, access or correction requests, consent withdrawal, account deletion or complaints, contact the FetePass365 Privacy Officer at support@fetepass365.com or through https://fetepass365.com. Please write “Privacy Request” in the subject line.

We will investigate and respond to privacy complaints. If you are not satisfied, you may contact the Office of the Privacy Commissioner of Canada or the applicable provincial privacy regulator.