Privacy Policy
Last updated: March 13, 2026
PDFity keeps public reading public: pricing, tool pages, and legal pages can be reviewed before you sign in.
The core product boundary is straightforward: standard PDF processing stays in your browser by default, and any move beyond that boundary should be an explicit choice.
Scope and product boundary
This policy covers the public website, the authenticated product, optional provider actions, and any live billing surface connected to PDFity.
The default promise is simple: standard document work stays in the browser unless the page clearly asks you to cross into another boundary.
Account, support, and plan data we receive
When you sign in, we receive the account details that your authentication provider shares with us so we can create and maintain your access.
We also receive the plan, entitlement, support, and billing-state information needed to keep Free and Pro behavior aligned with the public pricing surface.
Usage, analytics, and operational telemetry
PDFity uses analytics, performance telemetry, and operational logs to keep the product available, understand feature use, investigate problems, and enforce product limits.
These signals are part of the live service. They are separate from standard PDF file contents and should not be confused with document upload by default.
What stays out of our servers by default
Standard PDF file bytes are not sent to PDFity servers by default for normal local-first processing.
Local-only items such as signature drawings, watermark presets, and similar in-browser preferences are not treated as server-side account data under the current product model.
Optional provider and billing flows
Google Drive and Dropbox import or save actions begin only when you deliberately choose them. Those actions also involve the provider you selected and are subject to that provider's own rules and permissions.
When checkout is available, payment processing is handled through Paddle and its processors. PDFity should receive the billing state needed to operate the plan, not your full payment card details.
Retention, security, and contact
We retain account, plan, billing-state, and operational records for as long as they are reasonably needed to run the service, enforce terms, respond to abuse, resolve support issues, and meet legal obligations.
No internet product is risk-free. Our approach is to keep privacy and trust copy aligned with the real product boundary instead of making blanket claims that hide exceptions.
Questions
Need clarity on privacy boundaries?
Use support if you need a direct answer about account data, provider boundaries, or how local-first processing is scoped in the live product.
