Loading content
We take privacy seriously. This demonstration stores preferences and non-clinical booking request metadata in your browser only.
This is a demonstration draft, not a finalized legal policy or legal advice. Do not publish without review.
This document is a design-stage example for the [BRAND NAME] consumer marketplace, an experience in the BIIS ecosystem. It is not a published legal policy. Before launch, replace the placeholder with the correct legal entity, contact details and country-specific notices.
The local demonstration stores saved provider IDs, demo-session display name, a non-authenticated session flag and non-clinical appointment-request metadata in your browser. The checkout contact fields and passwords are not saved to local storage or transmitted to any service. The help form validates locally but sends nothing.
Before launch, implement notices covering search and location queries, account credentials, communications, fraud prevention, support messages, consent records, international transfers, retention and individual rights, tailored to the markets actually served.
The marketplace must not store diagnostic information, medical conditions, treatment notes, medical images, results or protected clinical records. Clinic eligibility screening, professional consent, patient identity checks and clinical bookings must occur within authorised Clinic systems under their own access policies.
This demonstrator never charges a card, sends a booking to a provider or confirms an actual appointment. Production payment data should be handled by a compliant payment partner, and booking status must come from the connected Salon or Clinic system.
This project does not install analytics trackers. It may request public map tiles and external photography when those views load. A production deployment must review third-party services, consent requirements and data-transfer implications.
You can clear demonstration data by clearing this site’s local storage in your browser. Real retention, export, correction, portability and deletion rights require a published legal process and verified user identity.
Add a real privacy contact, version history, governing entities and appropriate data-protection information before production deployment.