Privacy Policy — Bookbeam

Privacy Policy

Chrome Extension — Send articles and videos to your e-reader

Effective: March 18, 2026

1 Who We Are

Bookbeam is operated by Michał Włosik EFC, ul. Północna 16/5, 54-105 Wrocław, Poland (NIP: 8942747708). In this policy, "we", "us", and "our" refer to the operator. "You" and "your" refer to you, the user of the Bookbeam Chrome extension and associated services (collectively, the "Service").

2 What Bookbeam Does

Bookbeam is a Chrome extension that converts web articles and YouTube video transcripts into EPUB files and delivers them directly to your e-reader device. Supported delivery methods include Dropbox, Google Drive, e-reader email (Kindle, Kobo, reMarkable, PocketBook), and a temporary download link.

When you send an article, Bookbeam extracts the visible text content of that page from your browser, cleans and reformats it using an AI model, packages it as an EPUB, and delivers it via your chosen method. For YouTube videos, Bookbeam fetches the public transcript and optionally generates an AI summary.

Bookbeam only reads the content of the specific page you actively choose to send. It does not monitor your browsing activity, read other tabs, or collect any data in the background.

3 Eligibility

Bookbeam is intended for users aged 16 and older. By using the Service, you confirm that you are at least 16 years of age. We do not knowingly collect data from anyone under 16. If we learn that a user is under 16, we will promptly delete their account and associated data.

4 Data We Collect

4.1 Account Data

When you create an account, we collect:

  • Email address — used for authentication and account management.
  • Display name and profile photo — provided by Google if you sign in with Google OAuth; used for display within the extension.
  • Authentication tokens — stored locally on your device and managed server-side via Supabase Auth to keep you signed in.

4.2 Delivery Connection Data

If you connect a cloud storage provider, we store:

  • Dropbox — OAuth access and refresh tokens, and your Dropbox account email, stored server-side. Used exclusively to upload EPUB files to your Dropbox on your request.
  • Google Drive — OAuth access and refresh tokens, and your Google account email, stored server-side. Used exclusively to upload EPUB files to a Bookbeam folder in your Google Drive.
  • E-reader email address — the device email you provide (e.g. your Kindle address) is stored in your settings and used only to send EPUB files.

OAuth tokens for Dropbox and Google Drive are stored server-side and are never exposed in the extension's client code. They are used only when you actively trigger a send.

4.3 Article and Video Content

When you choose to send a page, the extension extracts the visible text content of that page. This content is:

  • Sent to our server for AI-assisted cleaning and EPUB generation.
  • Passed transiently to Google's Gemini API for cleaning and reformatting.
  • Stored temporarily (up to 24 hours) in our transit storage as an EPUB file awaiting delivery.
  • Not permanently stored — article and video content is deleted from our servers after successful delivery, or after 24 hours at the latest.

4.4 Send History

For each successful send, we record:

  • Article or video URL and title — displayed in your extension history tab and used for quota enforcement.
  • Delivery method — e.g. Dropbox, Google Drive, email, or link.
  • Content type — article or YouTube video.
  • Timestamp and file size — for usage tracking and debugging.

4.5 Settings and Preferences

Your configuration choices (delivery method, language, article options, YouTube mode) are stored locally in the extension's browser storage and synced to our server so they persist across devices and reinstalls.

4.6 Subscription Data

We store your subscription status, plan level, and trial period information. If you purchase a paid plan, payment is handled by Polar.sh (see Section 6). We receive only the resulting subscription status and Polar customer identifier — not your payment card details.

5 How We Use Your Data

  • Provide the service — authenticate your account, convert pages to EPUBs, and deliver them via your chosen method.
  • AI cleaning and reformatting — relay extracted article text to Google Gemini to produce clean, well-structured EPUB content.
  • YouTube transcripts — fetch public transcripts and optionally generate AI summaries for readable EPUB scripts.
  • Quota enforcement — track daily send counts against your plan's limits.
  • Settings sync — persist your preferences across devices.
  • Send history — display your past sends in the extension's history tab.
  • Customer support — respond to enquiries sent to our contact email.
  • Billing — manage your subscription via Polar.sh.

6 Third-Party Services

Bookbeam relies on the following third-party services to function:

Google Gemini — AI Article Cleaning
  • Extracted article text is sent to Google's Gemini API via our server-side edge function for cleaning, formatting, and optional translation into EPUB-ready HTML.
  • Content is processed in real time and is not permanently stored by us or logged to Gemini after processing.
  • Terms: ai.google.dev/terms
Supabase — Backend Infrastructure
  • Handles user authentication (email/password and Google OAuth).
  • Stores account data, delivery connection tokens, settings, subscription status, and send history.
  • Provides temporary file storage for EPUB transit files, which are deleted within 24 hours.
  • Hosted in the EU West region.
  • Privacy policy: supabase.com/privacy
