iTGTrackerPrivacy Policy

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 Privacy Policy

Version: 2026-10-17-v2. Published and effective: 17 October 2026. Chinese and Bahasa Melayu versions provide the same core information.

1. Operator, scope and contact

TYRENX TECHNOLOGIES is a Malaysian sole proprietorship, registration number 202603272412 (AS0523259-D). Business address: NO. 66, JALAN MUDA, OFF JALAN MERU, KAWASAN 19, 41050 KLANG, SELANGOR, MALAYSIA. Contact for privacy, access, correction and complaints: itgtrackercs@gmail.com.

This policy covers personal data in the iTGTracker website, Backend, BO, Windows Tracker, local QA, APIs, billing and support. Reading it does not waive personal rights or replace notices or consent legally required from employees or customers. This policy applies to relevant processing from publication; reading and acceptance records must not be backdated.

2. Our role and the customer's role

Where an enterprise customer determines the purposes and scope of hosted conversations, employee monitoring, QA or performance analysis, it is generally the controller and we act on its lawful instructions as processor. We act as an independent controller for platform accounts, billing, support and security where we determine the purposes. Roles follow the actual processing, not labels.

Employees, customers and other participants retain their statutory rights. Enterprise ownership of content or acceptance of an order does not transfer all individual data rights. Telegram, banks and Billplz may independently process data for their own services and obligations.

3. Data and sources

We process only the categories actually involved in enabled functions:

  • Enterprise and account information supplied by the customer or administrators: names, usernames, roles, contacts, status and permissions.
  • Authorized conversations: message text, message/chat/sender identifiers, timestamps, captured metadata and supported image previews.
  • Service and QA records: Sessions, Handle/Handover/Done, responsibility attribution, rule versions, model output, review explanations and evidence, reports and exports.
  • Technical and security information: device identifiers, approval/revocation, connection and login times, IP and necessary technical logs actually recorded, and authorization credentials.
  • Billing and support: orders, MYR amounts, invoices, payment status, transaction references, necessary payer information, submitted receipts, feedback and refund information.
  • Optional integrations: enabled cloud-scoring input/output, selected Google Drive folders and information needed to upload reports.

Sources include individuals, authorized customer personnel, approved connections, service operation and payment confirmations. We process actual conversation content, not metadata alone. This policy does not authorize extra collection for disabled functions. Receipts may contain financial information: redact unrelated balances and transactions first.

4. Purposes, grounds and choices

Purposes include supplying ordered functions, permissions and devices, collection and retrieval, QA and human review, response/performance reporting, authorized exports, payment verification and activation, support, corrections, abuse prevention, maintenance, disputes and lawful retention. Customer content is used only within lawful instructions and necessity.

Processing must satisfy applicable Malaysian PDPA consent requirements or other legally permitted conditions. Contractual necessity, legal obligations and security grounds are assessed for each activity; an employee is not automatically a party to the customer's subscription contract. Other applicable laws require their own assessment. A general “use means consent” statement is insufficient.

Without necessary account, verification, authorization or billing data we may be unable to perform the relevant function. Declining unrelated or optional information does not prevent other available services. Marketing requires a separate applicable basis and choice, not compulsory bundling with core services. We do not sell conversations or use them for unrelated advertising or general-purpose AI training without separate authorization.

5. Monitoring, sensitive information and children

Before monitoring, customers must inform relevant people about purposes, scope, recipients, retention and rights and establish the required lawful grounds. An administrator's approval or an employment contract does not automatically cover every monitoring activity.

Avoid unrelated private messages, passwords, OTPs, complete payment-card information and unnecessary identity, health or other sensitive information. Where special-category processing is necessary, applicable additional safeguards must be established. We do not guarantee automatic redaction of all sensitive content.

The service is for authorized enterprise use, not independent purchasing by children. Conversations may include children's information; the customer must apply legally required extra protection and contact us about inappropriate collection.

6. Recipients

Necessary data may be available to authorized customer users, confidential technical support, suppliers actually used for infrastructure/functions, verified professional advisers and authorities with a lawful basis. Access, purpose and confidentiality must match responsibilities.

DigitalOcean provides hosting. When FPX is actually available and selected, Billplz receives necessary payer name, email, order reference and amount; we do not request online-banking passwords. Customer-enabled Google Drive uploads involve selected reports and necessary Google authorization. Local models process relevant conversations on approved devices. Existing optional cloud-scoring code connects to the OpenAI API: the provider/model, transmitted content, locations and conditions must be disclosed and authorized before use; this policy does not automatically enable transmission. Telegram applies its own platform policies.

Unenabled Stripe, digital-asset channels and other proposed suppliers are not described as current recipients. The accompanying register records actual roles and status; new purposes or recipients require applicable notice, instructions and authorization.

