Security & privacy

Encryption

All traffic to and from ConfirmPO is encrypted in transit (HTTPS, via Let's Encrypt). Data is not currently encrypted at rest beyond whatever the underlying cloud storage provides by default.

Who can access your data

The buyer-facing dashboard requires signing in at zbackroom.com — with your own email (a one-time link), a Google account, or a password you set yourself after verifying your email — it is not publicly browsable, and there's no shared password. That single sign-in works across zbackroom.com and ConfirmPO. Passwords are salted and hashed (scrypt) and never stored in plain text. Password-based accounts require email verification (a 6-digit code) before the account becomes active — so an email address can't be claimed without proving you own it, even though the signup form asks for a password up front. A signed-in user only sees purchase orders they created or were sent to their own address. Supplier confirmation links are intentionally no-login by design (that's the point of the product), scoped to a single PO each, and can be revoked by the buyer at any time. Server infrastructure access is limited to the ConfirmPO operator; there is no separate staff or support team with access to your documents.

Backups & retention

The database is backed up daily and retained for 7 days. Purchase orders are kept until you ask us to delete them — there's no self-service delete button in the app yet, so email us and we'll remove it.

Confirmation links

• Each PO gets a unique link, expiring 30 days after it's last sent.
• Resending a PO extends the expiration automatically.
• Buyers can revoke a link immediately from the PO page, any time.
• All confirmation activity is timestamped in the PO's timeline.

AI training

Your documents are not used to train any AI model.

Hosting

ConfirmPO runs on AWS, in the US (us-west-2).