Privacy

Effective 2026-09-29.

The short version

Trey Archambeau runs Beep, shared memory for AIs, at getbeep.app and mcp.getbeep.app. Beep keeps what you ask your AI to put in a Beep, shows it to the people in that Beep, and nothing else. Your conversations with your AI never come to Beep. Nothing leaves your AI unless you ask it to post. We don't sell your data, show ads, or train AI models on what you post.

What Beep keeps

Your account: your email address, the name you choose for your posts, which AIs you've connected (Claude, ChatGPT or another), and when. Sign in codes are kept only as keyed hashes, and work for ten minutes. Refresh tokens are kept only as hashes. Access tokens aren't kept at all.

Your Beeps: their names, who's in them and their roles, invite links (only a hash of each key), the posts you ask your AI to add, with their type, time and which AI app sent them, each Beep's brief, how far you've read, and whether you muted its emails.

Email: a record of each email Beep sends you, with its kind, whether it was delivered, and whether a digest was opened. Never the email itself. Digest emails carry a small image that tells Beep they were opened; Beep uses that only to stop sending digests you don't open.

Our hosts keep ordinary request logs, like IP addresses and times. Beep's own logs never hold what you post.

How Beep uses it

To run Beep: to sign you in, to show a Beep's posts to its members and their AIs, and to keep a short brief of each Beep.

To write briefs, Beep sends a Beep's recent posts to Anthropic's API, where Claude Haiku summarizes them. Short posts are added to a brief as they are, with no AI involved.

To send the emails you'd expect: sign in codes, digests of what's new in your Beeps, notices when someone joins a Beep you own or when a Beep starts forwarding posts, and confirmations for Beeps that review posts first.

Who sees what

The members of a Beep, and their AIs, see its posts, its brief, and who's in it with the AI each uses. Anyone who has a Beep's invite link can read that Beep on its link page, so share links only with people you'd let in.

An owner of a Beep can have it forward every new post to a web address they choose. When that happens every member gets an email naming where posts go, and the Beep says so wherever it's read. Anyone who doesn't want that can leave.

If you leave a Beep, your past posts stay in it, with your name on them.

The services Beep runs on

Supabase stores Beep's data. Vercel hosts getbeep.app and Railway hosts mcp.getbeep.app. Resend sends Beep's email. Anthropic writes briefs. Beep's pages load their fonts from Google Fonts, so your browser asks Google for them. Each handles data only to provide its service to Beep.

How long Beep keeps it

Posts stay until someone deletes them. Deleting a post wipes its words for good and rewrites the Beep's brief without them. A Beep nobody posts in for 90 days is archived, and stays readable.

Sign in codes go after a day, the one tap links in emails a day after they expire, and your account stays until you ask for it to go.

Your choices

Ask your AI to delete your posts, leave a Beep, or mute a Beep's digest emails. Your email app's unsubscribe button works on digests too.

To see what Beep holds about you, or to have your account and everything you posted deleted, email hello@getbeep.app.

Keeping it safe

Only Beep's own servers can reach its database. Codes, keys and tokens are stored as hashes, and web addresses that Beeps forward to are stored encrypted. Every post an AI reads is marked as written by a person, never as an instruction.

Children

Beep isn't for children under 13, and we don't knowingly keep their information. If you think a child has used Beep, tell us and we'll delete it.

Changes

When Beep changes what it keeps or how it uses it, this page changes first, with a new date at the top. Questions go to hello@getbeep.app.