Pressly (“we,” “us,” or “our”) builds a browser extension that turns news articles into short video briefs. This policy explains what we collect, why, and the choices you have. We keep it short because we keep our data practices small.
Information we collect
Pressly requires an account. When you sign up we store your email address and authentication details through our auth provider (Supabase), and we count how many briefs you generate each month so we can enforce your plan’s limit. For Unlimited subscribers, our payment processor (Stripe) handles billing details — we never see or store your card number.
Article content you convert
When you convert an article, the extension reads that page’s text in your browser and sends it to our servers, where it is passed directly to the summarization service that writes your brief. We never write the article body to our database. It exists only in memory for the seconds it takes to produce the summary, and is then discarded.
The article’s link, title, and summary are held only long enough to hand the finished brief to your browser. Narration audio is generated moments after you convert, not during your original request, so we hold those few details until your browser confirms it has downloaded the brief — typically a few seconds — and then delete them entirely. Anything never collected (for example, if you close your browser before the brief arrives) is deleted automatically within 24 hours. We do not build a profile of your reading habits beyond the usage counts needed to enforce plan limits.
Images, audio, and your briefs
The pictures and animations in a brief are fetched by the extension directly from Google Image Search, from your own browser, and are stored only in your browser. They never reach our servers. Because the request is made from your browser as a normal search, Google receives it with your usual Google session and IP address — the same as if you had searched Google Images yourself. Pressly does not send these searches to its own servers, does not store them, and does not use them to profile you; they exist only to find imagery for the brief you asked for.
The narration audio is generated on our servers and held only until your browser downloads it, at which point our copy is deleted. Finished briefs live in your browser’s local storage, not with us.
Problem reports
If a page fails to convert, Pressly offers to send us a report. Only if you choose to send it do we receive that page’s link and title, the reason it failed, and your browser’s user-agent string. We use these solely to fix extraction bugs.
Analytics
We use PostHog to understand how Pressly is used — for example, that a conversion succeeded or failed, which site it came from, the article’s language, and how long it took. These events are tied to your account identifier so we can debug problems and measure whether the product works. We do not send article text, article links, or images to our analytics provider, and we do not use analytics for advertising or cross-site tracking.
How we use your information
We use your email to authenticate you, send essential service notifications, and respond to support requests. We use usage counts (such as briefs generated this month) to enforce the 15-brief free limit and to improve the product. We do not sell your data, and we do not serve advertising.
What the extension can access
Pressly asks to run on any site, because a news article can be on any site and we cannot know in advance which pages you will want to convert. The extension reads a page’s article text only when you ask it to — by clicking Convert or using the right-click menu — and sends it to us only for that conversion. It reads nothing from pages you don’t convert, it never converts anything on its own, and it does not track your browsing.
Cookies and local storage
The extension stores your briefs, reading queue, and preferences locally in your browser. Our website uses essential cookies to keep you signed in. We do not use third-party advertising or cross-site tracking cookies.
Third-party services
We rely on a small set of trusted providers, each receiving only what it needs: Supabase for authentication; Stripe for payments; Google (Gemini) and Groq to summarize article text; Microsoft Azure to generate narration audio from that summary; Google Image Search for brief imagery (requested by your browser, not our servers); and PostHog for product analytics. Each is bound by its own privacy commitments.
Data retention
Article body text is never stored, so there is nothing to retain. A brief’s link, title, summary, and narration audio are deleted from our servers as soon as your browser confirms it has them — usually within seconds — and in every case within 24 hours. Your finished briefs live in your browser, not with us; deleting one there removes it. The only thing we keep is your account (email and billing reference) and your monthly brief count. If you delete your account from the Profile page, we remove those within 30 days, except where retention is required by law.
Your rights
You can access, correct, or delete your personal data at any time from your dashboard, or by emailing us. Depending on your location, you may have additional rights under the GDPR or CCPA, including the right to request a copy of your data or to object to certain processing.
Children's privacy
Pressly is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us data, contact us and we will delete it.
Changes to this policy
We may update this policy as the product evolves. Material changes will be announced on this page with an updated date, and where appropriate, by email. Continued use of Pressly after a change means you accept the revised policy.
Questions about your data?
Email us at privacy@getpressly.com and we’ll respond within a few business days.