Dropbox — Optional Cloud Delivery
  • If you connect Dropbox, EPUB files are uploaded to your Dropbox via the Dropbox API using OAuth tokens you have authorised.
  • We access only the specific folder used for delivery. We never read, browse, or index other files in your Dropbox.
  • Privacy policy: dropbox.com/privacy
Google Drive — Optional Cloud Delivery
  • If you connect Google Drive, EPUB files are uploaded to a dedicated Bookbeam folder via the Drive API using OAuth tokens you have authorised.
  • We request only the drive.file scope, limiting access to files created by Bookbeam.
  • Privacy policy: policies.google.com/privacy
Resend — E-reader Email Delivery
  • If you use e-reader email delivery, EPUB files are sent as email attachments via Resend's API from the address deliver@bookbeam.tools.
  • Privacy policy: resend.com/privacy-policy
Polar.sh — Payment Processing
  • If you subscribe to a paid plan, payment processing is handled by Polar.sh. We do not receive or store your payment card details.
  • Privacy policy: polar.sh/legal/privacy

7 Data Sharing

We do not sell, rent, or trade your personal data. We share data only in the following circumstances:

  • Third-party service providers — as described in Section 6, strictly to operate the Service's core functionality.
  • Legal obligations — if required by applicable law, regulation, or valid legal process.
  • Business transfers — in the event of a merger, acquisition, or sale of assets, your data may be transferred to the successor entity.

8 Data Retention

  • Account data — retained for as long as your account exists. If you delete your account, your data is removed within 30 days.
  • Delivery connection tokens (Dropbox, Google Drive) — retained until you disconnect the provider or delete your account.
  • Article and video content / transit EPUB files — automatically deleted from our servers within 24 hours, or immediately after successful delivery.
  • Send history — retained for the duration of your account. You may request deletion at any time.
  • Settings and preferences — retained for the duration of your account. Local browser storage is cleared when you uninstall the extension.
  • Subscription data — retained for billing and quota enforcement for the duration of your account.

9 Data Security

We implement the following measures to protect your data:

  • All communication between the extension, our servers, and third-party APIs uses HTTPS/TLS encryption.
  • OAuth tokens for Dropbox and Google Drive are stored server-side — never in the extension's client code or browser storage.
  • API keys for third-party services (Gemini, Resend, etc.) are stored as server-side environment variables and never exposed to the extension client.
  • Authentication tokens are securely managed via Supabase Auth with automatic refresh.
  • User data in Supabase is protected by row-level security policies — each user can only access their own data.
  • The Supabase backend is hosted in the EU West region.

No system is perfectly secure. While we take reasonable precautions, we cannot guarantee absolute security of data transmitted over the internet.

10 Your Rights

Depending on your jurisdiction, you may have the following rights regarding your personal data:

  • Access — request a copy of the personal data we hold about you.
  • Rectification — request correction of inaccurate data.
  • Erasure — request deletion of your account and associated data.
  • Portability — request your data in a structured, machine-readable format.
  • Objection — object to processing of your data for certain purposes.
  • Restriction — request that we limit how we process your data.

To exercise any of these rights, contact us at hello@bookbeam.tools. We will respond within 30 days, or within the timeframe required by applicable law.

11 International Data Transfers

Our authentication and storage infrastructure is hosted in the EU (West region) via Supabase. However, third-party services including Google Gemini may process data in the United States or other regions. By using the Service, you acknowledge that your data may be transferred to and processed in countries outside your country of residence, which may have different data protection standards.

12 Browser Permissions

The Bookbeam extension requests the following Chrome permissions, each used for a specific purpose:

  • Active tab and scripting — to read the text content of the page you are currently viewing when you press Send. Content is only read when you explicitly trigger a send.
  • Storage — to save your settings, delivery configuration, and authentication session locally in the browser.
  • Identity — to support Google OAuth sign-in and to generate redirect URLs for Dropbox and Google Drive OAuth flows.
  • Tabs — to read the title and URL of the active tab for display in the extension popup and for metadata in the generated EPUB.
  • Alarms — to keep the extension's background service worker alive during long EPUB generation and delivery operations.

The extension does not monitor background tabs, does not track your browsing history, and does not collect any data unless you actively initiate a send.

13 Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Effective date" at the top of this document and, where feasible, notify you via the extension or our website. Your continued use of the Service after changes take effect constitutes acceptance of the updated policy.

14 Contact

If you have questions or concerns about this Privacy Policy or your data, please contact us:

Michał Włosik EFC

ul. Północna 16/5, 54-105 Wrocław, Poland

Email: hello@bookbeam.tools

Web: bookbeam.tools