What we can and cannot see

What is sent

When you start a run, the extension sends the titles and addresses of your open tabs, so the model can tell what they are. Page contents are not sent unless you turn on “read page content” in Options, which is off by default.

How it is protected

The request is encrypted in your browser to a key held only by the process that talks to the model, not merely to our server. TLS already stops eavesdroppers on the wire; this layer covers the two things TLS does not: a corporate proxy that terminates TLS with its own certificate, and our own infrastructure, which would otherwise see request bodies in load balancer logs, traces and crash reports.

The reply is encrypted the same way, because group names are made out of your tab titles.

What this does not do

It does not hide anything from the model provider. The model reads your tab titles; that is the product. Our provider does not train on API traffic.

What we keep

Your email address, and for each run: how many tokens it used, what it cost, and how long it took. Never the contents. Billing needs counts, not text, and the encryption above means the counts are all our own logs could hold anyway.