Effective date: 7 October 2026 · Last updated: 7 November 2026
Athleta is a social sports app that helps people find pickup games, see which nearby sports fields are active, and play with friends. This policy explains what we collect, why, who we share it with, how long we keep it, and the control you have over it.
Athleta is operated by BritePath Apps ("we", "us"). If you have questions or want your data deleted, contact pragnaywork@gmail.com.
We do not sell your data, we do not show ads, and we do not use advertising or analytics trackers.
| Data | Why we collect it and how it is used | Required? |
|---|---|---|
| Email address or phone number, and password | To create your account, sign you in and keep it secure. Passwords are handled by our authentication provider (Supabase) and stored only as a one-way hash; we can never see them. | Required |
| Display name | So friends and community members can recognise you. | Required |
| Date of birth, and an under-18 flag derived from it | To decide whether you are a minor and apply stricter safety defaults (see section 4). Never shown to other users. | Required |
| Bio, favourite sports, avatar customisation | Optional personalisation of your profile. Favourite sports also help us suggest relevant zones and games. | Optional |
| Profile photo | Optional. The image you choose stays on your device and is not uploaded to our servers. We store only a reference to it in your account settings so the app can display it on your device. | Optional |
| Home location | Optional. A spot you pick on the map in Settings — never your live position. Used to show relevant nearby zones and, only if you turn on “Show friends when I’m home”, to show your friends an “At home” pin at that spot. While that is on, we also store whether you are currently at home (yes or no) and when that was last checked. | Optional |
| Notification and privacy preferences | To remember your choices, such as whether notifications are on, who can see where you play, and whether friends may see when you are at home. | Set by you |
| Data | Why we collect it and how it is used | Required? |
|---|---|---|
| Precise location while the app is open | To show you on the map, list nearby zones and their distance, check whether you are inside a zone, check whether you are standing in a new field that other players have asked to be confirmed, and — only if you turned on “Show friends when I’m home” — check on your phone whether you are at your saved home. For the field check your position is compared on our server and is not stored; for the home check only “at home: yes or no” leaves your phone. | Required for map and activity features |
| Precise location in the background | Only to detect when you enter or leave a sports zone, so your activity is recorded automatically. See section 2. | Optional; you can decline it and still use the app |
| Zone entry and exit events | A timestamped "entered" or "left" record for a specific zone. Powers live player counts, activity levels, automatic goal tracking and attendance. | Generated by use |
| Data | Why we collect it and how it is used | Required? |
|---|---|---|
| Sports zones and their photos | Name, sport, coordinates, boundary shape and any photos you add. A new zone is visible only to you until it is confirmed as a real playing field: automatically using OpenStreetMap, by players who visit it, or by us. Once confirmed it is shown publicly on the map. | Optional |
| Field confirmation votes | If you are at a new field, the app may ask "Is this a real field?". We store your yes/no answer to decide the field and award points. Other users never see how you voted. | Optional |
| Goals | To track the training goals you set and award points when you complete them. | Optional |
| Events, RSVPs and attendance | Pickup games and community events you create, your RSVPs, and attendance records (marked by you or a community organiser), including optional minutes trained. | Optional |
| Community membership and community chat messages | To run the teams you join and deliver your messages to other members. | Optional |
| Direct messages | To deliver your one-to-one messages with friends and show your conversations, including whether a message has been read. Only friends can message each other. | Optional |
| Friends, requests, blocks and reports | To run your friends list and friend requests, to stop people you block from finding or contacting you, and to let us review reports. A report is stored with who made it and who it is about. | Optional |
| Referrals | If you tell us who told you about Athleta when you sign up, we match that to their account once yours is confirmed, so they can earn referral rewards. We store who referred whom. Only the two of you can see it. | Optional |
| "The OG" for early players in an area | When a field you added is confirmed, we compare its location with the fields of other early players nearby, so the first 10 verified players within about 10 km earn "The OG" badge. We use only the field's location, never your own position, and store which field earned it. | Generated by use |
| In-app notifications | A list of recent events for you, such as friend requests, challenge invites, finished goals and field decisions, with the name of the other player involved. We store whether you have read each one. Only you can see your notifications. | Generated by use |
| Points, badges and challenges | To run leaderboards, badges and challenges. Points are added or removed for goals and field confirmations: for example, +50 when a field you added is confirmed, and −300 for the person who added a field and everyone who vouched for it if it turns out not to be a real field. | Generated by use |
| Data | Why we collect it and how it is used | Required? |
|---|---|---|
| Push notification token | A device identifier issued by the push service so we can send you notifications, such as a new team message or a completed goal. | Only if you allow notifications |
We do not collect payment card details, contacts, call or SMS data, browsing history, or advertising identifiers.
Athleta asks for background location access. Here is exactly what that means.
Only to detect when you enter or leave a sports zone. Your phone's operating system watches the boundaries of your saved zones and tells Athleta when you cross one. Athleta then records an "entered" or "left" event for that zone. Background location is not used for anything else.
We share data only with the service providers needed to run the app. We do not sell it.
| Provider | What it receives | Purpose |
|---|---|---|
| Supabase | Your account, profile, zones, goals, events, messages, activity and all other data stored on our servers | Hosting, authentication and database |
| Expo push notification service | Your device push token and the text of each notification | Sending push notifications |
| Google Firebase Cloud Messaging | Your device push token and the notification content, passed on by Expo | Delivering push notifications to Android devices |
| Google Maps | Map requests from your device, which include the area being viewed | Displaying the map |
| OpenStreetMap (Nominatim and Overpass) | A search term from your device when you search for a place, and the coordinates of a new zone, sent from our server, when checking it | Place search, and checking that a new zone is on a real playing field |
We may also disclose data if the law requires it, or to protect the safety of users.
Athleta is not intended for children under 13, and we do not knowingly collect data from them. For users who tell us they are under 18:
Age is self-reported and is not verified with identity documents. If you believe a child under 13 has given us data, contact pragnaywork@gmail.com and we will delete the account.
You can delete your account and its data in either of two ways:
Deleting your account permanently removes your account, profile, preferences, goals, points, RSVPs, attendance records, community memberships, friendships, direct messages, community chat messages, zone entry/exit events, field confirmation votes, push tokens and unverified zones. What we keep is described in section 5. Data stored only on your device, such as your profile photo, is cleared from the app when you delete your account in the app, and is removed if you uninstall it.
You can, at any time:
Depending on where you live, you may have additional rights under laws such as the GDPR, PIPEDA, or applicable provincial or state privacy laws. We handle requests the same way wherever you are: email the address below.
Data is stored on Supabase and protected by row-level security rules, so each user can only read the data they are entitled to. Traffic between the app and our servers is encrypted in transit. No system is perfectly secure, and we cannot guarantee absolute security.
If we change how we handle your data, we will update this page and its "last updated" date. Significant changes will be announced in the app.
BritePath Apps
pragnaywork@gmail.com