MyPokerMaps
Privacy

Privacy Policy

This policy explains the categories of data MyPokerMaps uses for public discovery, accounts, Social Hub, Club Wallet, advertising, support, and operator workflows. We avoid claiming privacy controls that are not backed by product behavior.

Updated May 7, 2026
Club data boundary

Social Hub people search uses public-web social profiles. Club employee records, operator accounts, and raw club member records should not bleed into public-player search or messaging.

Data you provide

Account and player profile data comes from forms, settings, self-service flows, and support requests.

  • Name, email, phone, city/state, date of birth, profile settings, display name, handle, bio, and social preferences.
  • Support and partnership messages, including request metadata and user agent.
  • Identity or age verification status where supported by the verification provider.

Public discovery data

Club and event data may be shown publicly when the source system marks it public-safe.

  • Verified public clubs, tables, tournaments, streams, ad spaces, and public status messages.
  • Player-facing waitlist or registration states where a club enables public self-service.
  • Degraded or unavailable states when upstream public data cannot be confirmed.

Social data

Social Hub uses dedicated public social profiles.

  • Posts, comments, reactions, messages, communities, events, friend requests, and public profile summaries.
  • Visibility, discoverability, and messaging preferences control how social features behave.
  • Private club roles and employee identities are not a social-search source unless that person separately creates a public social profile.

Payments and receipts

Payments are handled by payment processors and routed by money ownership.

  • Platform-owned payments may include player memberships, advertising, subscriptions, and platform invoices.
  • Club-owned payments may include dues, balances, and wallet purchases through a participating club’s Stripe Connect account.
  • We do not store full card numbers in public web.

Notifications

Notification preferences are intended to reduce noise.

  • DMs and time-sensitive reminders can be immediate where supported.
  • General activity should default to lower-noise digest behavior where implemented.
  • Marketing and newsletter messages should be opt-out capable.

Cookies and analytics

Cookies keep the service functional and help measure performance.

  • Essential cookies support authentication, sessions, security, and preferences.
  • Analytics and performance tools help diagnose public-web reliability.
  • Advertising cookies or campaign attribution should follow consent and browser controls where applicable.
See More

Your controls

Controls live in profile, social, and browser settings where supported.

  • Manage profile visibility, messaging, notifications, discovery radius, and social controls in account settings.
  • Use support for access, correction, deletion, portability, or privacy questions when self-service is unavailable.
  • Club-specific records may require the participating club to act as the operational data owner.

Retention and deletion

Retention depends on account, legal, support, financial, and security needs.

  • Transaction, audit, support, compliance, and anti-abuse records may be retained when required.
  • Public social content may be removed or hidden when deleted or moderated.
  • Some club records belong to the club’s operational system and may be subject to club policies.

Security

Security is enforced through auth, encrypted transport, support tracing, and provider controls.

  • Use strong passwords and do not share reset links or tokens.
  • Report suspicious account activity or impersonation through support.
  • Profile photos and verification-sensitive features must not rely on arbitrary uploads.

Contact

Privacy requests should be traceable.

  • Email support@mypokermaps.com or submit a support request.
  • Include the account email and the exact privacy action requested.
  • Do not include passwords, full card numbers, or raw ID documents in ordinary support requests.