Experience Club US App Privacy Policy

Effective date: November 4, 2026

Experience Club US ("we", "us") operates the Experience Club US app. This policy explains how we handle information when you use the Experience Club US app. For privacy questions, contact contact@experienceclubus.com or write to Experience Club US, 4040 NE 2nd Ave, Miami, FL 33137.

Information we use

Account and identity. When you sign in through Google, Apple or LinkedIn, we use the account identifiers and available identity information supplied through that sign-in, such as your name, email and profile photo. Managed accounts can also sign in with an email address and password when email sign-in is enabled. Firebase Authentication processes those credentials; passwords are not stored in app profile documents or remote configuration. We use verified email addresses and approved account bindings to identify your club contact and check membership. The app does not ask for your Google, Apple or LinkedIn password. Information you supply to verify an additional email address, activate membership, recover access or contact support is used for that process.

Profile and preferences. We store your professional name and the profile information you choose to supply, such as a photo, company, role, biography, interests, social links and website. Birthdate is optional and private. We also store profile-discovery and attendance-visibility choices, blocked profiles, notification preferences and other account settings. Your login email and private identity/membership bindings are not shown in member discovery.

Events and membership. We use club contact and eligibility information, registrations, cancellations and attendance/admission information to provide member access, event registration, admission credentials and event updates. Authorized staff can access information necessary for event admission. When staff create a walk-in attendee record, the app receives the attendee’s name, email address, phone number and any supplied title/company details. Club membership and business records are managed separately from your app profile.

Search and operational activity. The app sends event, member and staff search input to its backend and business-record services as needed to return results. It records registrations, sharing preferences and inbox-read state needed to provide those features.

Optional nearby location. Eligible members can separately opt into nearby sharing and grant device/browser permission. If enabled, the app obtains precise location with a timestamp and accuracy estimate while Home is visible and the app is in the foreground. The service stores the latest accepted observation to find other eligible members who also share, using a 50-metre matching radius. Other members see eligible profile information and observation freshness, not your raw coordinates or an exact distance. A result describes a last observed location and does not guarantee that someone is physically present.

The app does not collect location in the background or maintain a movement trail. A last accepted observation can remain eligible for nearby results for up to two hours after its refresh unless sharing/access is revoked sooner. Expired results are excluded even if scheduled physical cleanup is delayed. Failed or inaccurate fixes do not extend presence. You can pause sharing in Profile → Privacy. Withdrawing device permission stops new collection when detected, but explicitly pausing sharing is the direct way to revoke existing app sharing. Device permission alone does not opt you into sharing.

Notifications and device/security information. With mobile notification permission, we register a push-delivery token and the device's time zone to send operational event updates and optional reminders, apply quiet hours and open the appropriate app screen. We maintain inbox items, read state and delivery observations. Authentication, App Check and hosting services also process technical request, device and security information to operate the service and prevent unauthorized access.

App diagnostics. In iOS and Android versions with diagnostics enabled, we use Google Firebase Crashlytics to investigate crashes, errors and freezes. Reports can include technical details about the error, where it occurred in the app, the app's state and version, device and operating system information, and identifiers for the app installation and session. Reporting starts automatically and can occur before sign-in.

In those versions, we also use Google Firebase Performance Monitoring to measure how quickly the app opens, restores a returning session and loads the Events list. It can also collect device and network information, resource usage, and network request measurements such as the request address, response time, status and size. The network measurements exclude query parameters and request or response contents. Google uses the IP address to estimate the country associated with a measurement. This estimate is separate from the optional precise location used for nearby sharing.

We use these reports to find and fix problems and improve app reliability and speed. We send the reports to Google Firebase for processing. Our app's custom diagnostics use technical error categories and fixed timing labels. They exclude member profile details, account identifiers, invitation links and precise location.

Photos and camera. We receive a profile photo you choose to upload or import. Authorized event staff may use the camera to scan an admission QR; the admission code is processed for check-in. The app does not upload a camera video stream as part of QR scanning.

Why and with whom we use information

