Privacy
November 12, 2026
BeatNavy.org is an invite-only map of Army–Navy watch parties for West Point grads. This page says what the site stores and who can see it. It describes how the site works today. It is not a claim that the site meets any particular privacy law.
Sign-in
You sign in with Google. The site receives the name and email address on that Google account. Sign-in and the database are run by Supabase, which stores the account. The site does not see your Google password.
Your profile
After you sign in you can add your name, class year, and, if you want, a company and a call sign. You pick where you watch: a neighborhood, city, or ZIP, not a street address. The dot on the map is shifted about half a mile from that spot, and the map does not zoom in past the neighborhood. You can say whether you are hosting, looking, or not sure, and whether you want a bar, a party, or a couch. You can leave a short note for grads who might vouch for you, and choose whether hosts of events you join can see your name.
Who invited you is stored and is not shown on the site.
Who can see it
- You can see your own profile. Other members usually see a call sign, class year, and company, not a full name.
- Members who can vouch see people waiting to get in: name, class year, company, the note they wrote, and where they watch.
- Chat shows a first name and class year. An event chat is for the hosts and people going. The local huddle is opt-in, for grads near where you watch, and those messages are matched using that approximate location.
- A “looking” dot has no name on it. People who are not signed in see a blurrier map and a count of grads and countries.
- Moderators can see profiles and open reports.
Events
If you host, the site stores the place, time, a short note, and any address and contact info you enter. Open-house and RSVP addresses are visible to members, because those are meant to be public venues. A couch address is visible only to the hosts and to guests the host has let in. Contact info is visible only to the hosts and to people who are going. Hosts see their guest list. Your name is on that list only if you chose to share it. Other members do not see who is going. A home event is blurred to the neighborhood, then shifted, before it goes on the map.
Invites, messages, and reports
Invite codes record who created them and who used them. Messages you post are stored with your account. If you report a person, an event, or a message, moderators can read what you wrote. Moderators can remove an account. That cancels the person’s events and hides their messages.
Agents
A member can connect an AI agent and give it a key. The site stores the name you give that key, the permissions you picked, the last four characters of the key, and a hash of the key. The full key is shown once and is not kept. The site also keeps a short log of which tools the key called and whether the call worked, not the text of your chat with the agent.
The agent acts as you, and only with the permissions you picked. It cannot sign people up, use invite codes, vouch, or post in chat. Couch addresses and guest names stay hidden from agents unless you turn that on. Whatever an agent does read goes to the company that runs the agent. Hosts can see when an RSVP was made by an agent.
Other services, and your browser
The pages are hosted on Cloudflare. When the robot check is turned on, Cloudflare Turnstile runs in the browser before you finish joining or create an event, and the site keeps a short-lived note that the check passed. If address suggestions are turned on, the address a host types is sent to Mapbox to look up the place.
The browser keeps a few things on your device: the sign-in session, whether sound is on, that you left the title screen, an invite code from a link, and a couple of on-site achievements.
Not sold, and deletion
This information is not sold.
To delete your account, email mattrhansen@gmail.com. The account and the profile, events, messages, and agent keys tied to it can be deleted on request. Write from the email on the account if you can, so it’s clear the request is yours. A few records may remain without your name, such as the fact that an invite code was already used.