Cookie Policy
This Policy explains how Webpage to PDF uses cookies and similar browser storage for conversion, accounts, security, preferences, payments, referrals, and analytics.
Last Updated: September 26, 2026
How We Use Cookies
The technologies involved depend on the features and consent choices available in your browser.
1What cookies and browser storage are
Cookies are small values stored by your browser and sent with matching website requests. We also use browser storage such as localStorage and sessionStorage. Together, these technologies can keep you signed in, protect requests, remember preferences, and support measurement.
Cookies set by Webpage to PDF are first-party cookies. Providers involved in checkout, human verification, authentication, analytics, or advertising may use their own cookies under their own policies.
2Strictly necessary cookies
Necessary cookies support account sessions, email verification, password recovery, two-factor setup, secure redirects, temporary messages, anonymous conversion allowances, request limits, fraud prevention, and human verification. The service cannot provide these functions reliably without them.
These cookies are active independently of optional analytics or marketing consent. Blocking them in your browser may prevent sign-in, conversion, checkout, account security, or support features from working.
3Cookies and storage we use
The service may use saas_session for sign-in; email_verification_session, password_reset_session, and two_factor_setup_session for short security flows; OAuth state and verifier cookies for supported social sign-in; X-Flash-Message for short redirect notices; and saas_locale for language selection.
cookie_consent stores your consent record, sidebar_state remembers the account sidebar, and saas-theme stores the selected color theme. saavo_affiliate_referral records the first valid Affiliate referral for an eligible signed-out visitor. Analytics may use session storage for a short signed visit cache and local storage to remember an opt-out.
4Anonymous identity and conversion protection
When anonymous identity is enabled, saavo_anonymous_id gives the browser a signed pseudonymous identifier. We use it to provide anonymous conversion time, count protected requests, apply concurrency and abuse limits, and decide when a human-verification step is required.
Clearing the cookie removes the current browser token, but the service may issue a new one on the next request. Clearing or replacing identifiers does not create additional entitlement to free use and may trigger security controls.
Current setting: saavo_anonymous_id lasts 365d and is renewed when less than 30d remains. The identifier strategy is random.
5Affiliate referral cookie
When an eligible signed-out visitor follows a valid Affiliate link, saavo_affiliate_referral stores the first active referral for the current browser session. A later link does not overwrite it. Invalid, inactive, missing, or malformed referral information does not create attribution.
Referral attribution is applied only when an eligible new account is created. Cookie preferences, a link click, or a displayed traffic count do not by themselves create or prove a commission.
6Analytics and marketing
First-party analytics may measure page views, sessions, referrers, devices, feature use, performance, and conversion events. Optional third-party analytics or advertising scripts run only when they are configured and the applicable consent category permits them.
Available preferences may include functionality, analytics, and marketing categories. The exact providers shown in the preference dialog reflect the active website configuration. Providers may set additional cookies under their own domains.
7Managing your choices
Use the cookie banner or preferences dialog, when shown, to accept or reject optional categories. You can also clear cookies, local storage, and session storage in your browser, block third-party cookies, or use provider-specific controls.
Clearing website cookies may sign you out of the website and reset website preferences. It does not clear the extension's separately stored settings, login tokens or temporary conversion files. To remove extension login information, sign out in the extension; uninstall it to remove its browser-managed local data. Downloaded PDFs are not deleted. Necessary website cookies cannot be disabled through our preference dialog.
8Browser signals, changes, and contact
Because there is no single standard interpretation of every “Do Not Track” signal, our main control is the cookie preference system. We will also honor browser or platform signals where applicable law requires it.
We may update this Policy when cookies, storage, conversion protection, analytics, advertising, or providers change. Questions can be sent to support@webpagetopdf.dev.