We keep the proof. We don't keep what we don't need.
A compliance tool should be the smallest possible target. Here's exactly what Claddr stores, what it never sees, and how the record is protected.
What Claddr storesThe result of each buyer check, linked to the orderSigned statements and the exact version signedOrder and payment references from StripeMonitoring findings for your storefrontAdmin actions in your workspace
What Claddr never touchesCard numbers. They're entered into Stripe's secure fields.Merchant ID documents. Stripe-hosted onboarding handles them.Your funds. Payouts go from Stripe to your bank.Your Stripe secret keys. You connect by signing in.
How the platform is protected.
IntegrityHash-chained ledgerEach entry includes the previous entry's hash, so any edit breaks the chain visibly.
AccessRole-based staff accessOwner, admin and reviewer roles. Reviewers see holds, not settings.
AccountabilityAdmin audit logEvery settings change and approval is logged with who did it and when.
TransportEncrypted in transitAll traffic between your store, Claddr and Stripe runs over TLS.
ResilienceBackup and restoreWorkspace configuration can be backed up and restored from the dashboard.
IsolationTest modePair and configure in test mode. No real money moves until every check passes.
Report a vulnerabilityIf you've found a security issue, email us before disclosing it publicly. We'll acknowledge your report and keep you updated until it's resolved.[email protected]
Need it for a review?We can share our data handling summary and answer security questionnaires for you or your processor.Request documentation