Overview
Convert: Web to PDF (“the Extension”) is a browser extension that converts webpages to PDF format. We are committed to protecting your privacy. This policy explains exactly what data the Extension collects, how it is used, where it is stored, who it is shared with, and the rights you have over it.
1. Data Collection
The Extension collects data in three narrowly-scoped scenarios: two voluntary feedback flows you initiate, and one automatic anonymous counter (Section 1.3). Outside of these, no data is collected, ever.
1.1 In-app feedback (opt-in)
After several successful PDF conversions, the Extension may show an in-app rating prompt. If — and only if — you actively submit the form, the following fields are collected:
- Star rating (a single number 1–5)
- Message (free-text feedback you type)
- Feedback type (optional category you select: Comments, Questions, Bug Report, or Feature Request)
- Email address (optional, only if you type one so we can reply)
Dismissing or ignoring the prompt collects nothing.
1.2 Uninstall feedback (opt-in)
When you remove the Extension, Chrome opens a short survey page on our website in a new tab. If — and only if — you choose to fill it out and submit, the answers you type are collected. Closing the tab without submitting collects nothing.
1.3 Anonymous usage analytics (automatic)
After each successful PDF conversion, the Extension sends a small ping to our own server at web-to-pdf-analytics.actuallyusefulextensions.workers.dev. The ping carries the following data:
- An anonymous install token — a random string generated the first time you open the Extension and stored locally in your browser. It is not a Google ID, not a Chrome profile ID, not linked to your name, your email, your IP, or any other account. Two devices belonging to the same person produce two unrelated tokens. The token cannot be reversed to identify you.
- Feature-usage signals— which Extension feature was used (e.g. “article mode”, “landscape”), which surface triggered the conversion (popup, right-click menu, keyboard shortcut), and the general category of site converted (e.g. “article”, “chat”). These are short labels, not the full URL or any page content.
- Hostname of public sites— when you convert a page on a public website (not localhost or a private network), the domain name (e.g. “en.wikipedia.org”) is sent so we can understand which types of sites the Extension is used on. The full URL path, query string, and page content are never sent.
- Extension version — so we know which build is active.
The ping does not include:
- The full URL or path of the page you converted
- The content of the page
- Your IP address (Cloudflare strips it before it reaches our log)
- Any browser, device, or fingerprint information
On the server we count: total PDFs created per day, how many unique install tokens were active per day, which features are popular, and how many install tokens were active on more than one day in a given week. We use these aggregates to understand whether the Extension is healthy and growing. We never look at individual tokens. We retain the per-day rows for 18 months for trend analysis, then delete them.
You can clear your anonymous install token at any time by clearing the Extension's data in Chrome's extension settings. A new token will be generated the next time you use the Extension.
1.4 What is NEVER collected
Under no circumstances does the Extension collect any of the following:
- Webpage content from pages you convert
- Full URLs, browsing history, or tab activity (only the hostname of public sites is collected, as described in Section 1.3)
- Cross-site tracking cookies or third-party tracking identifiers
- Per-user analytics, behavioral profiling, or session-level telemetry beyond the anonymous aggregate counter in Section 1.3
- IP addresses or device fingerprints
- Personally identifiable information beyond what you voluntarily type into the feedback forms above
- Health, financial, authentication, or location data
2. Data Handling and Use
Data the Extension collects (only the voluntary fields described in Section 1) is used solely for the following purposes:
- Improving the Extension. Reviewing aggregate feedback to prioritize bug fixes and feature work.
- Replying to you. If you provided an email address in the feedback form, we may use it to reply to your specific message about a bug or question.
Your data is never used for any of the following:
- Advertising, retargeting, or marketing
- Sale, rental, or licensing to third parties
- Profiling, automated decision-making, or scoring
- Training of machine-learning models
- Any purpose unrelated to the Extension itself
3. Data Storage and Retention
3.1 Local storage (on your device)
The Extension stores a small amount of data locally in your browser using Chrome's chrome.storage.local API. This data never leaves your device:
- User preferences — page size, margins, orientation, scale, default subfolder, and toggle settings. Retained indefinitely until you change them or uninstall.
- Download counter and rating state — a counter that determines when the rating prompt is shown. Retained until you rate the Extension or uninstall.
- Local feedback log— a local copy of any feedback you submitted (so you can view and export it from the Settings page). Retained until you click the “Clear” button in Settings or uninstall.
You can delete all locally-stored data at any time by removing the Extension from Chrome, or by clicking the “Clear” controls in the Settings page.
3.2 Server-side storage (only for submitted feedback and anonymous analytics)
When you submit feedback (Section 1.1) or uninstall feedback (Section 1.2), your submission is stored in a private database that only the developer can access. Anonymous usage analytics (Section 1.3) are also stored server-side.
- What is stored: only the fields listed in Sections 1.1, 1.2, and 1.3.
- Where it is stored:a private Cloudflare D1 database hosted on Cloudflare's infrastructure, accessible only by the developer.
- Retention: feedback is retained indefinitely unless you request deletion (see Section 6). Anonymous analytics rows are retained for 18 months.
- Security:all transmission uses HTTPS (TLS). The database requires authenticated access by the developer through Cloudflare's dashboard.
4. Data Sharing
The Extension does not sell, rent, lease, license, or otherwise distribute any user data to third parties for any purpose.
The only third-party infrastructure the Extension interacts with is Cloudflare Workers, which hosts our analytics and feedback endpoints. When you use the Extension, your browser makes HTTPS requests to our Cloudflare Worker carrying only the data described in Section 1. Cloudflare processes the request as the infrastructure provider; their handling of network-level data is governed by Cloudflare's Privacy Policy.
We will only disclose user data to other third parties when required by valid legal process (subpoena, court order) and only to the extent legally compelled.
5. Permissions Explained
The Extension requests certain Chrome permissions to function. Each is documented below with its specific purpose; none enable data collection beyond what is described in Section 1.
| Permission | Purpose |
|---|---|
activeTab | Access the current tab's content when you initiate a conversion. Only activates on user action, never in the background. |
scripting | Inject the content script that enables element removal, article extraction, and page preparation for PDF conversion. |
debugger | Use Chrome's DevTools Protocol to generate high-fidelity PDFs with proper text, fonts, and layout. |
downloads | Save the generated PDF file to your device's downloads folder. |
storage | Save your preferences (page size, margins, orientation) locally in the browser so they persist between sessions. |
contextMenus | Add right-click menu options for quick PDF conversion without opening the popup. |
6. Your Rights and Data Deletion
You have the following rights at all times:
- Right to know. This policy lists every category of data we collect. If you have questions about a specific item, email us (Section 9).
- Right to deletion of local data.Uninstalling the Extension or clicking “Clear” in its Settings page deletes all locally-stored data immediately.
- Right to deletion of server-stored feedback. If you previously submitted feedback and want it removed, email us at [email protected] with the date or text of your submission, or the email address you used. We will delete the matching row within 30 days and confirm in writing.
- Right to access. The locally-stored feedback log is viewable and exportable directly from the Settings page. For server-stored feedback, email us and we will send you a copy of any rows linked to your email address.
- Right to opt out. Never submitting the in-app feedback form or the uninstall feedback form means no data is ever collected from you in the first place.
7. Data Security
All transmission to our servers is encrypted in transit using HTTPS (TLS). Server-side storage is on Cloudflare's infrastructure, accessible only by the developer through authenticated access. Locally-stored data uses Chrome's built-in storage isolation, which scopes it to the Extension and the browser profile.
We will notify affected users by email within 7 days if we become aware of any unauthorized access to feedback data, where the affected user supplied an email address.
8. Children's Privacy
The Extension is not directed at children under 13 and we do not knowingly collect personal data from children. Because the only data we ever receive is what an individual voluntarily types into the feedback forms, no collection occurs unless an individual actively submits a form. If you believe a child has submitted feedback and you would like it deleted, contact us (Section 9).
9. Contact
Questions about this privacy policy, requests for data access or deletion, or any other concerns should be sent to:
Email: [email protected]
We respond to data-related requests within 30 days.
10. Changes to This Policy
If we update this privacy policy, the revised version will be posted at this URL with an updated effective date at the top of the page. We will never change the Extension to collect new categories of data without first updating this policy. Material changes that affect how existing user data is handled will be announced in the Extension's Chrome Web Store listing description.