Cookies and browser storage
Device-local drafts, sign-in and third-party payment or security services.
1. Storage used by the application
The implementation uses browser-local storage for draft recovery, demonstration state, some promotion-kit edits and checkout recovery identifiers. This is different from the server's authoritative shop and payment records. Information saved in one browser may not appear on another device.
2. Sign-in, payments and protection
Authentication, payment and security providers may use cookies or similar technologies as part of their services. A production inventory must record the actual technologies, providers, purposes and duration after those integrations are connected. This policy does not claim that provider cookies are absent or that a complete consent system is already deployed.
3. Optional analytics and advertising
No advertising-pixel or analytics consent is inferred from using the builder. Before enabling optional tracking, document its purpose and recipients, decide the applicable consent requirements, provide the appropriate controls, and ensure those controls actually affect loading and data collection.
4. Your browser controls
Browser settings can restrict or clear local storage and cookies. Clearing them may remove unsaved local drafts and recovery information or sign you out. It does not necessarily delete server-side records. Use the applicable account or privacy-request process for server-held information.
5. Shared devices
Sign out on shared devices and avoid leaving confidential shop material in a shared browser. Retention depends on account, purchase, security, support and legal recordkeeping needs; contact CartArchitect to request access, correction or deletion of information that is not required to be retained.