RecursiveX product operations Privacy & data handling >>> Contract-led client systems

Privacy & Data Handling

Clear boundaries for website data and client project data.

RecursiveX builds and operates custom workflow software. This page explains how website enquiries are handled, and how client system data is normally governed by project agreements, data processing terms, and documented client instructions.

Website scope
Enquiries, correspondence, basic site operations
Client systems
Handled under project-specific agreements
Company
RecursiveX PLT, Malaysia

This page is a public summary, not a replacement for project contracts.

The boundary

This page covers data handled through this website, direct enquiries, and general business correspondence with RecursiveX.

For custom software, Atlas workflows, hosted systems, integrations, support, migrations, and other client work, the applicable project agreement, statement of work, service terms, data processing terms, and documented client instructions control the specific data handling arrangement.

What is handled when someone contacts RecursiveX.

Information provided

Enquiries and business context.

If you email RecursiveX, the information handled may include your name, email address, company, message content, attachments, and the context needed to respond.

Purpose

Respond, operate, and keep records.

Website and correspondence data is used to respond to enquiries, discuss work, maintain business records, operate the website, protect systems, and meet legal or administrative needs.

Retention

Kept only while useful or required.

Correspondence and business records are kept for as long as reasonably needed for the enquiry, relationship, administration, security, or legal record-keeping.

Custom software data is handled according to the engagement.

Website and enquiries

RecursiveX decides how to respond and keep business records.

This includes direct communication with people who contact RecursiveX, plus basic website operation and administrative records.

Client systems

The client usually defines the workflow purpose and rules.

For Atlas and custom systems, project data is normally handled under the client agreement and documented instructions.

Typical data
Messages, contact details, business context, correspondence records.
Applicant, employee, business, document, signature, review, export, and operational workflow records.
Main rules
This public page, business record needs, and applicable law.
Project agreement, data processing terms, work order, access rules, hosting setup, and client instructions.
End-user requests
Contact RecursiveX for enquiries about data sent directly to RecursiveX.
Contact the client organization that collected the data; RecursiveX can assist the client according to the engagement.
End of service
Business records are retained or deleted according to operational and legal needs.
Return, export, retention, archive, or deletion steps should be defined in the project terms.

The default posture is practical, limited, and contract-led.

01

Access control

Client systems are designed with role-based access, permissions, and limited administrative access appropriate to the project.

02

Confidentiality

Client production data is handled as confidential project information and is not used for unrelated demos, marketing, or AI training without written permission.

03

Hosting and vendors

Hosting, storage, email, monitoring, and other subprocessors or vendors should be documented in the project arrangement where relevant.

04

Backups and recovery

Backup, recovery, retention, and export expectations are set according to the system architecture and client agreement.

05

Incident handling

Security incidents are assessed, contained, and communicated according to the applicable service terms, legal obligations, and client instructions.