Privacy

besummoned has no user accounts and collects as little as it can. This page describes everything the service stores, whether you use it in a browser or through an AI assistant such as ChatGPT or Claude.

What is stored

An event stores what its host typed: title, time, place, description and the registration settings. Signing up for an event stores the name you give, and your email address when the host asked for one. That is the complete list; there are no profiles, no tracking of who viewed what, and no advertising.

Cookies

Two functional cookies exist. One remembers that your browser created an event, so you can manage it later. The other remembers the name and email you last signed up with, so you can cancel your own registration. Neither identifies you personally and neither is shared with anyone.

Using besummoned from ChatGPT or Claude

When you create or join an event through an AI assistant, the assistant sends besummoned the same details the web form would: the event fields, or your name and possibly email when joining. Nothing else about your conversation reaches besummoned. What the assistant itself stores is governed by its own privacy policy.

Who can see what

Event pages are visible to anyone who has the link, which is how invites work. The guest list shows names only, and only when the host has not hidden it. Email addresses are never shown on the event page and never handed out through the API.

Where it lives, and how long

Event data is stored with our database provider (Neon) in the EU, and the site runs on Vercel, whose analytics count page views without cookies or personal identifiers. Events stay until their host deletes them. Removing yourself from a guest list deletes your name and email from that event immediately.

Getting something removed

Hosts can delete their events themselves, and guests can remove their own registration from the event page. For anything else, reach out on Bluesky and it will be handled manually.