Privacy

The short version

Meeting audio is transcribed on the customer's own computer and is never sent to us. What reaches Frasiey's servers is caption text, the translations of that text, and the bookkeeping needed to run an account: who signed in, which rooms were captioning, for how long, and how many people were reading.

• What leaves the room. The text, never the audio. Room audio.
• How long a meeting's words are kept. For the number of days that meeting chose, and until the meeting or the account is deleted where it chose no number. How long we keep it.
• Who else sees them. A short list, each one with a single job. Who else sees it.
• What you can ask for. A copy, a correction, a deletion, and five more. Your rights.
• Who to write to. privacy@frasiey.com, and we answer within one month.
• Where the agreement is. The data processing agreement, which applies without anybody signing anything.

Who we are

Frasiey is operated by Frasiey LLC, a North Carolina limited liability company. For anything in this notice, write to privacy@frasiey.com.

Two halves, and we are a different thing in each

For what is said in your meetings, and everything around it, the organization that runs the meeting decides and we act on its instruction. That covers the words spoken in a room, the schedule, the names on it, and the list of names and terms a meeting keeps. Our duties there are written out in the data processing agreement, which applies without anybody signing anything.

For your own account, meaning the people who sign in, their names and email addresses and your billing, we decide and we answer for it ourselves. That half is what the rest of this notice is mostly about.

Room audio

The Frasiey app opens the microphone you select on the room's own machine, and the speech is turned into text on that machine. Audio frames are held in memory only for as long as recognition needs them. Frasiey does not record, store, or upload audio, and provides no way for us to listen to a room.

Consequently there is no audio for us to disclose, lose, or be compelled to hand over. If your venue or jurisdiction requires notice that a room is being transcribed, that notice is the customer's responsibility. The printable room signs are a reasonable place to put it.

Caption text and translations

Recognized sentences are sent to us over an encrypted connection and stored against the meeting, the room and the session so that readers can catch up, transcripts can be downloaded, and translations can be produced. Translation is performed by machine on Cloudflare Workers AI, the default for every meeting. No meeting can choose Anthropic for translation.

A meeting can also switch on Correct names and terms, which is off unless somebody turns it on. With it on, each finished sentence is sent to Anthropic, together with that meeting's own list of names and terms, and comes back with those names spelled the way the meeting spells them. With it off, no caption text is sent for correction.

Caption text often contains personal data, because people say names out loud. Treat a transcript as you would treat minutes of the meeting.

A meeting can also switch on Summaries, off unless an operator turns it on, for the whole meeting or one room at a time. While it is on, the finished caption text of a session is sent to Anthropic and comes back as a short summary, which is stored with the meeting; anyone with the room's own link can read it on their phone while the session is on, and afterwards too if the operator has also turned on past sessions. The meeting's name, the room's name and the language it is spoken in, the session's title with its speaker names, and the date go with the caption text, so the summary can say what was discussed and who said it; no attendee's name, no access code and no email go with it. From the meeting's Summaries tab, an operator can open a finished summary with Read and hide it with Hide from phones: attendees stop seeing it on their phones within a minute, though we keep it the way we keep the rest of the transcript, and Show again puts it back.

Suggested terms, and your slides

When somebody presses Suggest terms on a meeting, Frasiey sends that meeting's name, its organizer, its dates, its room names, and the session titles with the speaker names and affiliations, to Anthropic, along with any link or note the person adds and the words already on that meeting's list, so that a list of words the rooms are likely to hear comes back. It happens only when the button is pressed, and no caption text, no audio and no reader data go with it. The suggestions are proposals until somebody accepts them.

Importing a schedule works the same way. When Frasiey cannot tell which column of your file is which, or which of your rooms a label in it means, somebody can press Let Frasiey try. That sends the file's column headings, up to six of its first rows (with anything that looks like an address taken out first), the meeting's room names and the room labels your file uses to Anthropic, and the answer comes back as a suggestion for that person to check. It happens only when the button is pressed, and no caption text, no audio, no reader data and nothing else from the file go with it.

Three things in Frasiey send text to Anthropic, and these are all of them. The first is suggestions somebody asks for: Suggest terms and, on a schedule import, Let Frasiey try, both above, which happen only on those buttons. The second is Correct names and terms, which a meeting switches on for itself: each finished caption sentence is then sent to Anthropic with that meeting's own names and terms, to be spelled correctly. The third is Summaries above, which a meeting switches on for itself: the finished caption text of a session is then sent to Anthropic, with the meeting's name, the room's name, the session's title and its speakers, and the date, to write the summary. So caption text reaches Anthropic only for a meeting that has turned on Correct names and terms or Summaries, and neither is on unless somebody turns it on. Translation is not one of them. Nothing else goes: not room audio, which never leaves the room's own machine, not what readers do, and not your account or payment details.

Anthropic deletes what we send it within 30 days and does not use it to train anything. Because these three send what people said or typed to another company, the console asks the first person who turns one on to say they understand that, once per account, and nothing is sent until somebody does.

