Privacy Policy

Introduction

This section explains how the platform handles introduction in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Scope of this policy

This section explains how the platform handles scope of this policy in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Definition of the platform

This section explains how the platform handles definition of the platform in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Types of users

This section explains how the platform handles types of users in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Account creation data

This section explains how the platform handles account creation data in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Profile information

This section explains how the platform handles profile information in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Clinics, doctors, and laboratories

This section explains how the platform handles clinics, doctors, and laboratories in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Appointment data

This section explains how the platform handles appointment data in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Laboratory services and results

This section explains how the platform handles laboratory services and results in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Payment and transaction data

This section explains how the platform handles payment and transaction data in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Contact and support messages

This section explains how the platform handles contact and support messages in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Technical and device data

This section explains how the platform handles technical and device data in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Cookies and sessions

This section explains how the platform handles cookies and sessions in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Why data is used

This section explains how the platform handles why data is used in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

General legal basis

This section explains how the platform handles general legal basis in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Sharing with service providers

This section explains how the platform handles sharing with service providers in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Provider access to needed data

This section explains how the platform handles provider access to needed data in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Retention of information

This section explains how the platform handles retention of information in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Information security

This section explains how the platform handles information security in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

User rights

This section explains how the platform handles user rights in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Correcting and updating data

This section explains how the platform handles correcting and updating data in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Account and data deletion

This section explains how the platform handles account and data deletion in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Children’s data

This section explains how the platform handles children’s data in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

International transfer

This section explains how the platform handles international transfer in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Third-party services and links

This section explains how the platform handles third-party services and links in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Notifications and messages

This section explains how the platform handles notifications and messages in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

Changes to this policy

This section explains how the platform handles changes to this policy in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.

How to contact us

This section explains how the platform handles how to contact us in the context of patient access, clinic activity, laboratory requests, appointments, notifications, records, reviews, reports, public contact messages, and account management. Information should be used only for operating the service, supporting requested care activity, maintaining security, and improving understandable coordination between the parties involved.

Access to information should follow the user role and the operational need. A clinic, doctor, laboratory, administrator, or support channel may need different details to complete a request, answer an inquiry, review activity, or maintain the account. The platform should avoid presenting privacy promises that cannot be verified, and the final public policy should be reviewed legally before launch.