iTGTrackerData Processing Agreement

Document content version: 2026-10-17-v2. Website language edition: 2026-10-22. These translations do not change accepted orders or their agreed contractual language. This website now uses fixed translations and no longer loads Google Translate. References in the original policy describe its publication context.

iTGTracker Data Processing Agreement (DPA)

Document version: 2026-10-17-v2. English translation; applies with a validly accepted order and confirmed attachments.

The provider is TYRENX TECHNOLOGIES, 202603272412 (AS0523259-D), a Malaysian sole proprietorship; address and contact are in the Terms. The customer is the enterprise in the accepted order. This DPA becomes effective only upon both parties' valid acceptance and covers hosted personal data processed on lawful customer instructions. Independently determined platform-operation data follows the Privacy Policy. Mandatory law prevails; this DPA governs data-protection matters over general service provisions.

1. Processing description

Purposes are ordered authorised collection, retrieval, staff-operation records, attribution, QA, review, performance, device approval, APIs and exports—not unrelated advertising, sale or general-purpose AI training without separate authority. Operations comprise receiving, transmitting, storing, retrieving, displaying, analysing, calculating, correcting, exporting, restricting and deleting within lawful instructions.

Data subjects include administrators, staff, conversation participants, customers and business/support contacts. Data includes captured content, identifiers/times, supported previews, Sessions/Handle/Handover/Done, attribution, rules, model/review results, performance, device/security information. Sensitive/special categories are not generally required; necessity requires written scope, grounds and additional safeguards before processing.

Processing lasts through service and clearly purposed lawful termination/export, deletion, backup and limited statutory-retention periods. The scoring scan window is not general retention; historical-evidence periods are not a universal promise.

2. Instructions and customer duties

Instructions include the effective order, authorised settings and support requests checked for identity, tenant, role and scope. Customers determine lawful purposes/grounds, notices, connection authority and accurate lawful instructions. We retain our own processor, security and confidentiality duties.

Process only on recorded lawful instructions. Where law requires different processing, notify where permitted. Promptly identify potentially unlawful instructions, suspend relevant processing where necessary and seek lawful alternatives without expanding purposes. Accepting a contract does not authorise access to other companies' or out-of-scope individuals' information.

3. Personnel and security

Restrict access to necessary authorised personnel under confidentiality duties and revoke unnecessary privileges when roles change. Apply risk-appropriate account authentication, role/tenant isolation, protected transmission and relevant storage, credentials, audit, backup and recovery.

Do not promise encryption of every field, cache, export or third-party copy, impossibility of reverse engineering, zero breaches or comprehensive certification. Record verified measures, limits and support access accurately. Material changes must not unjustifiably reduce agreed protection.

4. Support access, confidentiality and authorities

Platform administration is not general authority to browse customer content. Technical access requires lawful purpose, necessity, appropriate approval and traceability. Absence of a BO conversation screen is not proof that technical access is impossible.

Verify the authority, grounds and scope of official requests, notify customers where permitted and limit disclosure with necessary records. Respect lawful prohibitions on notification. Confidentiality does not exclude statutory customer/individual rights.

5. Subprocessing and external integrations

Use the recipient/subprocessor register confirmed with the order as the authorisation scope, imposing protection suitable to entrusted activities. Record infrastructure, optional cloud scoring and other entrusted functions separately. Banks, Telegram, customer-selected Drive and customer devices do not automatically have identical legal roles.

Before adding/replacing recipients, explain services, data, locations and safeguards as required by law and the effective order and obtain necessary instructions/authority. Customers may make reasonable data-protection objections; discuss alternatives, stop relevant processing or lawfully terminate affected services without punishing a valid legal objection with ETF. Urgent changes still require necessary authority and prompt explanation.

This version does not promise an unimplemented fixed thirty-day subprocessor notice or certification of all suppliers. Any fixed period requires a separate effective operational commitment. Subprocessing does not eliminate our statutory/contractual responsibility.

6. Locations and transfers

The principal host was checked as DigitalOcean Singapore (sgp1). Backups, suppliers, support and device copies must be separately recorded. New transfer paths require applicable grounds and safeguards; encryption or reading a policy alone is insufficient.

Assess Malaysian PDPA section 129 and applicable requirements. Where other laws apply, execute necessary transfer agreements, assessments and attachments separately. This DPA does not mean GDPR standard contractual clauses or all cross-border permissions are already in place.

7. Rights, corrections and assistance

Promptly refer hosted-data requests to customers where law permits and reasonably assist retrieval, verification, correction, export, restriction and deletion. Do not decide matters belonging to the customer without authority/law, or use customer control to avoid our own duties.

Verify necessary identity and scope, protect others' data and do not condition statutory requests on subscription acceptance, debt or ETF payment. Legally grounded charges require advance explanation. Assist necessary impact, security and transfer assessments with reasonable customer context.

8. Personal data breaches

On awareness, notify affected customers without undue delay with known nature, data/person categories, possible impacts, measures, recommendations and contact. Initial reports may be supplemented; do not wait for every investigation to finish.

Assist regulatory and individual notices according to actual roles and statutory deadlines. An unimplemented processor twenty-four-hour target is not a controller's legal deadline; no additional fixed twenty-four-hour SLA is created here. Stricter valid written requirements and mandatory law prevail.

9. Termination, return, deletion and backups

All payment modes permit manual export requests within thirty calendar days after effective termination for retained authorised content. Timely valid requests survive our delay. Expired/deleted data, third-party rights and limited legal holds are separate; no automatic read-only account is promised.

Customers may lawfully choose return, deletion or a reasonable combination. Confirm data scope, production deletion and final backup removal/rotation separately and provide reasonable handling records. An unverified sixty-day target is not a fixed promise, but retention cannot be purposeless or indefinite. Legal holds must limit categories, purposes, access and ending conditions.

Backups cannot return deleted information to routine use; reapply effective deletions after disaster recovery. Customers manage downloads and customer-controlled Drive copies. Assistance is limited by rights; copied third-party files cannot be guaranteed retractable.

10. Verification, liability and acceptance

Provide information reasonably necessary to demonstrate compliance. A customer or confidential independent verifier may review relevant processing on reasonable notice without other customers' data or service disruption. Do not frustrate legal obligations through unreasonable limits in incidents, regulatory requests or credible non-compliance. Agree additional costs/scope beforehand.

Liability follows law and effective contracts; individual remedies are not excluded and a commercial cap does not automatically waive mandatory data duties. Record customer, order, authorised representative, version, full text, date/time zone and confirmed attachments. Do not sign blank attachments and later insert suppliers/locations. Material changes require applicable notice and renewed authority.