Privacy Policy

Wedding stories are personal. This page explains what the current Toast Check app stores and when a speaker may choose to share part of a toast.

Draft for review before publication. The operator identity, support contact, backup retention, hosting details, and OpenAI data terms have not been confirmed. This page is intentionally excluded from search indexing until those details are settled.

Information Toast Check handles

Organizers enter a wedding name, an optional date, and the names of invited speakers. Speakers write a toast in the app. Toast Check stores that writing, selected passage records used for comparison, possible-match warnings, and any excerpts the speakers explicitly choose to share.

The current app has no personal account or password. Private organizer and invitation links grant access. The app saves those access tokens in the iPhone Keychain; the server stores token digests. Anyone with a working private link may be able to use its access, so keep links private.

How the information is used

Toast Check uses wedding and invitation details to connect speakers to the right event. It compares passages from different toasts to flag possible repeated anecdotes. A warning is a suggestion, not a guarantee that a repeat has been found or that every repeat will be detected.

For semantic comparison, the backend sends toast passage text to OpenAI’s text-embedding-3-small API and stores returned vectors in PostgreSQL with pgvector. Review OpenAI service terms, retention settings, and the production operator’s agreements before publication.

What other people can see

An organizer sees invited speaker names and progress, not their toast text or excerpts. A speaker normally sees only their own writing. A possible-repeat warning does not identify or quote another speaker.

After a possible match, two speakers can separately agree to share their names and individually chosen excerpts for that story. A pending request does not reveal the other person’s name or chosen excerpt. Either speaker can end sharing. This does not remove any copy another person may already have made.

Storage, access, and deletion

The backend stores wedding details, speaker names, toast text, comparison data, and agreed excerpts in PostgreSQL. The iPhone app stores private access locally in Keychain. It also keeps unsynced writing there temporarily for recovery after a failed save or relaunch; this is not account recovery.

A speaker can delete their own invitation and writing from the app. An organizer can revoke an invitation or delete the wedding. Those actions remove the related records from the active database and stop the affected private link from working. Forgetting access on a device only removes local access; it does not delete server data. There is no organizer account recovery in this version.

Confirm backup retention, log retention, any legal retention requirements, and the final production hosting arrangement before publication.

This website

This static marketing site has no form, analytics script, or advertising tracker in its source. The web host may process basic request information to deliver the site. Review the production host’s logging, cookies, and analytics configuration before publication.

Questions or requests

Add a verified operator name and privacy contact before publication. For app guidance in the meantime, see Support.