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.

Who we are

[FOR REVIEW — legal entity name, registered address and, where required, an EU/UK representative.] Frasiey is operated by Warpspeed Technologies. For anything in this notice, write to hello@frasiey.com.

[FOR REVIEW — controller/processor split.] For account data (the people who sign in and administer meetings) we expect to act as controller. For caption content produced in a customer's rooms we expect to act as processor on that customer's instructions, under a data processing agreement. This needs to be confirmed and a DPA drafted.

Room audio

The Frasiey helper opens the microphone you select on the room's own machine, and the speech engine runs 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

Recognised sentences are sent to our API over TLS 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, either by a model running on Cloudflare Workers AI or by Anthropic's Claude API, depending on the meeting's settings.

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

[FOR REVIEW — retention.] Our intent is to keep caption sessions, segments and translations until the account deletes them or the account itself is deleted, with an account-level control to auto-delete after a chosen number of days. The default period and any hard maximum must be decided.

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 organisers can see whether the captions were used. We do not set advertising cookies, we do not build profiles of readers, and we do not sell anything to anyone.

[FOR REVIEW — reader telemetry.] The reader stores its language and display preferences locally in the browser. Confirm whether the coarse connection sample is personal data in the relevant jurisdictions and whether a cookie banner is required; on the current design we believe it is not, because nothing identifying is stored.

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.

Processors we use

• Cloudflare — hosting, database, object storage and the translation model.
• Anthropic — optional higher-quality translation, when a meeting enables it.
• Stripe — payments and subscription management.
• Resend — transactional email, including sign-in codes.

[FOR REVIEW — sub-processor list, locations, transfer mechanism.] This list must be published with each processor's role and processing location, and kept current, with a notification mechanism for changes.

Your rights

You may ask for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it. Account owners can export transcripts and delete meetings themselves at any time from the dashboard. Write to hello@frasiey.com and we will respond.

[FOR REVIEW — statutory response windows, identity verification, the right to lodge a complaint with a supervisory authority, and the named authority.]

Security

Everything travels over TLS. Device credentials and sign-in codes are stored as hashes. Access to production data is limited to the people who operate the service. We have not yet completed a formal security certification. [FOR REVIEW — incident notification commitment and timescale.]

Changes

When this notice changes materially we will say so on this page and, for account owners, by email. [FOR REVIEW — notice period.]

Draft revision — not yet reviewed by counsel · 2026