File handling · browser-based PDF processing
Local inspection, with a clear boundary.
The Checker is designed to process your selected PDF in browser memory using a Web Worker. This describes PDF processing within the application, not the data handling of the hosting or authentication services.
Privacy — File and result handling
Your PDF is inspected locally in your browser. Changing the selected PDF or pressing Reset clears the current on-page PDF findings and previous event comparisons. Changing the event, year, session, or archived profile clears the previous event-specific comparison while preserving the separate generic PDF findings.
Cancel stops an active inspection and clears its associated in-page result. Leaving the page ends the active inspection. A TXT report you have already downloaded remains on your device unless you delete it. Clearing in-page results does not guarantee forensic erasure from device memory.
TXT report downloads are user initiated. Hosting and authentication logging are separate from the Checker’s PDF handling described here.
PosterBeacon is hosted on Cloudflare Workers. Source links open official pages only when you choose to follow them; your selected PDF is not attached. Do not email your PDF, unpublished research or sensitive personal information.
Email correspondence is separate from the browser-only PDF Checker. Messages sent to contact@posterbeacon.com are forwarded to an administrative mailbox. Your email address and message contents are handled through email forwarding and mailbox services. Replies may come from a separate administrative email address rather than an @posterbeacon.com address. Do not email your PDF, unpublished research or sensitive personal information.
Use is limited by generic inspection of up to 20 pages (archived comparisons remain single-page), a 10 MiB input cap and a 15-second watchdog. Failed or unavailable inspection produces UNKNOWN. No browser behavior is represented as institutional approval to use sensitive research.
Return to the local checker →Before any Google advertising is activated
No advertising cookies or ads are active here. Before activation, the privacy notice must be updated to describe the actual Google and partner advertising cookies, how prior visits can inform ads, and the available personalized-advertising choices. It must identify any additional participating ad vendors, link to their information and explain their available choices.
The final operator must review applicable consent requirements and site-specific disclosures before activation, and keep the notice aligned with any later vendor or configuration changes. This is a future update requirement, not a claim that a consent system exists or that legal review is complete. Google’s privacy-notice requirements ↗.
Optional local text report
The report contains bounded measurements, selected context, source references and corrective actions. It omits your filename, document text, font names, images and document metadata. It is generated in browser memory and saved only when you choose Download .txt report. The chosen report is a local file you control; reset clears the in-page report and measurements, not a file you have already saved. Changing event context clears the event comparison while preserving event-independent generic facts. Changing the PDF clears both.