Data map
Show what data moves through the operating layer.
Memberships, bookings, payments, CRM, exports, and integrations should have visible ownership.
Privacy review for evaluation.
This buyer review page identifies the privacy topics HexaFit should finalize before customer launch.
Privacy statusReview material for buyer evaluation.
Approved policy language should replace this page before production customer use.
Privacy flow
Privacy review is easier when buyers can see the data path.
These visuals connect data categories, member controls, subprocessors, and launch approval.
Member control
Give buyers a review path for access, export, and deletion.
Privacy work becomes clearer when member-facing controls are part of the implementation plan.
Vendors
List subprocessors after vendor and integration choices are final.
The page stays honest while showing the exact areas that need approval before launch.
Privacy topics
Items to finalize before launch.
The list is intentionally limited to review topics, not unsupported compliance claims.
Data categories should be documented before launch.Retention, deletion, and export workflows should be confirmed during implementation.Subprocessors and integrations should be listed after vendor choices are final.Security and privacy claims should link to evidence when available.