Legal
Privacy notice
A polished MVP summary of the data WPFlow currently handles to operate account access, request delivery, release evidence, billing, and support.
What data is handled
WPFlow only handles the data needed to operate the service safely.
- Account, membership, request, release, and billing records needed to run the service.
- Uploads and artefacts stored to support preview, evidence, and auditability.
- Operational logs and audit events that support supportability, release review, and troubleshooting.
Why it is handled
The data serves the governed delivery model rather than a broad ad-tech stack.
- To run onboarding, delivery, release review, and billing.
- To keep release evidence and approvals visible.
- To support service operations and issue investigation when required.
How access stays bounded
The public promise here is clarity, not over-claiming.
- Access to operational data is limited to the people and systems needed to run the service.
- Environment boundaries matter across staging and live workflows.
- Privacy questions can be sent to support@wpflow.io.