Data map
Show what data moves through the platform.
Memberships, bookings, payments, CRM, exports, and integrations should have visible ownership.
HexaFit Privacy Policy.
See how HexaFit handles platform data, SMS opt-ins, customer proof submissions, and buyer review topics.
Privacy flow
Privacy starts with the data path.
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.
SMS Privacy
SMS Privacy
HexaFit is a product of HexaSoft Innovations LLC. HexaFit may send SMS messages for demo scheduling, customer support, account, appointment, and service follow-up.
SMS opt-in information, phone numbers, and consent records are used only to provide HexaFit text messaging and are not sold or shared with third parties for promotional or marketing purposes.
Message frequency varies. Standard Message and Data Rates may apply. Reply STOP to opt out. Reply HELP for help.
Consent is not a condition of purchase.
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
What buyers should expect HexaFit to document.
Plain-language privacy topics that help operators and procurement understand the rollout.
Business, member, booking, payment, access, CRM, and support data are handled for platform operations.Access, export, correction, deletion, and retention workflows are reviewed during implementation.Subprocessors and integrations are documented as vendor choices are confirmed.Public privacy claims stay tied to approved operational evidence.