Who is responsible for your information
This notice is intended to explain how [legal entity name], trading as PILOMED, handles personal information through [website domain], customer support and related services. Add the registered address, company identifiers and the person or team responsible for privacy before launch.
Privacy contact: [privacy email] · Grievance contact: [name, role, email and postal address] · Response period: [approved period].
Information the service may collect
Describe only the data the live service actually collects. At launch, this may include information a customer provides, transactional records and limited technical information created while the service operates.
- Identity and contact details used for accounts, orders, consultation requests, support and newsletters.
- Delivery, order, payment-status, refund and customer-service records. PILOMED should not receive full card credentials from the payment provider.
- Wellness-request or report metadata submitted deliberately by a customer. Define the approved handling of any report file before enabling binary uploads.
- Device, browser, referral, consent and interaction data only where the final analytics and cookie configuration collects it.
Why information is used
Insert PILOMED’s approved legal basis or consent position for each purpose and jurisdiction. Do not treat this list as legal approval.
- To create and secure an account, process an order, arrange delivery and provide requested support.
- To review and respond to a consultation or lab-report request within the published service scope.
- To prevent misuse, keep operational records, meet applicable obligations and resolve disputes.
- To send marketing only where permitted and provide a simple way to withdraw or unsubscribe.
- To improve the service using appropriately configured measurement tools and consent controls.
Sharing and service providers
Name or accurately describe each approved category of recipient, such as hosting, authentication, payment, delivery, communications, support, analytics and professional advisers. State where information is processed and what safeguards apply.
PILOMED should not describe personal information as sold or never shared until its actual advertising, analytics and vendor arrangements have been reviewed.
Sensitive report information
The current lab-report endpoint records metadata only and does not accept the selected file. Before real uploads are enabled, PILOMED must implement authenticated private storage, encryption, access logging, role-based review, time-limited file access, deletion handling and an approved retention schedule.
Do not publish compliance or end-to-end encryption claims unless the complete system and operating process have been independently verified against the named standard.
Retention, security and incidents
Complete a retention table for accounts, orders, tax records, support, consultations, report requests, marketing consent, analytics and security logs. Explain when information is deleted, anonymised or retained due to an obligation.
Describe verified administrative, technical and physical safeguards without promising absolute security. Add the approved incident-notification and escalation process.
Choices and individual requests
List the rights available in PILOMED’s operating jurisdictions and explain how identity will be verified. This may include requests to access, correct, delete, restrict or withdraw consent, subject to applicable exceptions.
Request channel: [privacy request method] · Verification process: [process] · Expected response: [approved period] · Appeal or complaint route: [details].
Cookies, children and changes
Document necessary storage and each optional analytics or marketing technology. Provide consent and preference controls where required. State the approved minimum customer age and how information concerning a child is handled.
Explain how material changes will be communicated and keep prior versions available where appropriate. Last updated: [date].
Approved by: [name and role] · Version: [version] · Approval date: [date] · Next review: [date]