What we keep, and why.

Who we are

Sagena is made by The Bloom House, 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 everything and remove it. 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).
• 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. Anthropic does not train 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.

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. When a venue closes its account, or asks, we delete its data 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), Stripe (billing), Resend (transactional email from Sagena itself), and Google (Gmail, 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.