What this does.

Group scheduling the whole group negotiates. The date can be settled before anyone is invited: a gathering links a Cachet Coordinate page, where members enter availability and the group converges on a time together. Mechanism: the Coordinate engine on Cachet Calendar, linked by URL from the gathering.

Import the guest list you already have. Upload a CSV or tab-separated export; the importer proposes what each column holds and shows you your own rows read that way before anything is created. Mechanism: an RFC-4180 reader (quoted commas, embedded newlines, doubled quotes, byte-order marks, CRLF) with delimiter sniffing, plus heuristic column detection that is always confirmed by a human, including an optional dietary column. Works with any CSV or tab-separated export, and with any spreadsheet saved as CSV.

Re-import without damage. Importing a refreshed export matches people who are already on the roster instead of replacing them. Mechanism: match on address first; a row with no address joins the single roster person of that name who also has no address, and anyone else is added as a new person, with people who share a name shown together for the organizer to merge (a merged person keeps every reply and both links). Blank fields fill in; nothing filled in is overwritten. Invitation links keep working and replies survive.

Guests never need an account. Every guest gets a personal link that opens their own invitation and records a reply in one tap. Mechanism: a per-guest token that resolves inside one gathering and nowhere else. No app, no password, no sign-up.

The invitation can ask, and the group remembers the answer. The organizer chooses whether to ask what a guest cannot eat and whether they are bringing anyone. Mechanism: an answer given by a guest is kept in that person's record in the group and carried into every later gathering, and the guest can correct it from any later invitation. The organizer's own note is a separate field beside it, shown only to the organizer: neither one overwrites the other.

A roster that outlives one gathering. A group holds the people, their companies, their dietary notes, and what the organizer needs to remember, so a second gathering starts from a list that already exists. Attendance history is derived from the gatherings themselves rather than stored separately, so it cannot disagree with a reply somebody actually sent.

The data is yours, at any moment, without asking. Full CSV export of a gathering's roster and of a group's people, always available from the organizer link, never gated behind a plan or a support request.

Every page and export is constrained to one gathering or one group: a token or key resolves to a single object, never to an account-wide query. The link-preview image a gathering generates carries only its name, dates and venue, and the guest count when it fits (or only the product's own card, at the organizer's choice), because crawlers fetch that image with no token at all. Analytics record page views and which steps were used, from a closed list of event names that cannot contain a person, an address, or a gathering's title; every address is reduced to its route shape and the page title is dropped before anything leaves the browser, and Do Not Track is respected.