Private by design

Your documents.
Your space.

Privacy starts with where the work happens. Here’s what local processing means in TruePage, and where that promise begins and ends.

TruePage is available from Microsoft Store for Windows 11. This page describes the app’s implemented privacy design and its boundaries; it is not a claim of independent certification.

Document processing stays on your PC

TruePage is a native Windows PDF workspace. Organizing, compressing, converting, and protecting documents runs in the app and its local worker processes. There is no cloud-processing fallback, and ordinary document operations do not require an account or internet connection.

Optional feedback

When you select Send feedback, your message and optional reply email are sent through Cloudflare to the developer’s inbox. No files, logs, conversion history, app metadata, or device identifiers are attached. An internet connection is needed to send feedback. Unsent drafts stay in memory until the app closes.

Submitted feedback is stored in our support inbox. For deletion requests, contact support@truepage.app. Cloudflare, AWS SES and Fastmail process feedback and email delivery. Cloudflare uses the source IP address for abuse protection.

support@truepage.app

Your source documents stay yours

Source documents are opened read-only. The workspace holds your page arrangement and reversible edits; exporting produces new outputs. When an output filename already exists, Keep both is the default. Replacing an existing output requires an explicit choice, and source documents remain excluded output targets.

Local does not mean permanently erased

The workspace is not a saved project. A controlled language-change restart can briefly retain a protected, one-use workspace and undo-history handoff. Passwords are not restored through that handoff. Export operations can use temporary output data, which the application manages and cleans up as part of the operation.

Closing the app or deleting a file is not a promise of forensic erasure. Windows paging, hibernation, backups, filesystem behavior, and other software are outside the app’s control.

The boundary matters

TruePage’s local-processing promise covers TruePage and its worker processes. It cannot control Windows, Microsoft Store delivery, antivirus tools, endpoint monitoring, malware, or other applications. A file placed in a cloud-synchronized folder may be uploaded by the synchronization service even though TruePage processes it locally.

PDF password protection is also distinct from encrypting your computer or securing backups. Choose storage and sharing practices appropriate to the documents you handle.

This website is separate from the app

This website serves product information and articles. It does not accept document uploads, create accounts, or include a newsletter form. The site code adds no analytics scripts, tracking cookies, remote fonts, or third-party embeds.

Visiting a website still sends ordinary web requests, including an IP address and request information, to its hosting provider. Hosting logs and any features enabled by the site operator are separate from the desktop app’s local-processing behavior. Website delivery should not be understood as an offline service.

A promise we can explain

We describe the behavior of the product rather than claiming absolute security. Verification and improvements continue after release. As the app evolves, this page and the journal will reflect meaningful changes to that behavior.

Read the practical guide to local PDF processing →