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. Register purpose
This disclosure identifies suppliers authorized to process personal data on BookDulu's behalf in the actual contracted deployment. It is separate from a merchant's own independent providers. A list of product integrations is not an authorized subprocessor register. This draft cannot be published as a complete factual disclosure until the entries below are verified.
2. Required entry information
For each supplier record its full contracting legal entity, service/purpose, role, categories of data and subjects, processing and remote-access countries, storage/backup locations, contractual protection, transfer mechanism where required, onward suppliers and effective/review dates. Use the executed contract and deployment evidence; do not infer country from a brand, domain, timezone or salesperson.
3. Hosting and backup
[Details pending confirmation.] Development/UAT and live deployment must be assessed separately. A known server IP does not establish the full processing chain. Internal hosting is not a third-party appointment but still needs a factual location and access assessment.
4. Transactional communications
Brevo and configurable SMTP delivery paths exist. [Details pending confirmation.] Email authentication, safe branding links and message logs require independent operational checks. Do not publish real credentials or private message bodies in this register.
5. Payment processing
Revenue Monster integration exists for subscription payments. [Details pending confirmation.] A payment provider may act independently for some regulated/fraud purposes and as a processor for others; identify the actual roles. No unperformed tokenization, settlement or recurring-payment UAT is asserted.
6. Support and additional suppliers
[Details pending confirmation.] Suppliers must not be omitted because their use is operational rather than visible in the application repository. Describe any genuinely anonymized processing accurately and verify that re-identification is not reasonably possible before treating it as outside the personal-data register.
7. Authorization and changes
The final DPA must identify the applicable specific or general authorization arrangement, advance notice, objection window and resolution or exit process. [Details pending confirmation.] Publish updates with effective dates and preserve earlier registers needed for accountability. A materially different processing country requires a renewed transfer assessment where applicable.
8. Malaysia, Singapore and regional transfers
Assess Malaysian section 129 conditions and relevant Singapore overseas-transfer requirements against actual destinations. ASEAN model clauses may be used where appropriate only after completing the required parties, modules and schedules. No declaration of worldwide adequacy, universal local storage or automatic exemption is made. Contact sjchin@sjsoft.my for a verified register or a proposed supplier objection through the agreed contract process.