Review status
PENDING LEGAL REVIEW. Proposed revision 2026-10-19-draft-2. No effective date. This text is a review draft and does not replace any effective agreement. Square-bracketed review items must be resolved before approval.
Operator
BookDulu is operated by SJSOFT SDN BHD (202301022865), 23, Jalan PJS 5/8 Taman Desaria, 46150 Petaling Jaya, Selangor, Malaysia. Contact: sjchin@sjsoft.my; +60 16 220 0338.
1. Scope and who is responsible
This notice describes BookDulu's own account, subscription, website administration, support and security processing. A business using BookDulu generally decides why it processes its customers', students', patients', staff or guardians' records. For those service records, the business is normally the responsible controller or organization and BookDulu acts on its instructions. The actual activity and applicable law determine the roles; a software label alone does not.
For a business's appointment, student, clinical or invoice record, contact that business first or ask us to route your request. We will not disclose another tenant's information merely because an email address appears in both accounts. This platform notice does not replace each merchant's separate notice.
2. Information we handle
Account information includes names, email addresses, login identifiers, password credentials in the application's protected credential system, verification challenges, account status and staff permissions. Business information includes business identity, contact and outlet details, operating country, currency, timezone, published branding and configuration. Subscription information includes selected plans, authorizations, provider references, invoices, receipts and payment status.
Depending on the contracted modules, merchant records may include customer and owner contacts, pets, vehicle and service details, appointments, classes, attendance, package entitlements, credit ledgers, student and guardian relationships, communications, forms, documents and clinical information. Technical and support information may include request and security events, device/browser information supplied during use and correspondence. [Details pending confirmation.]
3. Sources and accuracy
We receive information from you, authorized business users, permitted guardians, support contacts and the relevant transaction or delivery providers. A merchant must ensure it has authority to supply another person's information. Keep details accurate and notify the responsible business or us of errors. Do not place full payment-card data, passwords, OTPs, private keys or unnecessary health information in free-text fields or support email.
4. Purposes and legal grounds
We use necessary information to create and verify accounts, provide authorized functionality, administer subscriptions, reconcile payments, respond to requests, prevent abuse, investigate security events and meet applicable legal duties. Merchant processing is limited by its lawful instructions and the DPA. The responsible organization must establish any consent, contractual necessity, statutory duty or other ground that the applicable law actually permits; this notice does not create a universal “legitimate interests” ground for every country.
5. Required information and choices
Forms identify required information. Without information necessary for verification, a transaction or lawful delivery of a requested service, that step may not proceed. Optional purposes must be identified separately. Agreeing to service Terms or acknowledging this notice is not blanket consent to marketing, sensitive-data collection or unrelated disclosure. If consent is the applicable basis, the relevant organization must provide an appropriate choice and explain consequences of withdrawal.
6. Recipients
Access is limited by role, outlet scope and purpose. Relevant recipients may include authorized personnel, contracted hosting and backup providers, transactional delivery providers, payment processors, professional advisers and authorities when lawfully required. A merchant receives the records it is authorized to control; another merchant does not receive them merely through sharing BookDulu. Transfers in a genuine corporate transaction require lawful safeguards and appropriate notice.
Brevo/SMTP and Revenue Monster are integration options in the software. The presence of an integration does not establish the contracting entity, production use or processing country. [Details pending confirmation.] We make no unverified claim that data is sold, never sold, used for AI training or never used for AI training: [Details pending confirmation.]
7. International processing
Our operator is Malaysian. Hosting, backup, support and provider locations must be identified separately; a timezone or domain name does not identify storage country. [Details pending confirmation.] Before a restricted transfer, the responsible organization must assess the applicable Malaysian, Singaporean or other national requirements, the recipient and contractual/technical protections. ASEAN model clauses may support a lawful arrangement when properly completed; naming them alone does not implement one.
8. Retention and account closure
We retain information for the purposes and period justified by the applicable legal and contractual duties, then securely dispose of it or remove identification where appropriate. Closing an account does not automatically erase financial, credit, clinical, audit or dispute records that require retention. Backups require a defined lifecycle and access safeguards. [Details pending confirmation.] We do not promise a fixed deletion date that has not been operationally established.
9. Security and incidents
The application uses tenant and permission checks and access restrictions. Security also depends on deployment, staff practice, provider contracts, backups and monitoring. No system is risk-free and no unverified encryption-at-rest, certification or recovery guarantee is asserted. [Details pending confirmation.] Where a breach requires notification, the responsible organization must assess the event and communicate through the applicable regulator and individual-notification procedure. Reporting a concern does not require waiting for a complete investigation.
10. Access, correction and other requests
Contact sjchin@sjsoft.my or use the signed-in Privacy Requests page. We verify identity and, for representatives, authority; request only proportionate evidence and use a secure channel for sensitive material. Depending on the law and circumstances, requests may concern access, correction, consent withdrawal, deletion, restriction, objection or transfer/export. Not every remedy applies in every jurisdiction and an export request is not a promise of a complete automatic portability tool.
We may need to clarify the records, refer a merchant-controlled request, protect another person's rights, retain legally required records or explain a lawful exception. Responses and extensions follow applicable law; [Details pending confirmation.] A recorded request status does not itself perform deletion or delivery.
11. Malaysia notice
Malaysian processing is assessed under the Personal Data Protection Act 2010 as amended and applicable instruments. Read the Bahasa Malaysia and English notices together. Acknowledgement does not remove rights or allow a prohibited disclosure. Requests concerning applicable access, correction, consent withdrawal, direct-marketing choices or data portability are assessed under the provisions and conditions in force. Complaints may be referred to the Malaysian Personal Data Protection Commissioner where appropriate. [Details pending confirmation.]
12. Singapore and other ASEAN countries
For relevant Singapore processing, assess BookDulu's role as an organization or data intermediary and the obligations applying to it. Requests may include access, correction and withdrawal of consent, subject to applicable conditions and exceptions. Overseas transfers require the applicable comparable-protection assessment. Complaints may be raised with the Singapore Personal Data Protection Commission where appropriate. Do not interpret this paragraph as an assertion that a data-portability regime is operational without checking the applicable commencement and rules.
Other ASEAN jurisdictions have separate laws. [Details pending confirmation.] No “ASEAN standard” replaces those checks. Where EU/UK law actually applies, a separate applicability and transfer review is needed; this ASEAN-focused draft does not automatically invoke GDPR or create a European establishment.
13. Children, health and sensitive records
Children's information and clinical records require additional necessity, authority, notice and security assessment. See the Children & Guardians and Healthcare addenda. A guardian link is not proof of unlimited authority; a platform feature is not consent to treatment or a school activity. Do not upload unnecessary sensitive records or national identifiers. Marketing and publication of a child's image require their own lawful assessment and choice.
14. Cookies and marketing
The Cookie Policy explains verified browser storage. Security and session storage may be necessary for requested functionality; non-essential tracking requires an applicable legal assessment and, where required, prior choice. Transactional notices concern requested accounts or services. Marketing must have its own lawful basis and controls, including relevant direct-marketing or Do Not Call requirements. [Details pending confirmation.]
15. Changes and contact
Approved notices identify revision and effective date. We explain material changes and obtain a fresh choice when the law requires one. We do not backfill consent for existing accounts. Contact the operator above for platform questions, and the merchant for its service records. We will not ask you to email a password, verification code or full card number.