Website inquiries and related email replies also involve Resend and the official support Gmail inbox for necessary contact details, business requirements and correspondence. Google Translate on the website and WhatsApp/Telegram contact links opened by users involve their respective third-party services. Processing follows actual use of the relevant function; an inquiry does not authorize transmission of an entire customer conversation database.

7. Locations and international transfers

A read-only server check identified the principal production host in DigitalOcean's Singapore region, sgp1. This does not establish that backups, all suppliers, support access or customer-device copies are confined to Singapore. Authorized users and support may access from their locations; customer downloads and Drive copies are managed by the relevant parties.

International transfers require applicable conditions under section 129 of the Malaysian PDPA and any other applicable law, suitable safeguards and records, and explanation or authorization where required. Encryption or supplier certification alone is not a transfer basis. “Cloud service” is not a blanket authorization for an unassessed new recipient or location.

8. Retention, exports and deletion

Data is retained for necessary purposes and applicable obligations, not indefinitely by default. Current image-preview rules allow up to 128 KB per preview and a 512 MB company content limit, with 30 days from message time; capture of every image is not guaranteed. The one-year rule stated for deleted-chat textual evidence applies only to that category, not all conversations, QA, logs or backups. The automatic-scoring scan window is not a general deletion period.

Ordinary conversations, QA, operational records, accounts, security, billing and support follow their respective purposes, lawful instructions, stated category arrangements and legal obligations. Customers can ask for the arrangements applying to their order and request deletion. Necessary legal/dispute retention must identify limited categories, grounds and ending conditions and restrict unrelated use.

All payment modes permit a manual export request within 30 calendar days after effective termination for retained data the requester is entitled to receive. A timely valid request is not invalidated by our delivery delay. This window does not extend a shorter disclosed category period or restore deleted information. Production deletion and final backup removal are recorded separately. Backups are not used to return deleted data to routine use; effective deletions must be reapplied after disaster recovery. Customers manage their own downloads and Drive copies.

9. Individual rights and requests

Depending on applicable law, individuals may request access, correction, withdrawal of applicable consent, cessation of direct marketing and applicable objection, restriction, deletion or portability. Conditions and exceptions apply; rights from another jurisdiction are not automatically unconditional local rights, and rights actually applicable are not excluded. Withdrawal generally does not invalidate prior lawful processing but may prevent necessary services.

Contact itgtrackercs@gmail.com with the request and relevant account/company. We verify only necessary identity and authority and protect others' data; do not send passwords, OTPs or unnecessary complete identity documents. For customer-controlled hosted information we assist referral and lawful handling, without using the customer contract or unpaid fees to obstruct statutory rights.

Malaysian access/correction requests follow the applicable statutory procedure: where applicable, usually within 21 days, with a further 14 days only where a lawful extension applies and written explanation is provided within the original period. Other requests and jurisdictions follow their own applicable periods. Refusals, limits and extensions must explain grounds and next steps; any legally permitted charge is explained beforehand.

Individuals may complain directly to Malaysia's Personal Data Protection authority, JPDP (www.pdp.gov.my), or another competent authority. The support address is a privacy contact and is not a statement that a statutory DPO has been appointed or registered.

10. Security and incidents

We apply risk-appropriate authentication, tenant/role controls, transmission and applicable storage protections, credential management, logs and backups. Protection of some server content and device credentials does not mean every field, local cache, downloaded file or third-party copy is encrypted. Absolute security is not guaranteed.

On becoming aware of a personal data breach we investigate, contain risks and fulfil applicable customer-assistance, regulatory and individual-notification duties according to our role. Initial information may be supplemented; notification must not await the completion of every investigation. Contractual operational targets do not replace statutory deadlines.

11. AI, human review and decisions

Models can make mistakes and evidence can be incomplete. An automatic pass is not human confirmation; unverified evidence is not a confirmed violation. Shared accounts or Handle alone do not establish authorship. Company review examples support that company's rules, not unauthorized cross-company training. We do not independently decide employment sanctions; customers should check original evidence and permit explanation and correction.

Local processing still involves device theft, access and log risks. Cloud processing and Drive uploads add external recipients. Available controls may stop relevant functions or revoke connections; server and third-party retention are handled separately.

12. Browser/device data, changes and activation

Necessary browser storage supports login tokens, language preferences and notice records. Windows components may retain configuration, credentials and logs. Browser clearing, sign-out, uninstalling, device revocation and Telegram-session revocation are different actions; none is a guarantee that every local/server copy is deleted. See the Cookie and Local Data Notice.

Material changes to purposes, recipients or this policy identify the new version and applicable date and require renewed choice or authorization where law requires. Reading a privacy notice, accepting subscription terms and agreeing to optional marketing are separate records. This version replaces earlier short privacy disclosures for subsequent processing without retrospectively expanding purposes. Prior versions and reading records are retained.