Your shop's data, kept to itself
A print business runs on its costs, its customers and its files. Here is exactly how those are kept separate from everyone else's, and what we have not done yet.
Two layers, not one
Your shop's rows are separated from every other shop's by the database itself, not just by application code that could forget a WHERE clause.
- Every table of workspace data carries a row-level security policy, and it is enforced even against the account that owns the table
- Your requests run as a database role that cannot escalate its own privileges and cannot bypass those policies, separate from the one that owns the schema
- A build gate refuses to ship a new table of workspace data that has no policy on it
- Tests that deliberately try to read another workspace's rows run on every build, as the same restricted role your requests use
Your keys are not our keys
Anything you connect is encrypted per shop, and the things that never need to leave your building do not.
- Channel tokens use per-shop envelope encryption, bound to your shop and that provider, never one app-wide key
- Printer access codes stay on your own network; the Link agent talks to your machines over your LAN
- Payments run through Stripe Connect, so card details never touch Printuple and payouts go to you
- We store a Stripe account identifier, not your banking details
Who can see your shop
Sign-in is yours to harden, and staff access is a separate, audited plane rather than a back door in the app.
- Two-factor sign-in and passkeys, on by your choice
- Roles decide what each team member can do, enforced on the server rather than hidden in the interface
- Session cookies are host-scoped, and a storefront host can never reach the app or the admin console
- Printuple staff have a separate login, and when one of us opens your console to work a ticket a banner sits across the top of it for the whole session, which expires by itself after an hour
Including the ones we would rather not give
Do you have a SOC 2 report?
No. Not SOC 2, not ISO 27001, not HIPAA, not PCI. We are a small team in a closed beta and we would rather tell you that than imply otherwise. What we do have is on this page, and it is all checkable in the product.
Can Printuple staff see my data?
Only to investigate a ticket, and never invisibly. A banner sits across the top of your console for the whole session and it expires by itself after an hour, so you always know when it happened.
Do I have to open ports on my router?
No. Link makes outbound HTTPS connections only. Nothing listens for incoming traffic, there is no port forwarding, and we hold no tunnel open into your shop.
What happens to my data if I leave?
Orders export to CSV from the orders list, and model files download from the library, so you can take your work with you. Deleting a whole workspace is not self-serve: you ask us and we do it, which is deliberate, because an irreversible button next to everything you have built is a bad idea.
Where do I report a security problem?
Email hello@printuple.com. We will confirm we have it, and we will not argue with you about whether it counts.
Something here not clear enough?
Ask before you sign up rather than after. A real person answers these.