This policy describes what Bagged collects through the Bagged iPhone app and this website, why we collect it, who else can see it, and how you can get rid of it. It applies to everything we operate. It is written to be read, not to be skimmed past.
Bagged, operated by Thomas Matera, an independent developer based in New Jersey, United States. If you have a question about anything here, write to hello@baggedgolf.com.
The short version
We collect your email, a username, and whatever you choose to log — rounds and scores, course ratings, optional photos, and who you follow.
There are no analytics, advertising, or tracking SDKs in Bagged at all. We do not sell your data or share it with advertisers.
Your profile lives inside the app. It is not a public web page and search engines cannot index it.
Photos are stripped of embedded metadata on your device before they are uploaded, so location data from your camera never reaches us.
You can delete your account, and everything attached to it, from inside the app at any time.
What we collect
Account information
To create an account we need an email address and a username. The username is how other people find you and is visible to them. Your email address is not shown to other users.
You can also add a display name and an avatar. Both are optional, both are shown to other people in the app, and the avatar goes through the same upload path as round photos, so it is stripped of its metadata the same way.
If you sign up with an email and password, the password is handled by our authentication provider and stored only as a salted hash. Nobody at Bagged can read it, and we cannot recover it for you — we can only send you a reset link.
If you use Sign in with Apple, we receive a stable identifier from Apple and an email address. If you choose Apple’s Hide My Email option, the address we receive is Apple’s private relay address, and that is the only address we ever hold for you.
Apple also gives us your first and last name, once, on the very first authorization and never again. We hold it only long enough to pre-fill your profile: it goes to a staging row that is deleted the moment your profile exists, and a copy stays in your device’s keychain in case that first write fails. We never receive your Apple ID password, and we receive nothing else from your Apple account.
That staged copy is a real row on our servers for as long as it exists: it holds the first name, last name, and email Apple gave us, it is readable only by your own account, and it has no update path, so a later sign-in cannot overwrite it. It is deleted when your profile is created, and swept with everything else if you delete your account before that happens.
We also hold a token from Apple whose only job is to disconnect Bagged from your Apple ID when you delete your account. It lives on our servers rather than on your device, no client can read it, and it is destroyed with the rest of your account.
What you create in the app
Together with the account details above and the request logs below, this is the complete list of what we hold for you.
- Rounds logged — which course, the date you played, and, if you enter them, the tees, your total score, the course par, and your hole-by-hole scores.
- Trophies — which trophies you have earned, derived from the courses you have logged.
- Course ratings — the half-star rating you give a course. There is no free-text field attached to a rating or a round. A rating you give is pooled into the average shown on that course to everyone in the app, alongside the number of ratings and a breakdown of how they are spread. Your individual rating is not labelled with your name, but on a course with very few ratings the breakdown may make it obvious.
- Round photos — optional. Stored as files in Supabase Storage, not in the database. See the note on photo metadata below.
- Home state — optional, with its own privacy toggle so you can set it without showing it on your profile.
- Follows — who you follow, and who follows you.
- Blocks — accounts you have blocked. Blocking hides each of you from the other and removes any follows between you in both directions. Unblocking lifts the block but does not restore those follows — they were deleted, not hidden. The person you blocked is not told.
- Course characteristics — structured tags you put on a course, chosen from a fixed vocabulary rather than typed. Your tags are pooled with everyone else’s and shown on the course itself, so what you pick contributes to what every other golfer sees there.
- Ranking lists — opt-in ordered lists of courses you build by hand, from a fixed set of list types with a size cap. They never fill themselves from your bag. A list you make is shown on your profile to other golfers in the app.
- Curator role — whether you have been made a curator for a course, which is what lets you edit that course’s registry entry and add photos to it.
- Reports — if you report an account or a photo, we keep the report, including whatever you write in the details box, so we can act on it. Reports are write-only from the app: nobody, including you, can read them back or edit them afterwards, and they outlive account deletion. See how long we keep it.
Photo metadata
Every image you upload — round photos and avatars alike — is stripped of its embedded EXIF metadata on your device, before upload. The app decodes the picture you picked down to raw pixels and writes a fresh JPEG from those pixels, so GPS coordinates, capture timestamps, and camera and lens identifiers are dropped rather than travelling with the file. We receive the image only.
This is worth being precise about: it means we cannot tell where a photo was taken from the photo itself. It does not change the fact that the round you attached it to names a course.
Location
If you ask Bagged to show you what is near you while browsing courses, the app requests your location while you are using it. It asks for a coarse fix, accurate to about a kilometre rather than to a green, and the coordinate is used on your device to order the list. It is never sent to our servers and we never store it. You can decline, and everything else in the app works normally.
Logging a round records the course you chose and the date. It does not record where you were standing.
Information we receive automatically
Supabase retains operational request logs as a normal function of hosting, including the IP address, timestamp, and the request that was made whenever the app or this site talks to our backend. These logs exist to keep the service running and to investigate abuse and outages. They are not joined to your profile for any other purpose.
Apple gives us aggregate App Store metrics — download counts, territories, crash totals, and similar. These arrive already aggregated. We do not control what Apple measures, and there is nothing in them we can tie back to an individual person.
What we do not collect
Bagged contains no third-party analytics, advertising, or crash-reporting SDKs. There is no Google Analytics, no Firebase, no Meta or TikTok pixel, no attribution or session-replay tool, and no tracking SDK of any kind in the app or on this website. Supabase is our only backend. We do not track you across other apps or websites, and we collect no advertising identifiers — the app never asks for permission to track, because there is nothing it would do with it.
We also do not collect:
- Your contacts, calendar, photos library beyond the images you pick, microphone, or health data.
- Payment information. Bagged is free, and no payments run through us.
What other people can see
Bagged is partly social, so some of what you log is meant to be seen — but only by other signed-in people, and only inside the iOS app. Your profile is not a web page. Nothing user-specific is published to this website, and nothing about you is crawlable or indexed by search engines.
- Visible to other users in the app: your username, the courses in your bag, your ratings, any photos you attach, and your follower and following lists.
- Visible only if you turn it on: your home state, controlled by its own toggle in the app.
- Never shown to other users: your email address, your authentication details, who you have blocked, and anything you have reported.
Round dates are shown to the day, never the time. That is deliberate. A precise timestamp on where someone plays, repeated across a season, describes their movements in a way a date does not. The app only ever asks you for a date, and only ever stores one.
Why we use it
- To create and authenticate your account.
- To store and show your bag, your ratings, and your photos back to you and to the people who can see your profile.
- To calculate trophies and tier points from the courses you have logged.
- To operate the follow graph, so people you follow show up for you.
- To enforce the blocks you set, and to review the reports you send us.
- To answer you when you email support.
- To keep the service secure, and to investigate abuse, spam, and fraud.
If you are in the UK or the European Economic Area: we rely on performance of a contract for everything needed to give you an account and a working app, on legitimate interests for security and abuse prevention, and on consent for the optional things you choose to add, such as photos and your home state.
Who else touches it
We keep the list of companies with access to your data as short as we can. Today it is:
- Supabase — our database, authentication, and file storage, running in the US East (Ohio) region. Your account, your logged rounds, your ratings, your follow graph, and your uploaded photos all live here.
- Apple — if you use Sign in with Apple, Apple handles that sign-in and tells us the minimum needed to identify your account. Apple also serves the map tiles behind the course map and the map of your bag, so Apple receives the map region you are looking at. Those tile requests go directly from your phone to Apple and are not tied to your Bagged account.
- Resend — delivers the email we send you, such as password resets and account notices. Resend sees your email address and the contents of those messages.
We may also disclose information if we are legally required to, or where we need to in order to establish or defend a legal claim, or to protect someone’s safety.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising. There is no revenue model here that would be improved by doing so.
How long we keep it
Your account data stays for as long as your account exists. When you delete your account, the deletion cascades: your profile, your logged rounds, your ratings, your follows, your blocks, your course tags, your ranking lists, your curator role, and any staged Sign in with Apple name still awaiting a profile are removed from our live database immediately, and your round photos and your avatar are removed from file storage.
Three things outlive a deleted account. The first is abuse reports. If you reported someone, or someone reported you, the report and what it says are kept. A report you filed is no longer linked to you once your account is gone: your identity is severed from it, and what remains is the report on its own.
The second applies only to course curators. If you have never curated a course, this does not affect you: every photo you uploaded is deleted along with the rest of your account. Curators can add photos to the shared course registry that every golfer sees. Those are registry content rather than anything personal, so they stay when a curator’s account is deleted. Round photos and avatars are always deleted either way.
The third is a housekeeping record. Removing your photos from the database is not the same as reclaiming the underlying files, so each file path is written to a list for a later sweep to clear. That list holds a bucket name and a file path, and the path contains the account id the file belonged to. Nobody can read it — not you, not another golfer, not the app — the id no longer refers to anything, and the row goes when the file does.
Your username is released the moment your account is deleted, so another golfer is free to claim it.
Encrypted backups lag behind the live database. Deleted records can persist in backups for up to 7 days before those backups roll off. They are not used to restore individual accounts.
Deleting your account
From any screen in the app, tap the menu button in the top left to open Settings, then choose Delete Account. You will be asked to type your username to confirm, so it cannot happen by a mistaken tap. It is reachable from anywhere in the app rather than buried in a submenu, and you do not need to email us or ask permission.
Deletion is permanent and cannot be undone. If you would rather remove one thing than all of it, you can delete an individual logged round, remove a photo, or turn off the home state toggle without touching the rest of your account.
Your rights
Wherever you live, you can ask us to give you a copy of your data, correct it, or delete it, and we will do it. Most of this is faster to do yourself in the app.
If you are in the UK or EEA, you also have the right to object to or restrict certain processing, the right to data portability, and the right to complain to your local data protection authority. If you are in California, you have the right to know what we collect, to delete it, to correct it, and not to be discriminated against for asking — and, as above, we do not sell or share your personal information.
To exercise any of these, email hello@baggedgolf.com. We may need to confirm you control the account before we act on a request.
Security
Traffic between the app and our backend is encrypted in transit with TLS, and data is encrypted at rest by our hosting provider. Access to production data is limited to people who need it to run the service.
Every table holding user data is protected by row-level security, enforced by the database itself rather than by the app. That means one account cannot read another account’s private rows even if a client is tampered with. Abuse reports are insert-only, so nobody can read back or edit what has been reported, and the Apple refresh tokens used to keep you signed in are held in a server-side table that no client can query at all.
No service can promise perfect security, and we are not going to pretend otherwise. If we ever discover a breach affecting your data, we will tell you and the relevant regulators as required by law.
Children
Bagged is not intended for children under 13, and we do not knowingly collect personal information from them. Where the law where you live sets a higher minimum age for consenting to this kind of service on your own, you must meet that age instead. If you believe an underage account exists, email hello@baggedgolf.com and we will remove it.
International transfers
Your data is stored in the United States. Bagged is operated from the United States, and our database and file storage run in Supabase’s US East (Ohio) region. If you use Bagged from outside the United States, your information is transferred to and processed in the United States, which may have different data protection rules than your own country. Where required, we rely on the European Commission’s standard contractual clauses to cover those transfers.
Changes to this policy
If we change what we collect or what we do with it, we will update this page and move the date at the top. For a change that materially affects you, we will also tell you in the app or by email before it takes effect.
Contact
Questions, requests, or corrections: hello@baggedgolf.com.