Privacy Policy

This notice describes the current Event Master pilot. Event Master is built around event discovery and consent-based social interaction at real venues. Going, check-in and temporary presence are separate concepts.

• Account and profile: account identifiers, display name, profile photo, bio, date of birth, social intent and privacy choices.
• Event activity: events you mark Going, check-in or presence state when you choose to verify it, and reviews you submit.
• Social and messaging: event-chat messages, Say Hi requests, accepted connections and private messages.
• Safety: blocks, reports, moderation decisions and limited evidence needed to review abuse or enforce account restrictions.
• Technical operation: technical information used for security, reliability, troubleshooting and abuse prevention.

Event Master does not use Going as proof that you are physically present. A location check happens only when you start a feature that asks to verify presence and your browser permits location access.

The device location sample, accuracy and timestamp are sent to the server to evaluate whether the sample is recent, sufficiently accurate and inside the event venue boundary. The persisted presence proof contains the event and venue, verification times, status and coarse distance/accuracy buckets — not your raw device latitude or longitude.

Current GPS presence proofs are short-lived (about ten minutes). Showing yourself to other people as Here now is a separate privacy choice. Ordinary users are never given raw coordinates through the presence model.

Some events or trust features may use Stripe Identity. Stripe may process an identity document and a matching selfie or liveness information for the verification flow.

Event Master stores the verification status, provider session reference, verified date of birth, relevant verification/expiry/revocation times and redaction metadata. The Event Master application data model does not store copies of your identity document or selfie/video.

After a successful verification Event Master requests redaction of the Stripe verification session. Provider-side processing and retention are also governed by the provider's own systems and terms.

Visibility is context-dependent and privacy-first. Aggregate Going or Here now counts can exist without exposing your identity. Profile or presence details are shown only where the relevant product rules and your visibility settings allow them. Blocking also restricts interaction and visibility where supported.

Temporary presence data is designed to expire. Other records are kept only for the product, security, integrity or moderation purpose they serve and are minimized or removed under Event Master's retention rules.

You can use Delete account from Profile. Deletion deactivates access, removes temporary location proofs, revokes active access and identity-verification state, and cleans or minimizes account-linked data. Shared conversation history, anonymized reviews/messages, or safety and moderation evidence may be retained where needed for other participants, integrity, abuse review or enforcement.

Event Master relies on service providers to host and operate the application and may use specialist providers for features such as identity verification. Those providers may receive information involved in the service they perform, and their handling is also governed by their applicable terms and privacy notices.

• Control browser location permission and start presence verification only when you choose to use a location-gated feature.
• Choose whether your temporary presence is visible to other members where that setting is offered.
• Use Block and Report controls for unwanted interaction or safety concerns.
• Delete your account from Profile.

During the Prague pilot, privacy requests can be raised through the operator or support contact channel provided with your access to Event Master. Dedicated operator and privacy-contact details will be published before broader public availability.

We may update this notice as the pilot, providers or product behavior changes. Material privacy changes should be presented clearly and, where required, handled separately from contractual acceptance.

See also the Terms of Use and Safety & photo policy.