How Poppelo handles your order data.
Poppelo runs on shared infrastructure with your data separated at the database, the storage layer and the model call. This page says what is enforced in code, what is verified in production, and what is not yet offered.
Separation
Every API request runs under Postgres row-level security bound to your tenant. Every stored document sits under a tenant prefix the storage layer enforces, including before a download link is signed. Each model call carries only your own documents and your reference data: one document, plus up to two of the same customer’s approved orders if you turn on partner examples. Background workers enforce tenant scope in code, with a tested inventory of every module that touches tenant data. Processing runs on shared infrastructure; this is not a container per customer.
What the AI does and does not do
The model reads documents and returns structured fields. It does not decide what happens next. Routing, validation and approval are fixed rules you can read line by line. Your documents are not used to train models. Corrections stay inside your account.
Approval controls
Auto-approval is off until an admin turns it on. Supplier invoices are always reviewed by a person. Orders that fail validation wait for review, and orders below your reject threshold are never written. Merged multi-PO documents cannot be approved by anyone.
Audit and records
The audit log is append-only, enforced by database permissions, and exported nightly to object storage. Every order keeps the document it came from, what was read, what a person changed, and the ID of the record it became. A full-tenant JSON export is available from Settings, a retention purge runs on your configured window, and an account is suspended rather than deleted at offboarding.
Access
Magic link, Google and Microsoft sign-in with a verified email, SAML and OIDC single sign-on with enforced-SSO domains, a session idle timeout, lockout after repeated rejected sign-ins, and API keys scoped to what an integration needs.
Roles and SSO
Four roles: an owner, who holds billing and the organisation; admins, who manage the team, connections and API keys; operators, who review and approve orders; and viewers, who can see orders and reports but change nothing. Enterprise accounts can require single sign-on for every user on a verified email domain through SAML or OIDC, so a person leaving your identity provider loses access to Poppelo at the same moment. Live acceptance against a customer identity provider is still outstanding; see the last section.
Secrets
Connector and mailbox credentials are encrypted at rest with a rotatable key ring and verified against the live provider before they are stored, so a bad credential fails at setup rather than on your first order.
Subprocessors and residency
Poppelo is hosted in AWS us-east-1 (United States). Documents are read by Anthropic in the United States. Error monitoring is Sentry, region to be confirmed. The subprocessor list names every third party that touches customer data, and the data handling page says how long data is kept and how it leaves.
Not yet offered
No SOC 2 or ISO attestation. No contractual uptime, recovery point or recovery time. Object Lock on the audit export bucket is monitored but not yet confirmed in production. Enterprise SSO has not been accepted against a live customer identity provider. These are beta-programme items. Ask us for the current status.
Questions about this workflow
Does every tenant get a dedicated processing container?
No. Poppelo uses shared processing infrastructure with tenant-scoped data access at the database, a tenant-scoped object storage prefix, and model calls that carry only that tenant’s own documents: one document, plus up to two of the same customer’s approved orders when the tenant turns on partner examples.
Is the audit export immutable in production?
The export runs nightly and checks the bucket’s Object Lock setting each run, but the production bucket configuration is not yet confirmed. We say so rather than claim it.
Do you hold a security certification?
No. Poppelo does not claim SOC 2, ISO 27001 or any other attestation today. Ask for the security packet for the current control evidence.
Ready to test the workflow?
Use your own orders during the trial, then review pricing and trial terms before you decide.