PE Boris Zabolotskikh ("we," "us," or "our") respects your privacy. This Privacy Policy explains what data we process when you use the https://webtopdf.space website, the Web to PDF browser extension, the online converter, license purchase features, support, and related services.
Web to PDF helps save web pages and selected parts of pages as PDF files. Therefore, some of the data the service works with is the content of pages that the user chooses to convert. We use this data only to provide product features, support, security, error diagnostics, product analytics, and to comply with legal obligations.
In brief
- The extension processes the content of the active tab when you start conversion, element selection mode, element removal mode, or chat/post export.
- Created PDF files and conversion history in the extension are stored locally in the user's browser, unless you use the Google Drive upload feature yourself.
- We do not sell users' personal data.
- We do not store bank card numbers. Payment data is processed by the payment provider Paddle.
- We do not request or collect passwords from websites you convert.
- Some technical and product events may be sent to analytics and diagnostics services such as Amplitude, Sentry, and Betterstack.
- The online converter on the website processes the URL, HTML code, or HTML file that you submit to create a PDF, and temporarily stores the result.
Products covered by this Policy
This Policy applies to:
- the https://webtopdf.space website;
- the Web to PDF extension for Chrome and compatible browsers;
- extension pages: settings, conversion history, PDF viewer, License & Billing, and support;
- the online converter on the website;
- checkout, the purchase success page, and related APIs;
- the feedback form and support requests.
If you go to a third-party website or use a third-party service, such as Google Drive, Paddle, Chrome Web Store, or social networks, the processing by that party is also governed by that third party's policies.
Chrome Web Store data categories
For the Privacy practices section in the Chrome Web Store, we disclose the following data categories because the extension may collect, use, store, process, or transmit this data as part of its features.
Personally identifiable information
We may process:
- the email you enter to recover a license, contact support, or make a purchase;
- the name and email from the feedback form on the website;
- the registered email associated with the license;
- the extension's internal user identifier;
- the license key and information about its status.
Financial and payment information
We process information needed for paid access:
- the selected plan;
- the country and currency for regional pricing;
- transaction and purchase identifiers;
- license, subscription, or lifetime access status;
- availability of the Customer Portal for payment management.
Bank card numbers and other sensitive payment details are processed by Paddle. We do not store card numbers in the extension or on the website.
Authentication information
We may process:
- the license key that confirms access to Pro features;
- the transaction ID after purchase in order to retrieve the license;
- the Google Drive OAuth token obtained through the Chrome Identity API if you use the PDF upload to Google Drive feature.
We do not collect passwords from websites that you open or convert.
Personal communications
We may process personal communications if you use the relevant features yourself:
- the text of messages you send through the feedback form;
- email correspondence with support;
- the content of ChatGPT, Gemini, or DeepSeek conversations if you start exporting such a conversation to PDF.
The extension uses the content of such conversations to create a PDF. We do not use personal communications content for advertising.
Location data
We may process:
- the IP address when you visit the website, use the API, contact support, make a purchase, or send requests to the Paywall API;
- the country or region determined from the IP address for Paywall availability and regional pricing;
- the IP address or generalized location information that may be processed by analytics services.
We do not collect GPS coordinates.
Web browsing and website visit history
The extension may process information about pages you convert:
- page URL;
- page title;
- page domain;
- conversion time;
- conversion mode and PDF settings.
In the extension history, this data is stored locally together with the PDF file. The page domain may be sent to product analytics, but not the full URL and not the PDF content.
User activity
We may process information about activity in the product:
- the fact that a PDF was exported;
- the selected conversion mode;
- conversion settings;
- created file size;
- browser language;
- extension version;
- device, OS, and browser information;
- app rating, if you provided one;
- technical events and errors.
This data helps us understand which features are used, diagnose failures, and improve the product.
Website content
This is a key category for Web to PDF. The extension may read and temporarily modify the DOM of the active page to prepare it for printing and create a PDF. Depending on the mode, this may include:
- page text;
- images;
- links;
- page structure and styles;
- the page element selected by the user;
- article content;
- post content;
- content of ChatGPT, Gemini, or DeepSeek conversations;
- the created PDF file.
Page content is used to generate the PDF. In the extension's normal mode, the PDF and its history are stored locally in the browser. If you use the Google Drive feature, the PDF is uploaded to your Google Drive and a public link is created for it.
Data processed by the extension
Converting pages to PDF
When you start conversion, the extension works with the active tab and uses browser capabilities to prepare the page and create a PDF. To do this, the extension may:
- check whether the current tab is supported;
- inject content scripts into supported pages;
- read the title and URL of the active tab;
- read the content of the page or the selected element;
- temporarily hide or modify page elements to prepare the PDF;
- use the Chrome Debugger API and Chrome's built-in print-to-PDF feature;
- save the result in local history.
Temporary page changes should be restored after conversion is complete.
Local PDF history
The extension stores the history of recent conversions in the browser's IndexedDB. A history record may include:
- the PDF file;
- page title;
- page URL;
- creation date and time;
- conversion mode;
- print settings;
- extension settings;
- extension version;
- file size;
- internal record identifier.
History is stored locally on your device. The extension limits the number of history records and deletes the oldest records when the limit is exceeded. You can delete individual records or clear the history in the extension interface.
Extension settings and profile
The extension may store in Chrome storage:
- interface language;
- conversion mode settings;
- information about showing tips and guides;
- installation date;
- initial extension version;
- number of available trial actions;
- app rating, if you provided one;
- license key, if it is activated;
- internal user identifier.
The selected interface theme may also be stored locally.
Google Drive
If you click "Share" and choose to upload a PDF to Google Drive, the extension:
- requests access through the Chrome Identity API;
- receives a Google OAuth token;
- creates or finds the
webtopdffolder in your Google Drive; - uploads the selected PDF file;
- makes the file available through a public "anyone with the link" link;
- shows the link to the uploaded file.
The PDF remains in your Google Drive until you delete it yourself. We do not receive your Google password.
Extension analytics
The extension may send a PDF export event to Amplitude. The event may include:
- internal user identifier;
- extension version;
- user agent;
- browser language;
- IP address as the remote IP processed by Amplitude;
- page domain or local file marker;
- conversion mode;
- conversion settings;
- print settings;
- PDF size;
- installation date;
- user preferences;
- app rating, if provided.
We do not send the PDF file itself, the full page URL, or the license key to Amplitude.
Error diagnostics
The extension may send errors to Sentry or Betterstack. Diagnostic events may include:
- internal user identifier;
- extension version;
- environment;
- stack trace and error message;
- technical execution context;
- browser and device information;
- extension command parameters;
- tab URL or title, if they ended up in the technical error context.
We try not to send license keys or PDF content to diagnostics.
Data processed by the website
Visiting the website
When you visit the website, the server and connected services may process:
- IP address;
- user agent;
- browser language;
- URL of the visited page;
- request date and time;
- referrer;
- technical cookies and local storage data;
- website interaction events.
The website uses Yandex Metrica, including Webvisor. This service helps analyze visits and improve website pages. Yandex Metrica may process cookies, IP address, device and browser information, visited pages, and user actions on the website.
Online converter on the website
If you use the online converter, you may submit one of the following sources:
- web page URL;
- HTML code;
- HTML file.
The website processes the submitted source and conversion settings, sends them to an internal PDF generation service, and temporarily stores the created PDF on the server. The PDF is available through a technical file identifier and is automatically deleted after a limited time. The current server logic deletes temporary PDF files older than approximately one hour.
Do not submit HTML code, files, or URLs to the online converter if you do not want them to be processed on the server.
Feedback form
If you send a message through the feedback form, we process:
- name;
- email;
- message subject;
- message text;
- IP address.
The message may be delivered to us through Telegram. We use this data to reply to the request, process the support request, investigate abuse, and ensure service security.
Email communications
We may use the email you provide to:
- send the license key, purchase, subscription, or lifetime access information;
- reply to a support request or a message from the feedback form;
- send important service notices related to security, payment, license, product changes, or this Policy;
- notify you about the status of a refund, dispute, subscription cancellation, or another payment request;
- send product news or marketing messages if such communication is allowed by law or you have consented to it.
You can opt out of marketing and product newsletters if they are sent. Service and transactional messages, such as emails about purchases, licenses, security, or support, may be sent regardless of your opt-out from marketing messages while this is necessary for the product to function, to perform the contract, or to comply with the law.
Purchase, license, and Paywall
For purchasing and managing a license, the website, extension, and backend may process:
- selected plan;
- country and currency;
- OS and browser;
- IP address;
- transaction ID;
- license key;
- buyer email;
- license status;
- subscription or lifetime access information;
- Paddle Customer Portal link.
Payment is handled through Paddle. Paddle may process payment details, tax information, address, email, and other information needed for payment, taxes, refunds, and legal compliance. We do not store bank card numbers.
Lifetime access
If you purchase Lifetime access, it means access to the paid features of Web to PDF for the lifetime of the product: while the product is available, maintained by us, and able to operate in a supported browser. Lifetime access does not mean a perpetual guarantee of the product's existence, its constant availability in the Chrome Web Store, or unchanged requirements from Chrome, browsers, and third-party platforms.
We are not responsible for the product being unavailable if the extension is removed, blocked, restricted, or becomes unavailable in the Chrome Web Store for reasons beyond our control, including Google decisions, changes to Chrome Web Store policies, browser technical limitations, or discontinuation of the product. In such cases, the payment for Lifetime access is not refundable, except where a refund is expressly required by applicable law.
Purchase success page
After purchase, Paddle may redirect you to the purchase success page with transaction_id in the URL. The website uses this identifier to retrieve the license key from the backend. If the extension is installed, the website may send the license key to the extension through an external runtime message so it can be stored locally in the extension profile.
The license key is shown to the user on the purchase page according to the current product logic and may also be sent to the buyer's email.
Third-party services
We may use the following third-party services and providers:
- Google Chrome and Chrome Web Store for extension distribution;
- Google Drive and Google Identity Services for uploading PDFs to Google Drive;
- Paddle for checkout, payments, subscriptions, taxes, refunds, and the Customer Portal;
- Amplitude for product analytics in the extension;
- Sentry or Betterstack for error diagnostics;
- Yandex Metrica for website analytics;
- Telegram for delivering messages from the feedback form;
- hosting providers and infrastructure services for the website, API, and backend.
Each third-party service processes data according to its own privacy policy and terms.
How we use data
We use data to:
- provide page-to-PDF conversion features;
- save and show conversion history;
- upload PDFs to Google Drive at your request;
- show correct settings and localization;
- manage trial access, the license, and Pro features;
- process purchases, refunds, and payment requests;
- reply to support requests;
- diagnose errors and prevent abuse;
- analyze feature usage and improve the product;
- comply with legal, accounting, and tax obligations.
When we share data
We share data only to the extent necessary for the product to work, support, analytics, diagnostics, payments, and legal compliance. Examples:
- A PDF is transferred to Google Drive if you start uploading it to Google Drive yourself.
- Extension usage events are transferred to Amplitude.
- Errors and technical context are transferred to Sentry or Betterstack.
- Payment and license data is transferred to Paddle and our Paywall backend.
- Messages from the feedback form may be transferred to Telegram.
- Website visit data may be transferred to Yandex Metrica.
- Data may be disclosed to public authorities if required by law.
We do not sell users' personal data.
Business transfer
If Web to PDF, the website, the extension, related services, or a substantial part of them are sold, transferred, merged with another project, reorganized, or transferred to a successor, user data may be transferred to the relevant party as part of such a transaction or preparation for it.
In that case, we will seek to transfer data only to the extent necessary to continue operating the product, support users, perform obligations, and comply with the law. The successor must process data in accordance with this Policy or provide users with a new privacy policy if required by applicable law.
Retention periods
The retention period depends on the type of data:
- local PDF history is stored in the user's browser until deleted by the user, the extension is removed, or old records are automatically deleted when the limit is exceeded;
- extension settings and the license key are stored in Chrome storage until deleted or changed by the user;
- PDFs created by the website's online converter are temporarily stored on the server and deleted automatically; the current retention period for temporary PDFs is approximately one hour;
- support messages are stored for as long as necessary to process the request and protect legitimate interests;
- payment, license, tax, and accounting data may be stored for as long as required to perform the contract and comply with the law;
- analytics and diagnostic data are stored according to the settings and policies of the relevant services.
How you can manage data
You can:
- delete PDF records from the extension history;
- clear the conversion history in the extension;
- change extension settings;
- remove the extension from the browser;
- delete uploaded PDF files from your Google Drive;
- revoke the extension's access to Google Drive in your Google account or browser settings;
- contact us to request access to, correction of, or deletion of data stored by us;
- contact Paddle regarding payment data if the data is processed by Paddle as the payment provider.
For data requests, email us at: support@webtopdf.space
Regional user rights
Depending on the country or region where you live, you may have additional rights regarding personal data. This may apply to users from the European Economic Area, the United Kingdom, California and other U.S. states, as well as from other countries and regions where applicable data protection laws provide similar rights.
To the extent provided by applicable law, you may have the right to:
- know what personal data we process and for what purposes;
- access your personal data;
- correct inaccurate or incomplete data;
- request deletion of personal data;
- restrict processing or object to it;
- receive a copy of the data in a portable format;
- withdraw consent if processing is based on consent;
- opt out of the sale, sharing, or use of personal data for targeted advertising, if this right applies to you;
- not be discriminated against for exercising privacy rights.
To exercise these rights, email us at: support@webtopdf.space
Security
We apply reasonable technical and organizational measures to protect data. Data transmission between the browser, website, backend, and third-party services is performed over secure connections where applicable.
At the same time, no method of transmission or storage is absolutely secure. Do not use Web to PDF to process data if you are not ready for the page or file you choose to be processed as part of the described features.
International data transfers
Our services and providers may be located in different countries. By using the website or extension, you understand that data may be processed outside your country, including in countries with different data protection rules.
Children's privacy
Our services are not intended for children under 13. We do not knowingly collect personal data from children under 13. If you believe that a child has provided us with personal data, contact us and we will take reasonable steps to delete such data.
Policy changes
We may update this Policy if the product, third-party services, Chrome Web Store requirements, laws, or our data processing practices change. The new version is published on this page with an updated date.
Contact us
If you have questions about privacy or data processing, email us at: support@webtopdf.space