Trust & Security

Security you can actually read.

PandazPOS was built behind the counter of a real Tampa smoke shop. So we treat your store's data the way we'd want ours treated: card numbers we never touch, sales we wall off store-by-store, and infrastructure we rent from the same companies the big platforms use.

This page lays out exactly how that works — in plain language, with no certifications we don't actually hold. If something here matters to your call, email us and a human answers.

Report something: [email protected] Privacy Policy Terms
Built on certified infrastructure
StripePCI DSS Level 1
CloudflareSOC 2 Type II
Supabase / PostgresSOC 2 Type II

These certifications belong to our infrastructure partners — not to PandazPOS. We are not independently SOC 2 or HIPAA certified. Those certifications belong to our infrastructure partners, not us.

How we handle your money

Card data never touches our servers. We're integrators of Stripe Terminal, not a payment processor.

01 Card data, off our hands
Payments run through Stripe Terminal — PCI DSS Level 1Active
Cards are read & encrypted by the terminal, not by usBy Stripe
We never see, store, or transmit raw card numbersEnforced
02 Smaller blast radius
Your store's PCI scope stays small — we can't lose what we never holdBy design
We keep a Stripe reference, not the cardActive
Refunds & reporting work off that referenceActive

How we wall off your data

One store can never see another store's data. Enforced by the database, not just the app.

01 Per-store isolation
Postgres Row-Level Security on every store's dataEnforced
Isolation verified by an automated test before changes shipTested
White-label per location — your brand, your environmentActive
02 Encryption
Encrypted at rest (Postgres / Supabase)Active
Encrypted in transit — TLS terminal ↔ app ↔ databaseEnforced
Automated database backupsActive

Built on certified infrastructure

We don't reinvent security — we build on companies audited for it. Each stamp below belongs to the vendor named on it, not to PandazPOS.

PCI DSS
Level 1held by Stripe
SOC 2
Type IICloudflare · Supabase
TLS 1.2+
everywherein transit
01 The stack under the counter
Cloudflare — edge network, WAF & DDoS protectionSOC 2
Supabase / Postgres — managed DB, encrypted at restSOC 2
Stripe — payment hardware & processingPCI L1
02 Reliability
Sub-100ms response at the edgeActive
Offline-ready — keep ringing through a WiFi drop, sync afterActive
Status & incident updates via security@On call

Age & product compliance

Built for regulated retail, by people who run regulated retail.

01 At the point of sale
ID scanning / age verification for age-gated productsActive
Age-gate prompts at checkout for restricted categoriesActive
Timestamped verification records for your filesRolling out
02 Privacy
Handling aligned with CCPA & GDPR principlesAligned
Export your data on requestActive
Delete your data on request (minus legal retention)Active
We don't sell your data — or your customers'Never

Subprocessors

The vendors we rely on, what they do, and what data they touch. We update this when it changes.

PandazPOS · subprocessor disclosure · 06.21.26
StripePayments & terminal hardware
Cardholder/payment data — handled entirely by Stripe; we never receive raw card data
US
Supabase / PostgresDatabase & auth
Store, inventory, sales & account data — encrypted at rest
US
CloudflareEdge, WAF, DDoS, DNS
Network traffic / requests in transit
Global edge
AppleiOS owner app distribution
App delivery + push notification tokens
US

"I keep your sales data walled off the same way I'd want mine. If you can't trust the register, you can't run the shop."

— Tee · owner, Smoke Mellow · builder of PandazPOS

Found something? Tell us.

Good-faith reports get a real human reply — we're a small team and we mean it.

[email protected]

Send details and steps to reproduce. We aim to acknowledge within 2 business days. Please don't access data that isn't yours or run disruptive tests against live stores.

Email security →