Tenant boundary
Storefront and merchant operations run behind scoped APIs and explicit store boundaries.
Trust center / security
Security and operations posture
Customer-safe evidence of the controls ReTale uses to protect tenant data, payment boundaries, generated storefronts, and platform operations.
Trust signal placeholders
Use these sections in your launch package. Replace “placeholder” values with approved evidence artifacts before production merchant traffic.
Tokenized payments
Checkout and card handling stay in provider-managed flows with no raw card payloads in storefront code.
Boundary enforcement
Generated storefronts are constrained to approved commerce SDK paths for checkout, inventory, and order flows.
Payment boundary
Hosted and tokenized payment flows keep sensitive payment entry outside ReTale app state and generated storefront code. ReTale stores provider references, not raw card data.
Tenant isolation
Storefront slugs, merchant store IDs, role checks, scoped repositories, and negative cross-tenant tests protect each store boundary.
Release gates
Generated-code isolation, API drift, migrations, security baseline, build, and browser evidence gates run before deployment.
Generated-code safety
Generated storefronts can control presentation but must use fixed SDK/API paths for checkout, identity, tax, inventory, orders, loyalty, and memberships.
Data retention
Default retention classes distinguish removable personal information from order, tax, payment-reference, dispute, audit, and legal-hold records.
Incident contact
Security and privacy concerns route to the platform support/compliance owner for manual triage, acknowledgement, and escalation.
Trust-page statements are a product summary, not a certification or guarantee. Request current compliance evidence through the contact intake before relying on it for procurement.
What to request before production
Evidence pack checklist
- Independent vulnerability scan report for public surfaces and APIs.
- Last 30-day tenant-isolation regression test evidence across public, merchant, and operator surfaces.
- Release-gate logs for API drift, migration, generated-code checks, and security baseline.
- Data-retention and DSAR processing evidence from the policy owner.