Privacy

EventPark Privacy Policy

Effective date: May 13, 2026. This text is a pre-launch privacy draft based on the currently documented functionality of the EventPark mobile platform and should be updated as actual data flows, third-party services, and store listing details are finalized.

1. Scope

This Privacy Policy explains how information may be handled in connection with the EventPark mobile platform and its related landing page. EventPark supports flows such as event discovery, registration, agenda tracking, networking, messaging, QR-based check-in, organizer operations, and planning workspace.

This text is based on the currently described product functionality. If new modules or integrations are added to the platform, this policy should be updated accordingly.

2. Information we may collect

While using the platform, the following categories of information may be processed:

  • Account and profile information: name, professional details, about section, LinkedIn, Instagram, website or blog links, and organizer profile information.
  • Event and attendance information: events you joined, registration details tied to free/paid/private event status, ticket or join status, and check-in status.
  • QR and entry information: event QR code, organizer scan result, verification, and check-in updates.
  • Session and content information: session views, agenda-related usage, text notes, session notes, feed posts, image posts, and note-sharing flows.
  • Networking and communication information: connection requests, direct message content, conversation history, Q&A questions, and moderation status.
  • Organizer and workspace information: created events, speaker and session data, notification history, tasks, checklist items, team roles, workspace invites, and assignment data.
  • Support and safety information: report-a-problem submissions, event report or complaint data, support requests, and review data related to abuse or policy violations.
  • Technical and device information: device, app usage, diagnostic, and log-type data used for security, reliability, and issue investigation.

3. How we may use information

  • To create accounts, authenticate users, and provide profile functionality.
  • To power event discovery, event detail, joining, and agenda/session experiences.
  • To keep networking, messaging, public profile view, and community interaction flows active.
  • To provide organizers with event creation, session/speaker management, QR check-in, notification, and PDF report generation capabilities.
  • To manage task, checklist, team, and invite flows inside Planning Workspace.
  • To respond to support requests, evaluate reports, and reduce safety, fraud, and abuse risks.
  • To improve platform performance, reliability, and usability.

4. Sharing of information

EventPark may share information or make it visible in the following situations:

  • User-visible profile information may be shown to other users within networking and public profile functionality.
  • Organizers and their teams may access information necessary for event joining, attendee lists, check-in status, workspace assignment, and event operations.
  • Content you submit in messaging, Q&A, feed, and other user-generated content functions may be visible to other users within the relevant product flow.
  • Information may be shared with service providers used for payments, hosting, analytics, push notifications, maps, or other technical infrastructure for service delivery purposes.
  • Information may be disclosed when required for law, legal process, regulatory requests, safety investigations, or protection of rights.
  • If the business structure changes, information may be transferred in connection with a merger, sale, or asset transfer.

5. Data retention and deletion

Information may generally be retained for as long as needed to support accounts, event operations, organizer reporting, safety needs, and legal obligations. Retention periods may differ across data categories.

The mechanism for account closure, deletion requests, or removal of certain information should be finalized before launch in line with the actual data operations flow. A working privacy contact or data request channel should be added before App Store and Google Play submission.

6. Security

EventPark aims to apply appropriate technical and organizational measures to protect personal and sensitive information from unauthorized access, alteration, loss, or misuse. However, no internet transmission or electronic storage system can be considered fully risk-free.

7. Children's privacy

EventPark is intended as a general event operations and engagement platform and is not presented as a service directed to children. If age restrictions or parental consent mechanisms are legally required, they should be defined separately before launch.

8. International use and third-party services

If third-party technologies such as hosting, push notifications, analytics, payments, or maps are added to the app, their data handling should be accurately reflected in this policy and in store disclosures.

Apple requires that App Store listings accurately disclose the data collection practices of the app and integrated third-party partners. Google Play also requires privacy policies to clearly describe what data is collected, how it is used, how it is shared, and the retention/deletion approach.

9. Policy updates

This Privacy Policy may be updated from time to time. When material changes are made, an updated effective date should be shown and users should be informed through the app or store listing where appropriate.

10. Contact

In the final pre-launch version, this section should include the developer or company name, a privacy point of contact, or a data request mechanism. That information has not yet been provided in this draft.

Back to landing page