Privacy policy
Last Updated: October 19, 2026
At BriskRead, accessible from briskread.com, the privacy of our visitors is one of our primary priorities. This Privacy Policy document outlines the types of information we collect and record, and how we use it.
1. Client-Side Processing Assurance
Document privacy first. RSVP, bionic formatting, Text-to-Speech, PDF/EPUB extraction, and image OCR run locally in your browser. Pasted text and uploaded files are not stored on BriskRead servers.
Optional features that contact a network: (a) Extract URL, where our server fetches the public page you request; (b) AI, which calls Google with your own key stored only in your browser; (c) account authentication and aggregate reading totals through Supabase; and (d) the optional Chrome extension when you explicitly send an article to BriskRead.
1b. Chrome Extension
The BriskRead Chrome extension reads the text of a page only when you ask it to, with a keyboard shortcut, the toolbar button or the right-click menu. It uses four permissions. activeTab and scripting let it read and display the page you are on. storage keeps your settings, read-later queue, reading positions and optional Gemini key on your device. contextMenus adds the right-click options. Page text is processed in your browser and is not sent to BriskRead. If you use AI summary or questions, the text is sent from your browser directly to Google's Gemini API using your own key. "Speed read linked page" opens briskread.com with that link, and our server fetches that public page for you. The extension has no analytics, no tracking and no ads. Uninstalling it deletes all of its data. BriskRead's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
2. Information We Collect
If you create an account or contact us, we may collect minimal metadata:
- Contact information: Name, email address, and the contents of any message you send us.
- Account information: Email address and authentication identifiers. Passwords are handled by Supabase Auth and are not visible to BriskRead.
- Reading totals: Signed-in users may sync word counts, reading speed, session duration, and estimated time saved. Document text is not included.
3. Cookies and Web Beacons
BriskRead stores your reading preferences (theme, font family, font size, and WPM speed) in your browser's local storage so they persist between visits. They are not sent to our servers.
We also integrate third-party services that use cookies:
- Google Analytics: We use Google Analytics to collect aggregated site traffic and engagement metrics to improve the product.
- Google AdSense: Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to BriskRead and/or other sites on the Internet.
You can opt out of personalized advertising by visiting Google Ads Settings. You can also opt out of some third-party vendors' use of cookies for personalized advertising at aboutads.info. Visitors in the EEA, UK, and Switzerland are asked for consent before personalized ads are shown. See how Google uses data from sites that use its services.
4. Log Files
BriskRead follows a standard procedure of using log files. These files log visitors when they visit websites. The information collected by log files includes internet protocol (IP) addresses, browser type, Internet Service Provider (ISP), date/time stamp, referring/exit pages, and number of clicks. This data is not linked to any personally identifiable information and is used solely for analyzing administration trends.
5. Contact Us
Questions about this policy can be sent to privacy@briskread.com.