Trust & Legal PDPA Notice
Malaysia · Personal Data

Personal Data Protection Notice

How Relify handles personal data across clinic operations, patient records, AI-assisted workflows, security and support under Malaysia’s Personal Data Protection Act 2010 (Act 709).

ProviderCasemix Solutions Sdn Bhd.
Applies toRelify platform & related services
JurisdictionMalaysia
Last updated9 August 2026
This notice is available in Bahasa Malaysia and English.
On this page

This Notice applies to personal data processed in connection with Relify. It is written to distinguish the clinic’s responsibilities from Casemix’s responsibilities, because the same platform can contain both Customer-controlled patient records and data Casemix processes for its own service administration.

If you are a patient: your clinic generally controls your clinical record. You can still contact Casemix about Relify privacy or security, but requests to access or change the medical record itself will usually need to be handled through your clinic.

01

About this Notice

This Personal Data Protection Notice (the “Notice”) explains how Casemix Solutions Sdn Bhd. (“Casemix”, “Relify”, “we”, “us” or “our”) handles personal data in connection with the Relify clinic management platform and related websites, support, communications and services.

This Notice is intended to support the Notice and Choice requirements under Malaysia’s Personal Data Protection Act 2010 (Act 709), as amended from time to time (“PDPA”). It should be read together with our Privacy Policy, Terms of Service, Data Processing Addendum and AI & Responsible Use information.

This is a notice, not blanket consent.This Notice tells you what processing may occur and what choices are available. Where the PDPA or another applicable law requires consent or another condition before particular processing takes place, that requirement is handled separately from this Notice.
02

Our roles: data controller and data processor

Relify is used by clinics and healthcare organisations to manage their own operations and patient information. The legal role of Casemix depends on the particular data and purpose involved.

When the clinic controls the purpose

For patient records and other Customer Data that a clinic or healthcare organisation decides to collect and use through Relify, that Customer will generally act as the data controller. Casemix will generally act as a data processor and process that data to provide the Services on the Customer’s instructions, subject to the applicable agreement and law.

When Casemix controls the purpose

Casemix may act as a data controller for personal data it uses for its own legitimate business administration, such as account and subscription administration, security, fraud and abuse prevention, support, service communications, website operations, business contacts and compliance with legal obligations.

If you are a patient seeking access to or correction of a clinical record, your clinic is usually the best first point of contact because it determines the clinical purpose and content of that record. Relify can assist the clinic in responding where appropriate.

03

Personal data we may process

The categories of personal data processed depend on how Relify is configured and which features are used. They may include:

  • Clinic and user account data: name, work contact details, user ID, role, permissions, professional information, clinic or branch details, account status and authentication information;
  • Patient identity and contact data: name, date of birth, sex or gender information where recorded, identification or passport details where the clinic collects them, contact details, addresses, emergency contacts and related-person information;
  • Health and clinical data: medical history, allergies, chronic conditions, diagnoses, ICD codes, clinical notes, medications, prescriptions, observations, vitals, laboratory information, referrals, attachments, visit summaries and other information recorded as part of care;
  • Appointment and operational data: bookings, queue entries, check-in information, assigned clinicians, consultation timing, room or service information and patient-flow records;
  • Billing, payer and transaction data: invoices, payment status, payment method, claims, payer or panel information, discounts, packages, tax or e-invoice fields and related transaction records;
  • Communications: support requests, email or messaging records, notification preferences, feedback and correspondence;
  • Technical and security data: IP address, browser or device details, session information, timestamps, security events, access logs, audit records and diagnostic information; and
  • AI interaction data: prompts or instructions submitted to an AI Feature, the authorised context supplied to that feature, generated outputs, user confirmations, tool or action records and related audit information where applicable.

Relify may also process supplier, staff, professional or business-contact information where a Customer uses the platform for inventory, procurement, administration or related workflows.

04

Where personal data comes from

Personal data may be obtained directly from you, from the clinic or healthcare organisation using Relify, from its Authorised Users, from a patient or related person, or from systems and services that the Customer chooses to connect to Relify.

Depending on the workflow, information may also come from laboratories, payers, insurers, corporate panels, payment or e-invoice services, messaging providers, booking channels or other integrations authorised by the Customer. Technical and security information may be generated automatically when the Services are used.

05

Why we process personal data

Personal data may be processed for purposes reasonably connected with the use and operation of Relify, including to:

  • provide, operate, maintain and support the clinic management platform;
  • enable patient registration, appointments, queue management, EMR, pharmacy, laboratory, documents, billing, claims, inventory, reporting, multi-branch and other configured workflows;
  • authenticate users, enforce roles and permissions, preserve audit trails and protect the confidentiality, integrity and availability of the Services;
  • respond to support requests, troubleshoot problems, communicate service information and manage subscriptions or accounts;
  • process billing, payment, tax, e-invoice, payer or claims-related information where the relevant feature is used;
  • provide AI Features when an authorised user requests them, including generating summaries, coding suggestions, analyses, reports, explanations or authorised operational actions;
  • operate Customer-authorised integrations and communications;
  • detect, investigate and prevent fraud, misuse, security incidents or prohibited activity;
  • maintain service reliability, performance and quality, including debugging and operational analytics; and
  • comply with applicable law, lawful requests, professional obligations or contractual requirements.

