Public policies
Visible
About, FAQ, privacy, terms, use-case, and contact pages are linked directly from the site shell.
Trust center
PaperKit is designed to look and behave like a complete, maintained publisher property: clear documentation, visible policies, reachable support, and straightforward explanations of how document jobs are handled.
Public policies
About, FAQ, privacy, terms, use-case, and contact pages are linked directly from the site shell.
Processing model
Files move through expiring job folders instead of sitting forever in a public archive.
Support route
Visitors can see how to get help instead of running into an anonymous utility wall.
Useful tool sites need more than an upload button. PaperKit publishes explainer pages, FAQs, legal pages, and contact details so visitors can understand who operates the site and what to expect from it.
Those pages are also linked from the header, footer, homepage, and sitemap so they are easy to find for both people and crawlers.
PaperKit keeps result pages out of search indexes and removes expired job data on a short schedule. That helps the public site stay useful without turning the service into an accidental document archive.
The same approach keeps the main catalog focused on evergreen, user-facing pages while temporary outputs stay private to the job token.
Trust also comes from explaining limits honestly. PaperKit makes it clear that availability can change, damaged documents may fail, and source quality affects output quality.
When people need help, the site gives them a dedicated contact route and describes what details to include when reporting a problem.
Open privacy policy
Read the short-form explanation of what job data is stored and why.
Read terms
Review the core rules around uploads, availability, and temporary output storage.
Get support
Use the public support route when you need help with a document job.