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 promise is about limiting access and time, not making an impossible guarantee.
Trust is built into how the product behaves, not just what it claims.
Every role sees only what its job requires. A vendor receives exactly one authorized job, a customer sees only their own documents. There is no shared library and no guest mode.
A document exists for the life of the print job and no longer. Cleanup runs automatically in the background, whether or not anyone opens the app.
We keep the details required to run a print job and nothing more. History records what happened, never the document itself.
Completed and expired jobs are purged automatically by the platform. If a customer forgets to confirm or collect, the order completes on its own so the document is still purged. No one has to remember to delete anything.
Print jobs move through a fixed, traceable sequence of states. The journey can be reviewed after the fact without retaining the file.
Every job follows the same path. Nothing lingers at the end.
If a customer forgets to confirm a print or collect a pickup order, the job completes automatically after the waiting period, so cleanup still runs. If a job expires before completion, the document is purged automatically. The same cleanup runs whether or not anyone opens the app again.
Read the security model and the privacy approach, without jargon.
