Data Protection
PrepackFlow Atlas keeps merchant-facing documentation, buyer-facing runtime behavior, and reviewer evidence aligned so merchants can understand what data is processed, where it is stored, and why.
- Merchant data is processed to authenticate the app, store pack configuration, publish runtime projections, and diagnose operational failures.
- Public documentation, review assets, and production URLs must describe the same live behavior.
- Feedback and operator diagnostics are stored separately from merchant pack configuration.
Processing purposes
PrepackFlow Atlas processes merchant data to install the app, authenticate API access, store pack configuration, publish storefront runtime payloads, verify theme and function behavior, and support operational maintenance.
The app does not require protected customer data for the current public distribution scope.
- Installation and authentication
- Pack profile and assignment management
- Storefront runtime projection and operational verification
Security and storage boundaries
Secrets are stored in appsettings-backed configuration for the deployed environment, and runtime error samples are redacted before they are written to the operator catalog.
Feedback submissions and operator error summaries are treated as operator-owned datasets and are not merged into merchant shop data.
- Redacted operator diagnostics
- Separate feedback inbox and error catalog surfaces
- DB-first storage for merchant pack configuration
Merchant-facing documents
If a merchant or reviewer relies on PrepackFlow Atlas documentation for compliance review, the public Privacy, Terms, Data Protection, FAQ, Changelog, and Feedback pages on the live domain are the controlling public surface.
- Production support URLs stay public
- Reviewer screenshots must match live pages
Support question
Use the feedback page to ask for clarification about documentation, data handling, or reviewer evidence.