Privacy Policy

Last updated: October 2, 2026

This policy covers the Glipsy browser extension (voice typing and read-aloud for the websites you visit) and the glipsy.com website. In short: we collect the minimum needed to sign you in and to run voice typing and read-aloud, we never sell your data, and the extension sends us nothing from a page until you start one of those two features there.

What we collect and why

• Account information. When you sign in with Google (through our authentication provider, WorkOS), we receive your name and email address. We use them to create your account and track your plan and usage limits.
• Voice recordings. When you start voice typing, your audio is sent to our servers and transcribed to text by our speech providers. The transcript is typed into the text field you were in. Recording only happens when you start it, and stops when you finish or discard the take.
• Where you're typing. Each voice take also sends the page's address, title and description, and a short stretch of the text just before and after your cursor in that field. All of it goes to our servers. Only a shortened piece of that surrounding text goes on to the speech provider, so names and terms come out spelled the way the page spells them.
• Text you choose to hear. When you start read-aloud, the text you picked (your selection, or the message whose read-aloud button you pressed) is sent to our servers and on to our speech providers to generate the audio. We also receive that text's markup as it sits on the page (its formatting, and things like link addresses inside it), so lists, code and headings are read properly, and the page's address.
• Usage data. We track how much voice typing and read-aloud you use, to enforce plan limits and show them in the extension popup.
• Payment information. Paid plans are processed by Stripe. We never see or store your card details; we keep only your subscription status.
• Product analytics. The extension reports usage events (for example that it was installed or removed, that you signed in, started voice typing or played a reply, and which version) to our analytics provider, PostHog. On the AI chat sites where Glipsy adds its own buttons, an event also names that site; on any other page it only says "other". Events are keyed by a random id the extension generates at install. They never include what you type, say, or read. Our server also syncs your account name, email, and lifetime voice typing and read-aloud totals to your PostHog person profile, including if you have not used the extension since analytics began. WorkOS signups that have not completed Glipsy account setup appear there with zero usage. Right after install, the extension opens a welcome page on glipsy.com with that id, which links the install to your earlier visits to the website.
• Website analytics. On glipsy.com (not in the extension) we use PostHog to understand how visitors use the site: pages viewed, clicks, where you came from, and session recordings of your visit to the site. PostHog sets a cookie so we can recognize a returning visitor. It doesn't know who you are unless you later sign in to the extension.

What stays on your device

Your preferences and your signed-in session are stored locally in your browser's extension storage. Uninstalling the extension removes them.

What we don't do

• We don't sell or rent your data to anyone.
• We don't show ads or use your data for advertising.
• We don't track your browsing. The extension is available on the pages you visit so its shortcut works there, but it sends us nothing from a page until you start voice typing or read-aloud on it. When you do, we receive only what's listed above.
• We don't use your recordings or text to train AI models.

Service providers

We share data only with the processors needed to run the service: WorkOS (sign-in), our speech-to-text and text-to-speech providers, Stripe (payments), PostHog (product analytics), and our hosting providers. Each receives only what its role requires.

Retention and deletion

We don't keep your audio once it's transcribed. We do keep the transcript, the text you had read aloud, and the markup and page details sent with them, alongside your account and usage records, to run and troubleshoot the service. They're kept while your account is active. To delete your account and its data, email support@glipsy.com and we'll take care of it.

Security

All data travels over HTTPS, and access to production systems is restricted to the people who operate the service.

Changes

If this policy changes, we'll update this page and the date above.

Contact

Questions or requests: support@glipsy.com.