Back

Privacy Policy

Effective date: 2026-05-31 · Last updated: 2026-10-16

1) Who We Are

This Privacy Policy is for the xfield application and website at https://xfield.app. It explains how xfield (“we”, “us”, “our”) collects, uses, shares, and protects information when you use our website, mobile apps, and related services (the “Service”), including Google user data obtained through Google Sign-In.

xfield is a sports venue booking platform. Payments you make are for booking a real sports facility (and related booking services), not for buying digital goods inside the app.

Contact for privacy requests: support at xfield.app.

2) Data We Collect

Depending on how you use the Service, we may collect:

  • Phone number — used for account verification and login via WhatsApp one-time password (OTP).
  • Verification events (for example requesting or confirming a code) for security, fraud prevention, and rate limiting.
  • Profile data you provide (for example your name) if required to complete your profile.
  • Booking data — stadium, pitch, date/time, status, shared-booking participants, and related history.
  • Payment and transaction data — amounts, payment status, refunds, invoices, payment method type, and provider references needed to process bookings. Card details are handled by our payment provider (Thawani); we may store a payment-provider customer id and tokenized saved-card references, not full card numbers.
  • Device location — when you choose to share it (for example on the map), we may collect precise location coordinates so we can show nearby stadiums. You can deny or revoke location permission in your device settings. We do not need location for every feature.
  • Push notification tokens — if you allow notifications on a mobile device, we store a device token (for example via Firebase Cloud Messaging / Apple Push Notification service) to send booking, match, or account alerts.
  • Google account data if you connect Google Sign-In for the stadium owner portal — see the dedicated “Google User Data” section below for how we access, use, store, and share that data.
  • Stadium media you or venue owners upload (for example venue photos) that appear in listings.
  • Technical data — approximate device or browser info, app/platform identifiers, IP address, and server logs needed to secure and operate the Service.
  • Preferences stored on your device (language, currency, theme, and cookie consent) as described in our Cookie Policy.

3) Google User Data — What We Access

xfield uses Google Sign-In only for the stadium owner portal. Players who book or join matches sign in with phone number and WhatsApp OTP, not Google.

Our Google OAuth client requests only these scopes: https://www.googleapis.com/auth/userinfo.email (see your primary Google Account email address) and https://www.googleapis.com/auth/userinfo.profile (see your personal info, including any personal info you have made publicly available).

When an approved stadium owner chooses “Continue with Google”, our application will access the Google user data Google returns for those scopes, including: primary email address, email verification status, Google account identifier (sub), name, and profile photo URL. We do not request or access Gmail, Google Drive, Calendar, Contacts, Google Workspace content, or any other Google API scopes.

4) Google User Data — How We Use It

We will use Google user data only to provide and improve user-facing owner features in the Service: linking a Google account to an existing xfield account, checking that the email is allowed for owner access, signing the owner into the owner dashboard, and displaying the owner’s name and profile photo in the owner portal and related stadium-management screens.

We do not use Google user data for targeted advertising, personalized or interest-based ads, retargeting, selling to data brokers, providing data to information resellers, determining credit-worthiness, lending, creating unrelated databases, or training non-personalized AI/ML models.

5) Google User Data — Storage, Sharing & Protection

We store the Google account identifier, name, email, and profile photo URL in our database as part of the owner account record, linked to the owner’s xfield user id. Session cookies keep the owner signed in while using the Service.

We do not sell Google user data. We do not transfer or disclose Google user data to third parties for purposes other than providing or improving the Service (for example hosting/infrastructure providers that process data solely to operate the Service), or when required by law, or to protect rights, safety, and security.

Security procedures are in place to protect the confidentiality of Google user data. We use HTTPS/TLS encryption to protect Google user data in transit between your device, Google, and our servers, and we restrict access to owner account records to authorized systems and personnel needed to operate the owner portal.

6) Google User Data — Retention & Deletion

We retain Google-linked owner profile data for the length of time needed to provide owner access and fulfill the purposes in this Privacy Policy, unless a longer period is required or permitted by law.

You may request deletion of your Google-linked data by deleting your xfield account in Settings or on the delete-account page, or by contacting support at xfield.app. When deletion is completed under our process, we delete or destroy the Google account identifier, name, email, and profile photo from the owner profile. You can also revoke xfield’s access to your Google Account in your Google Account permissions settings.

7) Limited Use & Google API Compliance

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. xfield uses Google user data only to provide or improve user-facing stadium-owner authentication and account features that are prominent in the Service.

