Privacy review for buyers.

Review the data, controls, vendors, and approval topics HexaFit should finalize before customer launch.

Privacy flow

Privacy review starts with the data path.

Connect data categories, member controls, subprocessors, and launch approval.

HexaFit data and integration boundary illustration

Data map

Show what data moves through the platform.

Memberships, bookings, payments, CRM, exports, and integrations should have visible ownership.

HexaFit member portal illustration for account access, updates, and self service

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.

HexaFit launch blueprint showing vendor choices and implementation readiness

Vendors

List subprocessors after vendor and integration choices are final.

The page stays honest while showing the exact areas that need approval before launch.

SMS Privacy

SMS Privacy

HexaFit may send SMS messages for demo scheduling, customer support, account, appointment, and service follow-up.

SMS opt-in data, phone numbers, and consent records are used only to provide HexaFit text messaging. HexaFit does not sell or share SMS opt-in data with third parties for promotional or marketing purposes.

Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help.

Customer Proof Privacy

Customer Proof Privacy

HexaFit may collect customer testimonials, review submissions, logos, approval records, and optional outcome details when a customer chooses to submit a story.

Customer proof submissions are reviewed before publication. HexaFit does not publish a testimonial, logo, quote, case study, or customer result unless the customer has provided permission for that use.

Private contact details collected for review and approval are used to manage the testimonial workflow and are not displayed publicly.

Privacy topics

Items to finalize before launch.

A short list of review topics, not unsupported compliance claims.

Document data categories before launch.Confirm retention, deletion, and export workflows during implementation.List subprocessors after vendor choices are final.Link privacy claims to evidence when available.