Legal
Privacy Policy
Version 1.7 draft · 18 October 2026
WisdomHub (“we”, “us”, “our”)
Operated by TRAINERS HUB SDN. BHD. (Company No. 202601033142 (1695237-T))
Effective Date: [Date]
Last Updated: 12 September 2026 (usage records, visitor cookie, legal bases, deletion method, 2024 amendment commencement)
1. Introduction
1.1 This Privacy Policy explains how we collect, use, disclose, store, and protect your personal data when you use WisdomHub (the “Platform” or “Services”).
1.2 We comply with the Personal Data Protection Act 2010, as amended (including amendments commenced under the Personal Data Protection (Amendment) Act 2024) (together, the “PDPA”) and its subsidiary regulations. We process personal data in accordance with the seven PDPA Principles: General, Notice and Choice, Disclosure, Security, Retention, Data Integrity, and Access.
1.3 Where the Platform is required to register under section 14 of the PDPA as a Class of Data User (Services Class or such other class as may be prescribed), our registration number is [CDU-XXXXXXX] and we will display it on the website footer.
1.4 Where we rely on your consent, we ask for it in a form we can record: a checkbox that starts unticked, or a choice in the cookie banner. We keep the record of what you agreed to, the wording you saw, and when. Simply using the Platform is not treated as consent. Where we process your personal data on a basis other than consent, Clause 5 says which basis.
2. Who We Are and Data Protection Officer
We are the data controller for the personal data described in this Policy.
- Legal name: TRAINERS HUB SDN. BHD.
- Company No.: 202601033142 (1695237-T)
- Class of Data User registration: [Number, if applicable]
- Registered Address: [Address], Malaysia
- Email for data queries: privacy@wisdomhub.com.my
Data Protection Officer (“DPO”):
- Name: [DPO Name]
- Position: [DPO Title]
- Email: privacy@wisdomhub.com.my
- Telephone: [+60 X XXXX XXXX]
The DPO is responsible for monitoring our PDPA compliance, responding to data subject requests, liaising with the Personal Data Protection Commissioner, and overseeing data breach response. The DPO is registered with the Commissioner.
3. Personal Data We Collect
3.1 From all Users
- Full name, email address, mobile number. We do not use passwords: you sign in with a one-time code sent to your email address, and we record when each code was issued and used.
- Login activity, IP address, browser/device identifiers.
- Communications with us and with other Users via the Platform.
3.2 From Trainers (individuals)
- Accreditation documents: your HRD Corp accreditation certificate, your HRD Corp TTT or exemption certificate, and any other professional certificate you choose to upload (PDF). We read the certificate number from the document to check it against HRD Corp’s public register. Uploads are stored in Malaysia-hosted, encrypted private storage, are accessible only to Platform staff performing verification (access is logged), and are never displayed on your public profile.
- NRIC or passport number: we do not ask for a separate identity document. Your certificate carries your NRIC or passport number, and that is the only place we hold it. We do not copy it into our active systems, and it is never displayed. The certificate file is retained under Clause 10. We hold the number because verifying your accreditation is part of the contract you make with us (PDPA section 6(2)(a)) and because, as an online marketplace operator, we must keep a record of each supplier’s identity card or passport number for three years (section 6(2)(c); Regulation 8 of the Consumer Protection (Electronic Trade Transaction) Regulations 2024). Access to the file is limited to verification staff and is logged.
- Profile content you choose to add: profile photo, professional summary, areas of expertise, programmes, articles, testimonials, company logos, and video links.
- Your plan, credit balance and history, and the receipts we issue to you.
- Training history and ratings received (from Full Launch).
- Bank account details, tax identification number (“TIN”), and SST registration number (if applicable). Collected at Full Launch, when a payout, receipt, or e-Invoice first requires them, and used only for split payment through our payment gateway, receipts, and e-Invoicing.
3.3 From Training Providers (Sdn Bhd / PLT)
- Company name, registration number, SSM forms, business address.
- Authorised representative name, position, work email address, and mobile number.
- Directors’ / partners’ information for KYC purposes.
- HRD Corp TP registration number and current accreditation status.
- Bank account, SST registration, tax details.
3.4 From Clients (Corporate)
- Company name, registration number, business address.
- HR / HOD contact: name, work email, mobile, position.
- HRD Corp employer code (for verification only — we do not process levy claims).
- Training briefs and engagement details, which may include limited information about employees (e.g., attendance lists, role descriptions). The Client is the data controller of any such employee data and the Platform acts as a data processor for the limited purpose of facilitating the Booking. The terms of that processing are set out in the Data Processing Addendum auto-executed at Client onboarding.
3.5 Sensitive Personal Data
Where we collect health, religious belief, political opinion, or other sensitive personal data (e.g., a User requests training accommodation), we will obtain explicit consent in accordance with section 40 of the PDPA. Since 1 April 2025 sensitive personal data includes biometric data. We collect none.
3.6 Usage Records and the Visitor Cookie
Usage records. While you are signed in we keep a record of what you do on the Platform: the pages you open, the searches you run, the profiles, briefs and programmes you view, the actions you take (for example saving a trainer, sending a message, publishing a brief), and the time of each. Each record carries your account ID, your session, your IP address and your browser or device identifiers. We keep these records in a form that identifies you for twelve (12) months. After that we reduce them to counts and totals from which nobody can be identified, and delete the identifying copy (Clause 10).
We use usage records for three purposes, and Clause 5 gives the basis for each:
(a) to run the service you have signed up for: showing you what you have saved, viewed and sent, keeping your place, and answering your support requests;
(b) to keep the Platform secure and detect misuse; and
(c) to understand how the Platform is used so we can improve it.
Visitor cookie. If you accept analytics cookies in the cookie banner before you have an account, we set a first-party cookie with a random identifier. It lets us keep the pages you looked at before registering and, if you later register, join that browsing history to your account. If you decline, no visitor cookie is set and nothing you did before registering is linked to you. You can withdraw the choice at any time at the cookie banner; withdrawal stops further linking and we delete the browsing history held under that identifier. The cookie is described in the Cookies Policy.
4. Sources of Personal Data
We collect data:
(a) directly from you when you register, complete a profile, submit a brief, message another User, or contact us;
(b) automatically when you use the Platform (cookies, log files, analytics tools);
(c) from third parties such as HRD Corp (for accreditation verification, with your consent), SSM (publicly available registry information), payment gateways, sanctions/PEP screening services, and your nominated referees.
5. Purposes of Processing
We use personal data for the purposes set out in the table below. The basis on which we rely is also identified. The PDPA allows processing with your consent (section 6(1)(a)) or, without consent, where the processing is necessary for one of the grounds in section 6(2). The two grounds we rely on are section 6(2)(a) (necessary for the performance of a contract to which you are a party) and section 6(2)(c) (necessary for compliance with a legal obligation). The PDPA has no “legitimate interests” ground and we do not claim one.
| Purpose | Legal Basis (PDPA) |
|---|---|
| Creating and administering your account | Contract, s.6(2)(a) |
| Verifying accreditation and identity (KYC) | Contract, s.6(2)(a); legal obligation, s.6(2)(c) where a law requires the check; consent, s.6(1)(a), for the HRD Corp register check |
| Facilitating bookings and communications between Users | Contract, s.6(2)(a) |
| Processing subscription payments and commission invoicing | Contract, s.6(2)(a); legal obligation, s.6(2)(c) |
| Compliance with tax, audit and statutory record-keeping (including LHDN e-Invoicing) | Legal obligation, s.6(2)(c) (Income Tax Act 1967, Service Tax Act 2018, Companies Act 2016) |
| Usage records to run the service (Clause 3.6(a)) | Contract, s.6(2)(a) |
| Fraud prevention, security monitoring, dispute investigation (Clause 3.6(b)) | Legal obligation, s.6(2)(c) (Security Principle, section 9); contract, s.6(2)(a) |
| Customer support and service announcements | Contract, s.6(2)(a) |
| Product analytics and service improvement (Clause 3.6(c)), including the visitor cookie | Consent, s.6(1)(a), given in the cookie banner; withdraw at any time |
| Direct marketing (newsletters, promotions, partner offers) | Consent, s.6(1)(a); opt out at any time (section 43) |
Where a purpose relies on consent, we ask for it in a form we can record and keep the record (Regulation 3, Personal Data Protection Regulations 2013).
6. Direct Marketing
6.1 We will only send you direct marketing communications where you have given consent (typically via a tick-box at sign-up or in account preferences).
6.2 You may withdraw consent at any time by:
(a) clicking the “unsubscribe” link in any marketing email;
(b) switching it off in Account settings; or
(c) writing to privacy@wisdomhub.com.my.
6.3 We will action your opt-out within fourteen (14) days of receipt and confirm in writing in accordance with section 43 of the PDPA.
7. Disclosure to Third Parties
We disclose personal data only as set out below, and only to the extent necessary:
(a) Other Users on the Platform — to facilitate bookings (e.g., Client sees Trainer profile and contact upon confirmation; Trainer sees Client brief).
(b) Service Providers acting on our behalf: cloud hosting ([provider name] — Malaysia-hosted; our database and document storage are located in Malaysia), payment gateway (Billplz), email delivery provider, customer support tools, MyInvois integration partner, web analytics (Google Analytics 4, loaded through Google Tag Manager, with your consent under the Cookies Policy), web font delivery (Google Fonts, which receives your IP address and browser details when a page loads and sets no cookie), and, where introduced, sanctions/PEP screening providers (none in use at present).
(b1) AI service providers: where a Platform feature uses an external AI service (for example, programme description drafting), only your profile and area-of-expertise text is sent to that provider. Identity documents, certificates, NRIC/passport numbers, and SSM numbers are never sent to any AI service. The provider is named in our sub-processor list at [/legal/sub-processors].
(c) HRD Corp — for accreditation verification, where the User has authorised disclosure.
(d) Professional advisers (lawyers, auditors, accountants) under duties of confidentiality.
(e) Regulators, courts, or law enforcement when required by Malaysian law or legal process.
(f) Acquirers in connection with a merger, acquisition, or asset sale, subject to confidentiality undertakings.
We do not sell personal data to third parties.
A current list of material sub-processors is maintained at [/legal/sub-processors] and refreshed on change.
8. Cross-Border Transfers
8.1 Where we transfer personal data outside Malaysia (for example to Google, whose analytics and font services process your IP address outside Malaysia), we ensure the transfer complies with section 129 of the PDPA as amended on 1 April 2025, relying on one of the following:
(a) the place has in force a law substantially similar to the PDPA, or ensures a level of protection at least equivalent to the PDPA (section 129(2)), which we assess and record in a Transfer Impact Assessment for each non-Malaysian processor;
(b) your consent to the transfer (section 129(3)(a));
(c) the transfer is necessary for performance of a contract with you (section 129(3)(b)); or
(d) we have taken all reasonable precautions and exercised all due diligence to ensure the personal data will not be processed in that place in a way that would contravene the PDPA (section 129(3)(f)), including standard contractual clauses, recognised certifications (ISO 27001, SOC 2 Type II), or binding corporate rules.
8.2 You may request a copy of the safeguards in place for any specified transfer by writing to privacy@wisdomhub.com.my.
9. Security
9.1 We apply reasonable technical and organisational measures to protect personal data, including encryption in transit (TLS), encryption at rest for sensitive fields, role-based access controls, multi-factor authentication for staff with privileged access, audit logging, periodic penetration testing, vulnerability management, and annual staff PDPA training.
9.2 Data breach notification. A personal data breach is any breach, loss, misuse or unauthorised access of personal data (section 4 of the PDPA). If one occurs we will:
(a) notify the Personal Data Protection Commissioner as soon as practicable and within seventy-two (72) hours of the breach where it causes or is likely to cause significant harm, judged on the nature of the data and the likely effect on you (for example, identity or financial data, account credentials, or sensitive personal data), and in any case where more than one thousand (1,000) data subjects are affected;
(b) notify you without unnecessary delay and within seven (7) days of notifying the Commissioner where the breach causes or is likely to cause significant harm to you; and
(c) keep a register of every personal data breach, whether or not notified,
in accordance with section 12B of the PDPA (in force 1 June 2025) and the Commissioner’s Data Breach Notification Guideline (v1.0, 25 February 2025).
9.3 Our internal Incident Response Runbook governs detection, containment, eradication, recovery, notification, and post-incident review. Staff are trained annually on the runbook and tabletop exercises are conducted at least once per year.
10. Retention
We retain personal data only for as long as necessary for the purposes for which it was collected, or as required by law:
| Category | Retention Period |
|---|---|
| Profile and account data (name, contact details, summary, programmes, articles, plan) | Duration of account, then deleted within 30 days of closure |
| Accreditation and other uploaded certificates | Duration of account, then deleted within 30 days of closure or of withdrawal of consent, whichever is earlier |
| Briefs, conversation messages, and files shared in a conversation | 24 months from the closure of the conversation |
| Booking and commission records | 7 years (Income Tax Act 1967 record-keeping) |
| Receipts, invoices, credit ledger, payment-gateway references, and e-Invoice records | 7 years (Companies Act 2016 s.245; Income Tax Act 1967 s.82 and 82A; Sales Tax Act 2018 and Service Tax Act 2018 s.24; LHDN e-Invoice Guideline). Kept after account closure. |
| Sign-in code records | 12 months |
| Usage records (Clause 3.6) in identifiable form | 12 months from the event, then reduced to counts and totals with every identifier removed. Reduced sooner if you close your account or withdraw analytics consent (see 10.2) |
| Visitor cookie browsing history not yet joined to an account | 12 months from the last visit, or on withdrawal of the cookie choice, whichever is earlier |
| Marketing consent records | Until withdrawal + 2 years |
| Marketing opt-out lists | Indefinite (to honour opt-out) |
| Support correspondence | 3 years from closure |
| Server logs and security records | 12 months |
| Acceptance/audit trail records | Duration of account + 7 years (Evidence Act 1950) |
| Counts and totals with all identifiers removed | Indefinite (no longer personal data) |
10.1 Disposal record. We keep a written retention schedule for every category above and a record of each disposal, and produce both to the Commissioner on request (Personal Data Protection Standard 2015, Retention Standard 6.1).
10.2 How we delete. When a retention period ends, when you close your account, or when you withdraw a consent that a record depended on, we do one of two things:
(a) delete the record; or
(b) where a record must survive for counts and totals, or because a financial record built on it must be kept, remove from it every field that identifies you or could be joined back to you: name, email address, mobile number, account ID, session ID, visitor cookie identifier, IP address and device identifiers. What remains cannot be linked to you by us or by anyone else, and we test that before we treat it as no longer personal data.
Financial records listed above are kept whole for their statutory period, with your identity in them, because the law requires it.
11. Your Rights as a Data Subject
Under the PDPA, you have the right to:
(a) Access — request a copy of personal data we hold about you (section 30);
(b) Correction — request correction of inaccurate or incomplete data (section 34);
(c) Withdraw consent — for any processing based on consent (section 38). We then stop that processing. Records we keep on the contract or legal-obligation bases in Clause 5 are not affected, but Clause 10.2 applies to your identity in them;
(d) Object to processing that is causing or is likely to cause you substantial and unwarranted damage or distress (section 42), except where the processing is necessary for the contract or a legal obligation;
(e) Limit processing for direct marketing (section 43);
(f) Data portability — ask us, by notice given by electronic means, to transmit your personal data directly to another data controller of your choice (section 43A, in force 1 June 2025). The right is subject to technical feasibility and compatibility of the data format; and
(g) Lodge a complaint with the Personal Data Protection Commissioner.
11.1 To exercise these rights, file the request from Account settings (each request is logged with the time you filed it) or contact privacy@wisdomhub.com.my. We will:
(a) acknowledge receipt within seven (7) days;
(b) respond substantively within twenty-one (21) days of receipt of a verified request, in accordance with sections 31 and 35 of the PDPA;
(c) where extension is necessary due to complexity, notify you with the reason and the extended timeline.
A reasonable fee may apply for access requests as permitted by the PDPA.
12. Cookies and Tracking
12.1 We set strictly necessary cookies (your session, security tokens, and the record of your cookie choice) without asking. We set analytics cookies (Google Analytics 4, loaded through Google Tag Manager, and our own visitor cookie described in Clause 3.6) only if you accept them in the cookie banner, and neither the tags nor the visitor cookie are loaded or set until you do. We set no marketing cookies at present. If we introduce any other category, the banner and the Cookies Policy are updated before it is enabled.
12.2 Detailed information is in our Cookies Policy, published on the Platform as the Cookies section of this Privacy Policy page ([/privacy#cookies]).
13. Children
13.1 The Platform is not directed at, and we do not knowingly collect personal data from, individuals under 18 years of age. If you believe we have inadvertently collected such data, contact us for prompt deletion.
14. Changes to This Policy
14.1 We may update this Policy from time to time. Material changes will be notified via email and/or in-app notice at least fourteen (14) days before taking effect. The “Last Updated” date and “Version” number will reflect the most recent revision. A versioned archive is maintained at [/privacy/archive].
15. Complaints and Contact
If you have a question or complaint about our handling of personal data:
- Email: privacy@wisdomhub.com.my
- Post: Data Protection Officer, [Address], Malaysia
If you are not satisfied with our response, you may lodge a complaint with the Personal Data Protection Commissioner of Malaysia:
Jabatan Perlindungan Data Peribadi (JPDP)
Aras 6, Kompleks Kementerian Komunikasi dan Multimedia
Lot 4G9, Persiaran Perdana, Presint 4
62100 Putrajaya, Malaysia
[www.pdp.gov.my]
16. Languages
16.1 This Policy is issued in Bahasa Malaysia and in English, as section 7(3) of the PDPA requires. The cookie banner and every consent checkbox are shown in both languages. [Bahasa Malaysia version pending.]
Cookies Policy
Version 1.5 draft · 18 October 2026
WisdomHub (“we”, “us”, “our”)
Operated by TRAINERS HUB SDN. BHD. (Company No. 202601033142 (1695237-T))
Effective Date: [Date]
Last Updated: 12 September 2026 (visitor cookie, legal bases, usage records)
This Cookies Policy explains how we use cookies and similar tracking technologies on WisdomHub (the “Platform”). It supplements our Privacy Policy and is consistent with the Notice and Choice Principle of the Personal Data Protection Act 2010 (“PDPA”).
1. What Are Cookies?
Cookies are small text files placed on your device (computer, tablet, phone) when you visit a website. They allow the website to recognise your device and store information about your preferences or past actions.
We also use similar technologies such as local storage, session storage, web beacons, pixels, and software development kits (“SDKs”) in mobile applications. References to “cookies” in this Policy include these other technologies.
2. Categories of Cookies We Use
We classify cookies into four categories. At present we set the first category always, and the analytics category only with your consent. A cookie banner lets you accept or decline analytics cookies when you first visit, and your choice can be changed at the cookie banner. No functional or marketing cookies are set today.
2.1 Strictly Necessary Cookies (always on)
Essential for the Platform to function. Cannot be turned off because the Platform will not work without them.
Examples:
- Session and authentication tokens
- Load balancing
- Security (CSRF protection, fraud detection)
- Cookie consent state itself
Legal basis: For a signed-in User, necessary for the performance of the contract between you and us (PDPA section 6(2)(a)) and for the security we owe you under section 9 (section 6(2)(c)). For a visitor without an account, these cookies hold no information that identifies you: the session token and security token are random values, and the consent record holds only your banner choice.
2.2 Functional Cookies (consent required)
Enable enhanced functionality and personalisation, such as remembering your language preference, dashboard layout, or recently viewed Trainers/TPs.
If you decline, certain features may revert to default settings each visit.
2.3 Analytics Cookies (consent required)
Help us understand how Users interact with the Platform so we can improve it. Aggregate metrics include page views, feature usage, session duration, and error rates.
Two analytics cookies exist. Google Analytics 4 counts visitors. Our own visitor cookie holds a random identifier so that, if you accept, the pages you look at before registering can be joined to your account once you register. If you decline, the visitor cookie is not set and nothing you did before registering is linked to you. Withdrawing your choice at the cookie banner deletes the browsing history held under that identifier (Privacy Policy Clause 3.6 and 10).
Where possible we configure analytics tools with IP anonymisation and PII minimisation.
Legal basis: your consent, given by an accept in the cookie banner and recorded (PDPA section 6(1)(a); Regulation 3, Personal Data Protection Regulations 2013).
2.4 Marketing Cookies (consent required)
Used to deliver targeted advertising and measure ad effectiveness on third-party platforms (e.g., LinkedIn, Meta, Google).
If you decline, you will still see advertising, but it will be less personalised.
3. Specific Cookies We Set
| Cookie | Category | Provider | Purpose | Expiry |
|---|---|---|---|---|
| Session cookie | Strictly Necessary | Platform | Keeps you signed in after you enter your one-time code | Deleted on sign-out or when the session expires |
| Security token | Strictly Necessary | Platform | Protects forms against cross-site request forgery | Session |
| Consent record | Strictly Necessary | Platform | Remembers that you have read the Privacy Notice, and your analytics choice | 12 months |
_ga, _ga_* | Analytics (consent required) | Google Analytics 4 | Visitor counting and behaviour analytics. Loaded through Google Tag Manager only after you accept analytics cookies. IP anonymisation on. | Up to 2 years |
| Google Tag Manager | Analytics (consent required) | Loads the analytics tags above. Sets no cookie of its own. Not loaded until you accept. | — | |
Visitor cookie (wh_visitor) | Analytics (consent required) | Platform | A random identifier. Keeps the pages you looked at before registering and joins them to your account if you register. Set only after you accept analytics cookies. Deleted, with the history under it, when you withdraw your choice. | 12 months |
Local browser storage. Your browser also keeps a local copy of a half-finished registration, profile, brief, or programme form so it is not lost if you close the tab. This is browser storage, not a cookie. It never leaves your device and is cleared when the form is submitted.
Usage records. Once you are signed in, what you do on the Platform is recorded on our servers against your account (Privacy Policy Clause 3.6). That is not a cookie and is not switched off by the banner; the banner controls only whether those records are also used for product analytics and whether pre-registration browsing is joined to them.
3A. Cookies we may introduce later (not set today)
None of the following is set at present. Each will be added to Section 3, and the banner in Clause 5.1 enabled, before it is used.
| Cookie | Category | Provider | Purpose | Expiry |
|---|---|---|---|---|
lang_pref | Functional | Platform | Remembers your language preference | 12 months |
_mp_* | Analytics | [Mixpanel / Amplitude — confirm] | Product analytics | Up to 1 year |
fr, _fbp | Marketing | Meta | Ad targeting and measurement | Up to 90 days |
li_* | Marketing | Ad targeting and measurement | Up to 6 months | |
IDE, NID | Marketing | Google Ads | Ad targeting and measurement | Up to 13 months |
4. Third-Party Cookies
Google Fonts. Our pages load their typefaces from Google Fonts. That is not a cookie: Google receives your IP address and browser details when the font file is requested, and sets nothing on your device. It is listed as a service provider in the Privacy Policy.
Some cookies are set by third parties that provide services on our behalf or measure ad performance. These third parties are listed in the table above and in our Sub-Processor list at [/legal/sub-processors].
Each third-party cookie is subject to that third party’s own privacy and cookies notices. We do not control what third parties do with the data they collect through cookies set on the Platform, beyond the contractual safeguards described in the Data Processing Addendum and our Sub-Processor terms.
5. How to Manage Cookies
5.1 On the Platform
When you first visit, our cookie banner asks whether you accept analytics cookies. Strictly necessary cookies are set either way, because the Platform does not work without them. Your choice, the banner wording you saw, and the time are recorded. You can change your choice at any time at the cookie banner or by clearing the consent record via your browser. Declining after an earlier accept stops Google Analytics 4 and deletes the visitor cookie and the browsing history held under it.
5.2 In Your Browser
Most browsers let you block, delete, or restrict cookies through their settings. The exact steps vary by browser:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Safari: Settings → Privacy
- Firefox: Settings → Privacy & Security
- Edge: Settings → Cookies and site permissions
Blocking strictly necessary cookies will prevent the Platform from working correctly.
5.3 Do Not Track
Most browsers offer a “Do Not Track” (“DNT”) signal. Industry standards on responding to DNT are still developing. We currently treat a “DNT: 1” signal as a request to disable analytics and marketing cookies, equivalent to declining those categories in the cookie banner.
6. Mobile Applications
We have no mobile application at present. If one is released, it may use SDKs and device identifiers (e.g., Advertising ID, Identifier for Vendors) for similar purposes. You can manage these through your device settings:
- iOS: Settings → Privacy & Security → Tracking
- Android: Settings → Google → Ads (reset advertising ID or opt out of personalisation)
7. Children
We do not knowingly use cookies to collect data from individuals under 18 years of age.
8. Updates to This Policy
We may update this Policy from time to time to reflect changes in the cookies we use or in legal requirements. The “Last Updated” date and “Version” number above will reflect the most recent revision. A versioned archive is maintained at [/cookies-policy/archive].
9. Contact
Questions about this Cookies Policy or our use of cookies should be directed to:
- Email: privacy@wisdomhub.com.my
- Post: Data Protection Officer, [Address], Malaysia
10. Languages
This Policy and the cookie banner are issued in Bahasa Malaysia and in English (PDPA section 7(3)). [Bahasa Malaysia version pending.]