We use information to authenticate accounts, manage app profiles and membership access, provide events, admission, member discovery and nearby features, deliver notifications, handle support and deletion requests, and protect the service.

Eligible member viewers may see profile and attendance information according to your visibility settings and the app's access rules. Nearby requires separate mutual sharing. Authorized club operators and event staff can access information needed for their operational roles. Hiding attendance from member previews does not remove the registration or the identity needed by admission staff.

We use Google Firebase/Google Cloud for app identity, protected application data, server operations, hosting, integrity checks and mobile push infrastructure; Apple services support Apple sign-in, device integrity and iOS push delivery. Notion holds club business/contact, membership and event records. Sign-in providers and our configured transactional mail service process the information needed for their functions.

External websites and social/contact links open services with their own privacy practices. Newsletter signup takes place on the club website and is separate from app notifications. The app source does not implement advertising identifiers, ad networks or a cross-app advertising tracking flow.

Your choices and deletion

You can edit your profile, remove optional information, manage discoverability and attendance visibility, pause nearby sharing, manage notification choices, and use device settings to manage permissions. Some member features depend on eligibility and the information required to provide them.

You can request deletion from Profile → Membership & account → Delete account after reauthentication with a connected sign-in provider. The app removes app-owned profile data, personal assets, interests, settings, identity bindings, inbox/push registrations and authentication as its deletion process completes. Temporary cleanup/status-writeback identifiers can remain while required work is pending; the app reports pending or failed work rather than claiming completion.

Deleting the app account does not automatically delete Notion club business/contact records, cancel membership or an external booking, remove club registration/attendance records, or unsubscribe a separate website newsletter. Contact us for requests concerning those records.

Retention, security and transfers

To open returning sessions faster, the app may keep a disposable snapshot of your own profile and photo, last-known membership display and Home content previews on your device or browser. A snapshot is used only while it is less than 24 hours old; expired snapshots are discarded when next read. Local bytes may remain until the app next accesses storage or you clear app/browser data. The snapshot is tied to your signed-in account and does not grant membership or authorize actions. It excludes other members’ nearby identities or coordinates, tickets and private offer access details. The app refreshes from the server and clears these snapshots on sign-out, account switching, account deletion or confirmed loss of access. Local storage can also be removed by clearing app/browser data.

App account data is maintained to operate your account until changed or deleted, subject to the deletion process above. Nearby eligibility expires within two hours of the last accepted observation, with a scheduled cleanup process. Inbox items expire after 90 days; related active-event observations can extend through the event. Temporary operations are removed when their required work is completed. These are application rules, not promises of simultaneous erasure from every provider's logs or backups. Operational/security logs and managed backups follow the retention settings of the services that process them. Separate club records are retained as needed to administer membership, events, recordkeeping and related requests. Contact us to ask about a particular record or request its deletion.

Google Firebase may process diagnostics in the United States and other countries where it operates. Crashlytics keeps crash traces and associated identifiers for 90 days before starting removal. Performance Monitoring keeps events associated with IP addresses for 30 days and installation-associated and de-identified performance data for 60 days before starting removal. Firebase retains diagnostics separately from your app account under these service retention periods.

We use authenticated access, server-side authorization, app-integrity checks and encrypted transport. These controls do not guarantee absolute security. The app backend and protected app data use Google Cloud services in the United States. Identity, business-record, security and email services may involve processing in other countries. Contact us with questions about processing locations.

Age, privacy requests and updates

The app is intended for adults aged 18 and older. If you believe someone under 18 is using the app or has provided information, contact us so we can review the situation. This audience policy does not mean that the app independently verifies every user’s age.

Contact contact@experienceclubus.com for privacy questions and requests. You may ask us for access to, correction of, or deletion of information associated with your account. We may need to verify your identity before acting. Requests about separate membership, event or newsletter records are handled with the systems and teams responsible for those records.

We may update this policy when the app or our practices change. We will identify the effective date of an updated policy here. Material changes that require an additional notice or choice will be communicated through the app or an appropriate account contact channel.