Product capability
Protect the publishing boundary
Validation, expiry, reporting and controlled delivery give teams practical control over how documents are shared.
Publish a PDFA protected publishing baseline.
EmbedFox validates PDF MIME type, signature and size before publication. It uses public expiry, an owner removal path and a minimal report form.
- Every upload is checked before publication: the declared MIME type, the
%PDF-signature and the file size. - An anonymous upload creates a public reader URL that expires seven days later, and the owner can remove it before that.
- Every public reader carries a short report form, and reported documents enter a closed moderation queue.
- Missing, disabled and unauthorized documents return the same response, so a reader URL cannot be used to test whether a document exists.
- No cookies are set for metrics, so a reader does not need a consent banner on your page.
Designed for publishing. Anonymous uploads are public for seven days. Validation and expiry do not make this upload flow private document hosting.
What it does not do yet.
Naming the edge is more useful than implying there is none. These are on the product roadmap, not in the product.
- Limiting a document to allowed embed domains, or protecting it with a password.
- A preview limited to the first pages, with an email gate or a publisher handoff for the rest.
For publishing over time
More control for each document.
Domain lock, controlled downloads, preview gates, paywalls and custom domains make the public boundary explicit.
Delivery status for this capability lives on the product roadmap; delivered changes appear in the changelog.
Keep reading.
The pages that answer the next question about this capability.