Skip to main content

    Privacy Policy

    Last updated: November 2026

    1. Information We Collect

    We collect information you provide directly, including:

    • Account Information: Email address and display name when you create an account
    • Club Submissions: Information you provide when submitting clubs or events
    • Newsletter: Email address when you subscribe to our newsletter
    • Contact Forms: Name and message content when you contact us

    2. How We Use Your Information

    We use collected information to:

    • Provide and improve our polo directory services
    • Send newsletters (only if you've opted in)
    • Respond to your inquiries and support requests
    • Analyze site usage to improve user experience
    • Ensure security and prevent fraud

    3. Information Sharing

    We do not sell your personal information. We may share information with:

    • Service providers who assist in operating our platform
    • Legal authorities when required by law
    • Polo clubs when you submit listing requests (with your consent)

    4. Cookies and Tracking

    We use cookies and similar technologies to:

    • Remember your preferences and settings
    • Understand how you use our site
    • Provide personalized content

    You can control cookies through your browser settings. Disabling cookies may limit some functionality.

    5. Data Security

    We implement industry-standard security measures to protect your information, including:

    • Encrypted data transmission (HTTPS)
    • Secure database storage
    • Regular security audits
    • Access controls for staff

    6. Your Rights

    You have the right to:

    • Access the personal data we hold about you
    • Request correction of inaccurate data
    • Request deletion of your data
    • Opt out of marketing communications
    • Export your data in a portable format

    7. Children's Privacy

    Our service is not directed to children under 13. We do not knowingly collect information from children under 13. If you believe we have collected such information, please contact us immediately.

    8. International Transfers

    Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place for such transfers.

    9. Changes to This Policy

    We may update this policy periodically. We will notify you of significant changes by posting a notice on our site or sending you an email.

    10. Signing in with Google

    You can sign in or create an account with Google, with an emailed link, or with an email address and password. If you use Google:

    • What we receive from Google: your name, your email address, the web address of your Google profile picture, and your Google account ID. We ask Google only for basic sign-in information (the openid, email and profile scopes) and we do not read anything else from your Google account.
    • What we store: those details are saved in our database. The accounts table also holds the access token and ID token that Google issues for your sign-in.
    • Existing accounts: if an account with the same email address already exists, signing in with Google opens that account, but only when Google reports the email address as verified; otherwise the sign-in is refused. Google can be used for an existing account only after that account's email address has been confirmed; if it has not been, the Google sign-in is refused and nothing on the account is changed. The first time you confirm your email address with an emailed link, we sign out every other session on the account and remove any password and any linked Google sign-in that were added before the address was confirmed. Changing your email address and confirming the new one has the same effect.
    • Cookies: authjs.csrf-token and authjs.callback-url are set for every visitor (the site checks your session on each page load), not only at sign-in; they are security and redirect cookies, not tracking. authjs.session-token (your signed-in session, up to 30 days) exists only once you have signed in. While you are sent to Google and back, authjs.state and authjs.pkce.code_verifier are also set and are cleared when you return. On our HTTPS site these names carry a __Secure- prefix (the CSRF cookie uses __Host-).
    • Google handles your Google account under its own privacy policy (policies.google.com/privacy). Signing out clears the session cookie in your browser. To ask us to delete the details above, contact us using the address below.

    11. Contact Us

    If you have questions about this privacy policy or our data practices, please contact us: