Updated October 2, 2026
Other players see your first name, photo, skill, status, bio, and the public courts you play at. They do not see your email, a map pin for you, or a last name. This is a plain-language draft, not a lawyer’s policy.
Account: email, a hashed password, first name, skill, home courts, and whether the email has been confirmed. Optional profile: photo, bio, usual times, formats, hand, paddle brand, and tournaments you add. Activity: the status you post, Let’s play requests, follows, blocks, and reports. Alerts: the courts and skill range you watch, and whether you want email.
Venue coordinates belong to public courts so Nearby can work. We don’t ask the phone for your location. Your account has no personal latitude or longitude.
The court and profiles are for signed-in players. A public profile does not include your email. Photos are stored privately and loaded only for someone who is signed in. Court street addresses on the court are the venue’s public address, not yours.
If you both follow each other, you show up as friends. A block hides each of you from the other’s court and profiles. A report is visible to the people who operate Stackr, not to the player you reported.
We email you only for things you ask for: a password reset, an optional confirmation link, and open-court alerts if you turn email on. Mail goes out through the provider configured for the server (for example Resend or SMTP). We don’t sell the list.
A single session cookie keeps you signed in. It is httpOnly, limited to this site, and marked secure when the app is served over HTTPS. Resetting your password ends other sessions. We don’t use advertising cookies.
Data stays until you delete the account or we remove it because the account was abused. Delete account, on You, asks for your password and then removes the user, the photo, follows, requests, and tokens. Rate-limit counters are short-lived keys, not a profile.
The database, photo storage, and email provider are the companies whose keys are set in the server environment. They process data so the app can run. Questions about a specific deployment go to the person who operates that deployment.