Privacy

What we keep, and why.

Sagena is software for wedding venues. It reads the venue's email with couples, remembers what was said, and helps the venue reply. That only works if venues trust us with their inbox, so this page says plainly what we do with it.

Last updated 15 November 2026.

Who we are

Sagena is made by Sagena LLC, the company behind Rixey Manor in Rixeyville, Virginia. Questions about this policy go to isadora@sagena.ai. We answer them ourselves.

Two kinds of people

Venuesare our customers. They sign up, connect their accounts and decide what Sagena does. For a venue's data, we are the processor and the venue is the controller.

Couples write to venues. We hold their messages because the venue asked us to. If you are a couple and want to know what a venue holds about you, ask the venue first. They can see what they hold about you, and pass a request to delete it on to us. If that does not work, write to us.

What we collect

  • Account details: name, email address, venue name, billing through Stripe. We never see card numbers.
  • Email between the venue and couples, when the venue connects Gmail (see below).
  • Transcripts of recorded Zoom calls, when the venue connects Zoom (see below).
  • What the venue types into Sagena: notes, pricing, rules for how Sage should write, the venue's own voice.
  • Usage: which pages are used and when, errors, and how much AI each venue uses, so we can bill fairly and fix what breaks.

Gmail

A venue can connect one or more Gmail accounts to Sagena. We ask Google for two permissions and no more:

  • Read mail(gmail.readonly). Sagena reads incoming and sent messages so it can find the couples in them, keep each couple's history in one place, and draft replies in the venue's voice.
  • Send mail(gmail.send). When the venue approves a reply, Sagena sends it from the venue's own address, so couples get a normal email from the venue.

What we do with what we read:

  • We store the messages and the facts drawn from them (names, dates, guest counts, budgets, what was asked) in the venue's private account.
  • We pass message text to our AI provider, Anthropic, to draft replies and pull out those facts. If Anthropic cannot answer, the same text goes to OpenAI as a backup. Neither trains models on it.
  • We do not use Gmail data to train general AI models, and we do not let anyone else.
  • We do not sell it, share it with advertisers, or show it to anyone outside the venue's own staff and the people who run Sagena when they need to fix a problem.
  • We never read mail unrelated to the venue's work on purpose. The connection covers the whole inbox because Google offers no narrower permission for reading replies to the venue, so connect a work account, not a personal one.

Sagena's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Taking it back.A venue can disconnect a Gmail account on its Settings page at any time. Disconnecting revokes our access with Google and deletes the stored login tokens straight away. Mail already stored stays in the venue's account until the venue removes it or asks us to. A venue can also cut us off from Google's side at myaccount.google.com/permissions.

Zoom

A venue can connect its Zoom account so that the transcript of each recorded tour or call lands on the right couple in Sagena. Sagena's own Zoom app is waiting on Zoom's review. Until it is through, a venue can connect a private app it makes in its own Zoom account instead (see “Your own Zoom app” below). Sagena's own app asks Zoom for three permissions and no more:

  • Who you are (user:read:user), so we know which Zoom account is connected.
  • Your list of cloud recordings (cloud_recording:read:list_user_recordings), so we can see which calls have a transcript.
  • The recording files (cloud_recording:read:list_recording_files), to download the transcript of each call. We read the transcript only, never the video or the audio.

What we do with what we read:

  • We store each transcript, with the meeting's topic, time and the names of the people on it, in the venue's private account, against the couple the call was with.
  • We pass transcript text to our AI provider, Anthropic, to work out what the call was about and who it was with. If Anthropic cannot answer, the same text goes to OpenAI as a backup. Neither trains models on it.
  • We cannot start, schedule, change or delete anything in Zoom, and we never record a call ourselves. A call has a transcript only if the venue recorded it in Zoom.
  • We do not sell Zoom data, share it with advertisers, or show it to anyone outside the venue's own staff and the people who run Sagena when they need to fix a problem.

Taking it back.A venue can disconnect Sagena's own Zoom app on its Settings page at any time. Disconnecting hands our access back to Zoom and deletes the stored login tokens straight away. A venue can also remove Sagena in the Zoom App Marketplace, under Manage, then Added Apps. Zoom then tells us, and we delete the stored login tokens. Transcripts already in Sagena stay in the venue's account until the venue asks us to remove them, and we delete them within 30 days of being asked.

Your own Zoom app.A venue can instead make a small private app in its own Zoom account and give Sagena the app's three values. That app has the same three read permissions, in the form Zoom gives an app that works across the venue's Zoom account (each one ends in :admin). Those permissions reach every user on the venue's Zoom account, but we read only the recording lists and transcripts of the Zoom users the venue adds in Sagena, never the video or the audio. We store the app's secret encrypted and never show it again, and we treat what we read exactly as above. A venue can remove each Zoom user it added on the same Settings page, which deletes the stored values straight away. Deleting the app, or changing its secret, in the venue's own Zoom account stops our access at once. It does not remove the stored values: they stay until the venue removes them in Sagena, or until we clear them when the account is archived, 30 days after its plan ends.

Where it lives

Data is stored with Supabase on servers in the United States (AWS, Ohio) and the app runs on Vercel. Both encrypt data at rest and in transit. Each venue's data is kept apart from every other venue's at the database level.

How long we keep it

For as long as the venue's account is open. Thirty days after a venue's plan ends, the account is archived and kept for 12 months, with an email a month before we delete it. If a venue asks us to delete its data sooner, we do, within 30 days. Backups clear within 30 days after that. We keep billing records for as long as tax law asks.

Who else touches it

Only the services we need to run: Supabase (database), Vercel (hosting), Anthropic (AI drafting), OpenAI (AI drafting, only when Anthropic cannot answer), Stripe (billing), Resend (transactional email from Sagena itself), Google (Gmail, when connected) and Zoom (call transcripts, when connected). Each one holds only what its job needs. We do not sell data, and we do not use third-party advertising trackers.

Your rights

Ask us what we hold about you, ask for a copy, ask us to correct it, or ask us to delete it. Write to isadora@sagena.ai and we will answer within 30 days. If you are in the UK or EU, you also have the right to complain to your data protection authority.

Changes

If this policy changes in a way that matters, we email every venue before it takes effect. The date at the top is the date of the current version.

See also contact.