Modelo de seguridad

Que se queda en local. Que llega a PDFity. Que cruza a terceros.

Esta pagina existe para volver inspeccionable nuestra promesa de confianza. La idea base de pdfity es simple: el procesamiento PDF estándar debe quedarse en el navegador por defecto y cualquier salida de ese límite tiene que ser explicita.

What stays in-browser by default

Standard PDF processing for routine workflows such as merge, split, reorder, rotate, watermark, page numbering, and signing is designed to happen locally by default.

What pdfity still receives

Authentication data, usage counts, billing state, and operational telemetry are used to run the product, enforce limits, and support accounts.

What only happens by explicit choice

Drive imports, Dropbox saves, and Polar checkout are optional boundary crossings triggered by the user, not silent defaults.

Checklist

Lo que esto significa, y lo que no

It means standard processing is not upload-first by default.

It does not mean every external dependency disappears.

It means the third-party boundaries are explicit instead of hidden.

It does not replace a team's own regulatory, legal, or security review.

Modelo de seguridad de PDFity | pdfity