THE PLANNER PRINT PREP GUIDE
Privacy policy
Effective 3 November 2026. This covers the browser tool, optional Plus access and the service providers below.
1. PDF processing
Files are not uploaded to a server. PDF parsing, previewing and output generation happen in your browser and its workers. The app does not send PDF bytes, images, extracted text, file names, paths or content hashes over the network. It does not execute document actions, attachments or scripts.
The site still downloads its own HTML, scripts, fonts, PDF resources and the self-authored example when selected. “Local processing” does not mean first-time use is offline.
2. Cookies and local storage
The PDF workspace and Plus access code set no cookies. Our hosting, security and external checkout providers may use cookies under their own policies; the workspace does not require advertising cookies. PDFs are never stored in localStorage, sessionStorage, IndexedDB or the Cache API. Print settings and named profiles stay in page memory by default. If you explicitly choose Remember profiles, only profile names and print settings are stored in localStorage until you turn that option off, choose Clear all saved profiles, or clear browser storage. No source PDF name, preview or content is automatically included. Files exist in page memory until cleared or the page is left. Refresh does not restore them. Normal browser caching of site assets and files you download is controlled by your browser. Clearing the tool is not secure erasure of operating-system memory.
3. Advertising and your choices
No Google AdSense or other advertising platform is enabled in this version. We do not currently load third-party advertising scripts or use your visit history for ad targeting. If Google advertising is introduced later, the policy must explain that Google and its partners may use previous visits to this and other sites to personalise ads. You can manage Google personalised advertising at Google Ad Settings.
4. Analytics and retention
The tool does not send usage events to Google Analytics or a session-recording service, and keeps no application analytics history. The public site uses GitHub Pages and Cloudflare for delivery and security; optional Plus access runs on Cloudflare Workers. Cloudflare processes request metadata such as IP addresses and operational security/performance information under its Privacy Policy. We do not set a separate retention period for provider-controlled infrastructure records. This public website is hosted on GitHub Pages. GitHub logs and stores visitor IP addresses for security purposes and processes request information under its own privacy policy. We do not maintain a visitor-history database or control the hosting provider’s retention period; GitHub determines retention under its policy, rather than a fixed period promised by this application. See GitHub Pages data collection and the GitHub Privacy Statement. PDF files remain in your browser and are not included in these asset requests.
5. Settings, feedback and external services
Exported settings JSON contains only versioned print settings. It contains no PDF, file name, path, text or content hash. You choose where to save it. A feedback summary is generated locally and sent only if you separately email it. Your email provider and the recipient mailbox then process that message; it is not an automatic analytics submission.
Ko-fi, Google Ad Settings and linked reference sites are external services with their own policies. They are not embedded in the editing workflow.
6. Optional Plus access
Opening the Plus panel checks whether paid access is available. When enabled, Plus contacts the configured access service. Buying Plus creates a temporary checkout identifier and random browser proof in sessionStorage; entries older than 24 hours are discarded when the Plus panel opens. They bind the return to the browser that started checkout; a redirect alone never unlocks access. If Keep Plus signed in is selected, an opaque access token is saved in localStorage. It is verified online, expires after 30 days without use and is removed locally when you sign out, turn off remembering or clear storage. Uncheck it on shared devices. No license key or device fingerprint is stored in the browser. Saved print profiles are separate and never contain PDF data.
Billing records include order/event identifiers and license hashes. For email recovery, the application stores a keyed hash of the normalized purchase email and an encrypted license, rather than a plaintext email. Browser sessions and recovery tokens are stored as hashes. Recovery links work once and expire in 15 minutes; encrypted pending delivery records expire within the same period or are removed after sending. Sessions expire after 30 days without use. Refunds revoke access and remove related recovery credentials. Minimal billing records remain as needed for purchased access and disputes; contact support about deletion. Creem handles checkout, tax and receipt information under its Privacy Notice. Card details are entered on Creem checkout, not in the PDF workspace. Resend delivers requested sign-in links and processes the recipient address and email content. Its published standard retention is 30 days for email and log data on Free, Pro and Scale plans; backups are retained for 7 days. Provider policies and any applicable account configuration govern their records. We use these emails for access restoration, not marketing. Files and file names are never included. Local demo links simulate email and do not send mail or take payment. No PDF content is included in payment or recovery requests.
Contact
Privacy questions: [email protected].