Where Casemix acts as processor, the Customer determines the relevant purposes and legal basis for the underlying patient or Customer Data. Where Casemix acts as controller, we process personal data only for purposes that are notified, permitted by law or otherwise supported by an applicable legal basis or condition.

06

Sensitive personal data, health information and minors

Relify can process sensitive personal data, particularly information concerning a person’s physical or mental health and, where used, biometric information. Such data receives heightened care because of the potential impact of unauthorised access or misuse.

The clinic or healthcare organisation is responsible for ensuring that it has the consent, authority or other condition permitted by law that is required for its collection and use of sensitive patient data. Casemix processes that information to provide the Services in accordance with the Customer’s instructions and applicable law.

Relify may hold information about children or other persons who cannot independently provide the relevant authority where that information is entered for legitimate healthcare purposes. In those circumstances, the Customer is responsible for obtaining and documenting any authority, consent or involvement of a parent, guardian or other legally authorised person that is required.

07

AI Features and personal data

Relify includes AI-assisted features for clinical and operational workflows. These may include a business or operational assistant, visit-summary generation, ICD-10 or ICD-11 suggestions, clinical analysis, reporting, explanations and tools that can perform authorised administrative actions.

What an AI Feature may receive

When an Authorised User invokes an AI Feature, Relify may make available the prompt or instruction and the minimum relevant context needed to answer or carry out the request, subject to that user’s permissions and the feature’s scope. Depending on the request, the context may contain personal data or sensitive health information.

Human review and clinical responsibility

AI output is assistive and may be inaccurate, incomplete or inappropriate. Relify is designed so that AI is not the sole factor for a final clinical decision. Qualified healthcare professionals remain responsible for reviewing diagnoses, coding, medications, summaries, treatment or other patient-care decisions before relying on them.

Operational actions

Where the AI Assistant is permitted to perform an operational action, such as an authorised queue, inventory, invoice, report or other administrative action, Relify may associate the action with the initiating user, apply that user’s permissions, record action details for auditability and require confirmation for certain sensitive actions.

Automated decision-making and profiling

Not every use of AI is automated decision-making or profiling. If Relify introduces a feature that uses personal data to make or materially influence a decision about a data subject without meaningful human involvement, we will assess the feature under applicable PDPA requirements and guidance and provide additional notice or controls where required.

AI data is not a free-standing data purpose.Patient or clinic information is not made available to an AI Feature merely because it exists in Relify. The processing occurs when the relevant feature is used or where the Customer has configured an authorised AI workflow. Any separate use of identifiable Patient Data for a materially different purpose would require an appropriate legal basis, notice, instruction or consent as applicable.
08

Who personal data may be disclosed to

Personal data may be disclosed only where reasonably necessary for the relevant purpose, where instructed by the Customer, or where permitted or required by law. Classes of recipients may include:

  • Authorised Users, branches or entities within the Customer’s permitted Relify environment;
  • hosting, cloud infrastructure, storage, security, email, communications, support, analytics and AI service providers that support the operation of Relify;
  • laboratories, payers, insurers, corporate panels, payment providers, e-invoice services, messaging platforms or other systems connected at the Customer’s request;
  • professional advisers, auditors, insurers, banks or business service providers where reasonably necessary for Casemix’s administration and legal obligations;
  • government departments, regulators, courts, law-enforcement bodies or other authorities where disclosure is required or permitted by law; and
  • a successor or proposed successor in connection with a legitimate corporate transaction, subject to appropriate confidentiality and data-protection safeguards.

Casemix does not sell or rent Patient Data for unrelated advertising. Our current service providers and relevant processing roles may be described in the Subprocessors page.

09

Transfers outside Malaysia

Some service providers or connected services may process personal data outside Malaysia. Where a cross-border transfer occurs, Casemix will take steps intended to ensure that the transfer is permitted under Act 709 and applicable Commissioner guidance, taking into account the destination, purpose, recipient and available legal, contractual, organisational and technical safeguards.

A Customer may also choose integrations or communication channels that involve international processing. The Customer remains responsible for the legality of transfers it independently directs or configures, while Casemix remains responsible for the obligations that apply to Casemix’s own transfers.

10

Retention, return and deletion

Personal data is retained for no longer than is reasonably necessary for the purpose for which it is processed, subject to applicable legal, professional, tax, medical-record, dispute, security, backup and contractual requirements.

For patient and clinical records, the Customer generally determines the applicable retention period because it controls the healthcare purpose and must comply with its own professional and legal record-keeping obligations. Relify provides tools and contractual processes to support retention, export, return and deletion, but using the platform does not replace the Customer’s own retention responsibilities.

