Data use and scope
Customer, order, merchant, account, device, request, audit, and storefront records are used to operate storefront, checkout, support, security, fraud-prevention, audit, and compliance workflows.
Public policy / privacy
How ReTale uses, protects, retains, and handles personal information in platform workflows.
These launch-baseline pages describe the current product posture. Final legal, privacy, and compliance approval is required before production merchant traffic.
Customer, order, merchant, account, device, request, audit, and storefront records are used to operate storefront, checkout, support, security, fraud-prevention, audit, and compliance workflows.
Customer PII is targeted for a seven-year default retention class, with anonymization where allowed. Orders, payment references, disputes, tax records, and legal holds can require longer preservation. Logs default to 90 days and generated code to two years, subject to approved policy.
Privacy and data-subject requests are manually reviewed through the Contact page. ReTale separates removable personal data from records needed for tax, chargeback, dispute, accounting, security, or legal obligations; this page does not claim automated fulfillment.
Clerk, Cloudflare, Twilio, payment gateways, hosting, and database services may support platform operation when configured. Access is scoped by tenant, role, service need, and audit requirements.