Last updated: June 29, 2026

Changelog

This changelog records visible maintenance work for JUST FREE PDF. It focuses on changes that affect user trust, privacy language, content quality, sitemap coverage, public pages, and the PDF editing workflow.

June 29, 2026 — review hardening and trust cleanup

• Updated homepage and footer language so privacy wording consistently explains server-assisted processing where needed.
• Removed older absolute browser-only wording from public product and policy pages.
• Expanded thin core pages for signing PDFs, filling PDF forms, browser PDF editor security, PDF form behavior, and data-flow boundaries.
• Corrected the homepage guide link for the “Why edited PDF text shifts” card so it points to the matching guide page.
• Renamed public build labels from internal review terminology to production-oriented version labels.
• Kept public pages free of Google Analytics and Google Tag scripts during the AdSense review period.
• Maintained the warning that users should never click ads to support the site.

June 29, 2026 — guide library expansion

• Expanded the guide hub so users can start with editable-text detection, data flow, status, text editing, forms, signatures, metadata, redaction, security, and export review.
• Added deeper guidance for AcroForm, flat form, scanned form, and XFA behavior.
• Expanded security content covering browser extensions, shared devices, downloads, cache, cloud sync, and sensitive document categories.
• Added more natural internal links between tool pages and guide pages without linking every page to every other page.

June 29, 2026 — policy and technical alignment

• Rewrote privacy and cookie disclosures to match the current upload, analysis, operation, export, and download workflow.
• Improved the status page with workflow status, known limits, advertising review status, and post-deployment checks.
• Improved sample guidance so users can test with non-sensitive files before uploading important documents.
• Adjusted static resource cache behavior and webmanifest content-type handling in the Go server.
• Kept sitemap entries aligned with canonical, indexable pages.

June 29, 2026 — production bundle cleanup

• Updated the public JavaScript build identifier to 20260629-production-006.
• Removed public console build output and user-facing internal startup error wording from the editor bundle.
• Updated homepage CSS and JavaScript references to versioned filenames so the page no longer depends on stale fixed-path asset caches.
• Expanded the Cookie Policy with current cookie status, advertising-cookie boundaries, analytics status, browser site data controls, and policy-update rules.
• Expanded the Contact page with product support, privacy, copyright, abuse, advertising, and responsible security reporting categories.
• Kept the site free of Google Analytics, Google Tag Manager, and premature ad units during the review-preparation state.

June 29, 2026 — static asset cache cleanup

• Added versioned editor asset filenames: /app.20260629-production-006.js and /app.20260629-production-006.css.
• Kept /app.js and /app.css as current compatibility copies while changing their Go server cache headers to no-cache.
• Updated deployment checks to require purging CDN/proxy caches for old fixed asset paths before resubmitting AdSense.
• Added test coverage for homepage asset references and cache headers.

Maintenance principles

Tool pages should explain how to perform a task in JUST FREE PDF. Guide pages should explain document structure, workflow risk, review steps, and decision rules. Policy pages should match the actual product, not aspirational claims. If analytics, advertising scripts, OCR providers, retention settings, or third-party processing change, public disclosures should be updated before the change is treated as production behavior.

Open maintenance work

• Add more original interface screenshots and annotated examples as the editor changes.
• Document deployment-specific stale-file cleanup behavior after it is verified in production.
• Continue pruning or redirecting legacy thin pages so every public page has a clear purpose.
• Recheck Search Console after deployment and wait for recrawling before submitting another AdSense review.

Deployment verification note

Each source package should be checked after deployment by loading the live homepage, a tool page, the guide hub, the privacy policy, sitemap.xml, manifest.webmanifest, and at least one new guide URL. The site should not be resubmitted for review while production still displays older privacy wording, old build strings, missing guide URLs, or outdated sitemap entries.

Next content priorities

The next useful additions are original interface screenshots, downloadable non-sensitive sample PDFs, a clearer temporary-file cleanup statement after deployment verification, and more examples showing how exported PDFs differ across viewers. These additions should be based on observed product behavior rather than generic filler text.