Last updated: June 29, 2026

Changelog

This changelog records meaningful product, content, privacy, and technical changes. It exists so users and reviewers can see that JUST FREE PDF is maintained as a real PDF utility and knowledge center, not only as a group of static policy pages.

June 29, 2026 — AdSense readiness and trust cleanup

• Removed Google Analytics and Google Tag scripts from public HTML pages during the review period.
• Rewrote privacy and cookie disclosures to match the actual upload, analysis, operation, export, and download workflow.
• Replaced an older absolute browser-only claim with clearer server-processing boundaries.
• Added a visible homepage note explaining that some workflows may use server processing.
• Changed About page positioning from an overly strong local-processing title to a privacy-conscious product description.
• Expanded the guide library with detailed articles about editable text detection, exported text shifts, AcroForm versus flat forms, portal submission checks, metadata review, unsafe redaction, workflow privacy tradeoffs, and common editing mistakes.
• Expanded sample-file and status pages so they explain real testing procedures and known limits rather than acting as placeholders.
• Adjusted static resource cache-control behavior and webmanifest content type handling in the Go server.
• Added redirects for legacy thin template pages so users and crawlers reach stronger canonical resources.

Content review notes

The guide library now separates tool instructions from educational pages. Tool pages should explain how to use the editor. Guide pages should explain document structure, risk, validation, and decision rules. This separation is intended to reduce repeated wording and give users more useful information before they upload or submit a file.

Privacy review notes

The current public language should describe JUST FREE PDF as privacy-conscious, not as a guarantee that every workflow is offline. Some operations may use server processing. Uploaded PDF contents should not be used for advertising targeting, analytics events, resale, or AI training. Policy pages should be updated again if analytics, advertising scripts, retention behavior, OCR providers, or third-party processing changes.

Technical review notes

The server code now distinguishes HTML pages, sitemap files, robots files, ads.txt, llms.txt, webmanifest files, versioned assets, and API/export routes for caching purposes. Production deployment still needs to be verified with real response headers after release. A correct source change is not enough if the deployed binary or static bundle is still old.

Open maintenance work

• Add more original browser screenshots and annotated examples as the product interface changes.
• Document automated stale-file cleanup after the deployment environment confirms retention settings.
• Continue rewriting or removing legacy template pages so every indexable page has a distinct purpose.
• Keep the sitemap synchronized with canonical, indexable pages only.
• Recheck Search Console after deployment and wait for recrawling before submitting another AdSense review.