If you add your slides in the Frasiey app on the room's laptop, Frasiey reads the words on those slides and in the speaker notes, and uses them to spell names and product words correctly. Those words leave the laptop as text, the same way the captions themselves do, and they are held with the meeting. The slide file itself is never uploaded, and Frasiey keeps no copy of it. If your slides carry something that should not leave the room, do not add them.

Readers

Reading a room requires no account and no sign-in. We record a coarse sample of how many readers are connected to a room over time, and the reading language they chose, so that organizers can see whether the captions were used. Nobody is identified by it. We do not set advertising cookies, we do not build profiles of readers, and we do not sell anything to anyone.

Account data

To run an account we hold: the email address you sign in with, your name if you give one, which accounts you belong to and in what role, sign-in session records, an audit log of administrative actions, and the meetings, rooms and devices you create. Sign-in is by emailed six-digit code; we store a hash of the code, not the code.

Payments

Payments are processed by Stripe. Card details are entered on Stripe's own pages and never reach Frasiey's servers. We store Stripe's customer and subscription identifiers and the metered usage totals we report for billing.

What we hold, why, and on what footing

The law asks us to name a basis for each thing we do. Here they are, in one place.

How long we keep it

Two clocks run on the words spoken in a meeting, and a page that names only one of them is a page that is not true. Both are here.

Who else sees it

• Cloudflare: hosting, database, object storage and machine translation.
• Anthropic: the suggested terms and schedule columns a planner asks for, correcting names and terms in caption text when a meeting switches that on, and writing the summaries a meeting turns on.
• Stripe: payments and subscription management. Stripe also uses payment data for its own fraud checks and its own legal duties, and decides that use itself.
• Resend: transactional email, including sign-in codes. Resend holds that mail in the United States.
• Google or Microsoft: only where your account signs in with them. They see who signed in, and nothing from a meeting.
• Zoom or Microsoft Teams: only where an operator pastes a caption link for a meeting, which sends that room's finished caption lines to it.

What each one does, where it does it, and where it publishes its own promises are listed on our providers page, with a dated log of what has changed. We give account owners 30 days' notice by email before a new provider handles personal data.

Where it goes

Your data may be processed in the United States. Cloudflare, Stripe, Anthropic and Resend have each signed the European Commission's standard clauses with us; Cloudflare, Stripe and Anthropic also rely on the Data Privacy Framework. Where your account signs in with Google or Microsoft, or an operator sends captions to a Zoom or Teams meeting, that transfer runs under your own agreement with that company rather than ours.

Your rights

• Access. Ask us what we hold about you.
• A copy. Ask for a copy you can take elsewhere. Any member of a account can download a copy of the account from account settings, without asking us: its meetings, rooms, laptops, settings, schedule, list of names and terms, and every transcript with its translations.
• Correction. Ask us to fix anything that is wrong.
• Deletion. Ask us to delete it. An owner can delete a whole account from account settings, and an operator can delete a meeting.
• Restriction. Ask us to stop using it while something is being sorted out.
• Objection. Object to anything we do because it is in our own legitimate interest to do it.
• Consent. Where you gave consent, you can withdraw it at any time, by turning off the switches that send text to Anthropic. Withdrawing it does not undo what was done before.
• Complaining. You can complain to your data protection supervisory authority. We would rather you told us first, but you do not have to.

We answer within one month; if a request is complex we may take up to two more and will tell you. We check who you are by asking you to reply from the email address the account uses, because that is the address the service already trusts.

For the words spoken in a meeting, ask the organization that ran the meeting; we act on their instruction. If you write to us about a meeting, we will pass it to them.

Cookies

Two cookies, and this is both of them.

We set no other cookies, and no cookie is used to track you across sites. That is why there is no cookie banner on this site: there is nothing to ask you about. The fonts and everything else a page needs are served from frasiey.com, so opening a Frasiey page tells nobody else that you did.

The sign-in cookie is sent to every frasiey.com address, including the pages your attendees read, and only the sign-in service ever reads it. Nothing on a reader's phone asks for it.

The reader itself sets no cookie at all. The phone remembers the language it is reading in, the room code as it was typed, the display settings somebody chose, and any caption lines they saved, in that browser and nowhere else. The reading language and the room code are sent to us with each read of the captions, because the phone needs them to get the right words and to be let in. The display settings and the saved lines never leave the phone, and neither does anything typed into the reader's search, which looks through the captions on the phone itself.

Security

Everything travels encrypted in transit. Device credentials and sign-in codes are stored as hashes, and a request for another organization's meeting is answered as if it did not exist. Access to production data is limited to the people who operate the service. The whole of it, including what our providers hold and what Frasiey can honestly claim for itself, is on the security page.

If something goes wrong

If we learn of a breach affecting your data we will tell you without undue delay, and the relevant authority within 72 hours where the law requires it.

Children

Frasiey is for organizations. An account is for an adult acting for one. The service is not designed for children and we do not knowingly hold a child's data.

Machines, and what they do not decide

Recognition, translation and the correction of names are done by machines, without a person reading along. None of them makes a decision about anybody: nothing in Frasiey scores you, ranks you, profiles you or decides anything that affects you.

Changes

This notice is dated at the top. When it changes materially we will say so on this page and tell account owners by email.