Privacy policy

Account. Your email address, a display name, and a password (stored only as a salted argon2 hash — we never see it). Optionally a home city and a favorite corps, if you choose to add them. We also keep a contribution reputation score.

Seat photos. The image itself, an optional caption, and — deliberately — the coordinates, compass heading, and device orientation at the moment of capture, plus the camera's focal length. That geometry is the entire point: it is what lets us place a photo in the right section and tell other fans what the view is actually like. You may also tag a row and seat. We store your phone's model name (for example “iPhone 16 Pro”) and how precise its location reading was, because comparing photos taken on different cameras is only possible if we know which camera took them. That is a hardware model shared by millions of phones, not an identifier for yours.

Seat measurements. Bench width, view distance, and elevation, captured with the camera or AR/LiDAR, plus which section they came from.

Your activity. Reviews you write, trips you plan, and score predictions you make.

Ordinary server logs. Requests to the API are logged with a request id for debugging and abuse prevention, and are not used to build a profile of you.

No advertising identifiers, no third-party analytics or tracking SDKs, no contacts, no background location. The app never tracks your position while you aren't using it — location is read at the moment you capture something, and not otherwise.

Photos are stripped of their EXIF metadata before storage, so the original file's embedded camera and GPS tags do not travel with the image we publish. Note the deliberate exception above: we read the focal length, and record your capture location separately, as described — that data is the feature, and it is used to position the photo, not to track you.

Only to verify a contribution is genuine. When you submit a seat photo or measurement, the coordinates are checked against the venue's boundary. A submission we can't place at the venue isn't discarded — it's held for a person to review before it can appear. Without that check, the seat data every other fan relies on could be faked from a couch; indoors, where GPS is often unreliable, that check frequently can't be made automatically, which is why a human makes it instead.

The permission is “while using the app.” If you decline it, everything except contributing still works.

Public once approved: seat photos and their section, row/seat tag and caption; reviews; your display name and reputation next to those contributions; and aggregate seat statistics derived from measurements.

Never public: your email address, your password, your saved trips (unless you explicitly create a share link for one), and your exact capture coordinates — those are used server-side to place a photo in a section and are not shown to other users.

Submissions are moderated before publication, automatically and by a human when flagged.

Map tiles. Venue maps load imagery from OpenStreetMap and Esri. Loading a map means those providers see your IP address, as with any embedded map. We send them nothing else.

Hosting. The app runs on a server we operate in the United States (New York), provided by Contabo. The database and uploaded photos are stored there. If you use CorpsPlay from outside the United States, your data is transferred to and processed in the US.

Payments. The optional tip jar, when enabled, goes through Stripe-hosted checkout. Card details are entered on Stripe's page and never reach our servers. This is currently switched off.

We do not use advertising networks or data brokers, and we do not sell your data to anyone.

On the web, your session token is kept in your browser's local storage. In the iOS app, it's kept in the system Keychain. Signing out removes it. We don't use cookies for tracking.

Account data is kept until you delete your account. Contributions — photos, reviews, measurements — are kept while they remain useful to other fans, since a seat guide is only as good as its history. Server logs are short-lived.

You can edit or delete your reviews, trips, and predictions in the app, and revoke camera or location access at any time in iOS Settings.

To delete your account, or to request a copy of your data, email [email protected] and we'll action it. Deleting your account removes your account details; published photos may be retained without attribution where other fans' seat data depends on them — tell us if you want yours removed entirely and we will remove them.

CorpsPlay isn't directed at children under 13, and we don't knowingly collect their information. If you believe a child has created an account, contact us and we'll remove it.

The 2026 season is a beta. Features and this policy may change as the app develops; if what we collect changes materially, we'll update the date at the top and say so in the app.

Senechal Consulting LLC — [email protected]. Questions about this policy, a takedown request, or anything else, that address reaches a human.

Support the project