Printing inherently requires a document to reach the printing environment. Doxzo does not pretend otherwise. It minimizes that exposure with temporary access, automatic deletion, and strict authorization.
Clear boundaries are part of trust. Here is exactly what Doxzo does and does not claim.
Documents are temporary by default, vendors see only authorized jobs, and files are automatically deleted after completion or expiry.
To print, the document must reach the printing environment. Doxzo's promise is about limiting access and time, not making an impossible guarantee.
Every design decision maps to one of these five principles.
Vendors resolve to a specific record and can only access jobs where their vendor ID matches. Customers can only access their own jobs.
Documents live only as long as a job requires. A cleanup worker removes objects on completion or TTL expiry, independent of browser activity.
PostgreSQL stores metadata only, never document bytes. History remains available without retaining the underlying file.
Final-state and expired jobs are purged server-side. Deletion does not depend on a customer or vendor remembering to clean up.
Print job events record the lifecycle. Server-side status transitions mean the frontend can never set an arbitrary state.
Every job follows the same server-enforced path. Nothing lingers at the end.
At the final state, the backend deletes the document object and keeps only metadata for history. If a job expires before completion, the object is purged automatically.