Privacy

Last updated 28 October 2026.

InHousePDF assembles PDF packs in the browser for teams in any industry. It is not a professional adviser. This notice says what can leave the device. The short version is on No data collected.

Documents

PDF bytes, page text and file names are handled in your browser. They are not sent to us. There is no account. The tool can keep a copy in this browser so the same files are still there after you open Pack Builder, reload, or return to a tab. That copy stays on the device. It is cleared when you choose Clear all work, after a period of inactivity, or when the tab closes if you picked that option. Passwords are not stored. Open the proof panel on the pack builder, or the browser Network tab, while you add files and download. Requests during assembly should be zero. You can also switch off the network after the page has loaded and build the pack again.

What we do not take from the tool

Analytics and error reports

Optional, same-origin, and off until an operator sets an endpoint. Events are page views and coarse tool events. They cannot include file names or page text. A report is sent only after you read it and press Send. There is no session replay.

Advertising

Not used in this release. Slots exist in guide layouts, hidden, at a fixed height, so a later creative cannot shift the page. They are outside the file controls. See the cookie policy before any ad network is enabled.

Templates

A saved template is a JSON file of section titles and settings. It does not contain PDF bytes or source file names. It downloads to your device. Loading a template does not send it anywhere.

Contact

A public contact address is not set on this build yet. Security reports go to the address on the security page.