Privacy at Trippi Cue

1. What the extension listens to

Only the sound of the meeting tab, and only after you click the extension icon in that tab. Chrome grants tab audio through the activeTab permission, which requires that click every time — there is no way for the extension to start listening on its own, and it never touches your microphone or any other tab.

While it is listening, the extension shows it. Closing the window or stopping it in the popup ends the capture.

2. Where the audio goes

The audio is streamed from your browser directly to our speech-to-text provider, Soniox, over an encrypted WebSocket. It does not pass through our backend, and we neither record nor store it. The connection is opened with a short-lived session token that our backend issues for that one session; it is not an account key and it expires in minutes.

The provider returns text. Its own handling of the stream is governed by its terms as a processor for us.

3. What is sent to us, and why

To write an answer, the extension sends our backend a short rolling window of the meeting — about a dozen of the most recent recognised lines, the speaker labels, the participant names visible in the call, and your own name if the extension detected or you set it. Your name and the speakers matter for one reason: without them the model cannot tell a question asked of you from a question asked of somebody else.

Our backend turns that window into a prompt and asks a language model for a short answer. The model provider is Groq today; a build may be configured to use Anthropic Claude instead. The provider receives the prompt, returns the answer, and acts as a processor for us.

That text is used and dropped. It is not written to our database, and it is deliberately kept out of our error logs — when a model call fails, we log the provider and the status code, never the meeting.

4. What we do keep

Three things, none of which is the content of a meeting:

• An install record. When the extension is installed it registers with our backend and receives an anonymous identifier and a token. That record holds the identifier, the token hash and when the install was last seen — no name, no email, until you sign in.
• Counters. How many answers were shown to that install and how much meeting time it used, per day and per month. This is what your plan is measured against.
• An account, if you make one. Signing in stores your email address and links the install to it, so a plan bought on one machine works on another.

5. Payments

Plans are sold through Paddle, which acts as the merchant of record. Card details are entered on Paddle’s side and never reach us; we receive the fact of a subscription and its state.

6. Who else sees anything

• Soniox — the audio stream, to turn it into text.
• Groq, or Anthropic where a build is configured that way — the prompt built from the meeting window, to write the answer.
• Paddle — billing data, if you buy a plan.

Nobody else. We do not sell data, we do not run advertising, and this site carries no analytics or tracking scripts at all.

7. What we never do

• Record or store the audio of your meetings.
• Keep a transcript, a summary or a history of your calls.
• Join your call as a participant or a bot.
• Read tabs other than the meeting tab you started it in.
• Use your meetings to train models of our own.

8. Your rights and how to use them

Write to [email protected] and ask for a copy of what is stored about your account, or for its deletion. Deleting the account removes the account record, the installs linked to it and their counters.

Removing the extension stops all processing immediately: with the extension gone, nothing is captured and nothing is sent. The install record and its counters stay until you ask for the account to be deleted.

9. Changes

If the product starts doing something this page does not describe — storing a transcript, say — this page changes in the same release, not after it. The date at the top is the date of the last change.