xfield does not use Google APIs or Google user data to create, generate, improve, distribute, or train systems that produce AI-generated non-consensual intimate imagery (AI NCII), deepfakes, or any intimate or sexually explicit imagery of real people.

We do not use Google user data or Google Workspace APIs to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models. We do not transfer Google user data to third parties for AI/ML training.

8) Why We Use WhatsApp OTP

We use WhatsApp OTP to help secure accounts, reduce fraud, and confirm that the person logging in controls the phone number on the account. Message and data rates may apply depending on your plan and carrier.

Never share your OTP with anyone. Our support will never ask you for your OTP.

9) How We Use Your Data

  • Provide login, account access, discovery of venues, and booking functionality.
  • Authenticate stadium owners via Google Sign-In for the owner dashboard, as described above.
  • Process and manage bookings, cancellations, payments, and refunds.
  • Show nearby stadiums when you share location.
  • Send transactional notifications you enable (for example booking updates).
  • Prevent fraud, abuse, scalping, and automated or bot activity.
  • Improve reliability, debug issues, and secure the Service.
  • Comply with legal, tax, accounting, and dispute obligations.

10) Legal Bases (GDPR-style)

If GDPR applies to you, our legal bases may include contractual necessity (to provide login, bookings, and payments), legitimate interests (security and fraud prevention), and consent where required (for example device location or push notifications).

11) Sharing & Disclosure

We may share information with:

  • Stadium and venue owners and staff, as needed to fulfill bookings and handle disputes (for example your name, phone, and booking details).
  • Payment providers — we use Thawani to process online payments and refunds. Payment data needed to complete a charge or refund is shared with Thawani under their terms and privacy practices.
  • Messaging or verification providers such as WhatsApp/Meta (or intermediaries) used to send WhatsApp OTP messages.
  • Google — when an owner uses Google Sign-In, authentication is handled by Google under Google’s terms and privacy policy; we receive the Google profile fields described in the Google User Data section.
  • Push notification infrastructure providers (for example Google Firebase / Apple) when delivering notifications to your device.
  • Map and geocoding providers: we use OpenStreetMap map tiles and Nominatim (nominatim.openstreetmap.org) to show maps and resolve stadium locations. Those requests may include map tile coordinates or venue latitude/longitude, and are also subject to the OpenStreetMap Foundation privacy policy.
  • Hosting and infrastructure providers that help us operate the Service.
  • Authorities if required by law or to protect rights, safety, and security.

12) Location

We request location only when a feature needs it (for example finding nearby stadiums on the map), not solely to open the app.

On supported devices we may request precise location so the map can place you accurately. If you grant only approximate location, we use what your device allows.

You can refuse permission and still browse venues and book without sharing your live location.

13) Push Notifications

If you enable notifications, we store a device push token and may send alerts about bookings, matches, payments, or account activity.

Notification content is kept as limited as practical. You can disable notifications in your device or app settings; we remove device tokens when you delete your account or unregister the device.

14) Maps & OpenStreetMap

Map imagery and some location text come from OpenStreetMap and Nominatim. OpenStreetMap data is available under the Open Database License (ODbL). Attribution: © OpenStreetMap contributors. See https://www.openstreetmap.org/copyright.

15) Security & Encryption

We use industry-standard measures to protect data in transit, including HTTPS/TLS for our website, API, and app traffic.

No method of transmission or storage is completely secure. Please protect your device, WhatsApp account, and OTP codes.

16) Data Retention

We retain personal data as long as needed to provide the Service, comply with legal obligations, resolve disputes, and enforce our agreements. Retention periods may vary by data type.

When you delete your account, we remove your name, phone number, saved cards, device notification tokens, and chat messages. Upcoming bookings, including shared bookings, must be cancelled or finished first. Payment records, invoices, refunds, and bookings stay so we can meet tax, refund, and dispute obligations. Those records are no longer tied to your name or phone number.

17) Your Rights

Depending on your location (for example GDPR or CCPA), you may have rights to access, correct, delete, or export your personal data, and to object to or restrict certain processing. You can delete your account from Settings in the app, or on the web from the delete-account page. For other privacy requests, contact support at xfield.app.

18) Cookies & Local Storage

We use essential cookies and local storage (for example language, currency, and theme) to make the site work. See our Cookie Policy.

19) Children

The Service is not intended for children. If you believe a minor has provided personal data without appropriate consent, contact us.

20) Changes

We may update this Privacy Policy from time to time. Updates are effective when posted on this page. If we change how we use Google user data, we will update this policy and, where required, notify users before using that data in a new way.

About xfield·Delete account·Cookie Policy·Refund Policy