Following termination, Customer Data may remain for a limited period in active systems, recovery environments or backups before deletion according to the applicable agreement, backup lifecycle and legal obligations. Data subject requests for deletion or restriction are assessed in light of the applicable legal role and any requirement to retain the record.

11

Security and personal data breaches

Casemix maintains administrative, organisational and technical safeguards designed to protect personal data against loss, misuse, unauthorised or accidental access, disclosure, alteration or destruction. Measures may include role-based access, authentication controls, encryption where appropriate, audit logging, backups, monitoring, access reviews, environment controls and incident-response procedures.

No internet-connected service can guarantee absolute security. Customers and Authorised Users also have responsibilities, including protecting credentials, assigning appropriate permissions, securing devices and promptly reporting suspected compromise.

If a personal data breach occurs, Casemix will investigate and take containment and remediation steps appropriate to the circumstances. Where Act 709 or applicable Commissioner guidance requires notification, Casemix will notify the Personal Data Protection Commissioner and/or affected data subjects in the manner and within the timeframe required by law. Where Casemix is acting as processor, it will also support the relevant Customer with information reasonably needed for the Customer’s own obligations.

12

Your rights and choices

Subject to Act 709, applicable exceptions and the role in which Casemix is processing the data, a data subject may have rights to:

  • be informed whether and how personal data is processed;
  • request access to personal data;
  • request correction of personal data that is inaccurate, incomplete, misleading or not up to date;
  • withdraw consent by written notice where processing depends on that consent;
  • prevent processing in circumstances provided by law, including certain processing likely to cause damage or distress;
  • prevent processing for direct-marketing purposes; and
  • request data portability where the statutory requirements, technical feasibility and format compatibility requirements are met.

Other requests, including requests to delete, restrict or export information, will be assessed according to applicable law, the relevant controller/processor role, contractual obligations and any legal or professional requirement to preserve the record.

Patient requests

If your request concerns a medical record held by a clinic through Relify, please contact that clinic first. Where the clinic is the data controller, Casemix generally cannot independently alter or release the clinic’s patient record without the clinic’s authority, except where required by law.

13

Mandatory and voluntary information

Whether providing personal data is mandatory or voluntary depends on the feature and context.

  • Required for the Service: certain account, authentication, clinic, billing or technical information must be provided or generated so that Relify can create accounts, secure access, provide contracted features, process subscriptions or comply with legal obligations. If it is not provided, the relevant service may not be available.
  • Required for a Customer workflow: a clinic may require particular patient or clinical information in order to provide care, bill a service, submit a claim or complete another workflow. The clinic determines that requirement and the consequences of not providing the data.
  • Optional features: some profile fields, marketing communications, integrations or AI Features may be optional. If an optional feature is not used, the personal data required only for that feature does not need to be submitted to it.
14

Service communications, cookies and marketing

Casemix may send operational messages necessary to administer the Service, including security notices, account information, support responses, billing communications and material service changes. These are different from promotional marketing.

Where Casemix sends direct marketing to business contacts, recipients may opt out using the mechanism provided or by contacting us. Relify websites may use cookies or similar technologies for essential operation, preferences, security and analytics. Additional information may be provided in a separate cookie notice where applicable.

Customer communications to patients, including appointment reminders or messaging campaigns, are controlled by the Customer. The Customer is responsible for ensuring that it has the authority and required consent or opt-out mechanisms for those communications.

15

Data Protection Officer and privacy governance

Act 709 requires a data controller or data processor to appoint one or more Data Protection Officers when the applicable statutory or regulatory criteria are met. Casemix will maintain a DPO and complete any required registration where those criteria apply to its processing activities.

Regardless of whether a statutory DPO appointment is triggered at a particular time, privacy enquiries and data-protection requests for Casemix can be sent to the contact details below.

Privacy / Legallegal@relify.com.my
General Supportsupport@relify.com.my

Company: Casemix Solutions Sdn Bhd. For general enquiries, you may also use the Relify contact page.

16

Changes to this Notice and related documents

We may update this Notice when Relify’s data flows, features, subprocessors or legal obligations change. The “Last updated” date identifies the current version. Where a change materially affects how personal data is processed, we will provide additional notice where required by law and, where appropriate, through the Service or Customer communications.

For more detail, please review the Privacy Policy, Terms of Service, Data Processing Addendum, AI & Responsible Use information, Security information and Subprocessors list.

This Notice is intended to be available in both Bahasa Malaysia and English. If you need this Notice in an accessible format or require assistance understanding it, please contact us.

This Notice describes Relify’s intended data-handling framework and does not remove any rights or obligations that cannot lawfully be excluded. Where applicable law imposes a stricter requirement, that requirement applies.

Run your whole clinic on Relify.

One month free. No credit card required. Free migration help.