Questions that clarify scope and boundaries before access is granted.

Settle scope, access, data and support boundaries in writing for each engagement.

01

Access and scope

Assessment access starts with the minimum read-only set required to answer the agreed question.

Do you need administrator access?

Not for the initial assessment. Any later write access is time-bounded, named and separately approved.

Will you change production?

Only through a separately approved change window with validation, a rollback path and client ownership.

Which platform versions are supported?

Supported production builds are confirmed during scoping. Mixed MT4/MT5 estates are handled where the required documentation, access and representative test environment are available.

Do you replace vendor support?

No. We can organise evidence across system boundaries; third-party vendors remain responsible for their products.

Supported production builds are confirmed during scoping.

02

Data and confidentiality

The source list, location, retention and deletion procedure are agreed before collection.

Can logs contain personal or account data?

Yes. Logs may contain account identifiers, IP addresses, names, email addresses, comments and other identifiers. Collection is minimised and masking is used where feasible.

Where is client data processed?

In the location and infrastructure agreed against the client's data policy; the model/provider choice follows the same policy.

How long is data retained?

The configured retention period and deletion procedure are agreed before collection. Working copies are removed on schedule; the client retains agreed reports and artefacts.

Logs may contain account identifiers, IP addresses, names, email addresses, comments and other identifiers.

03

Commercial and support terms

Final terms are governed by the applicable agreement.

What does it cost?

Scope, acceptance criteria, timing and price are proposed after the environment and question are understood. No public rate card or outcome guarantee is implied.

Can support continue after handback?

Only within an explicitly agreed service window, scope and escalation model. Named engineer, backup and response targets are contract-specific, not blanket promises.

Which languages are available?

English, Traditional Chinese and Simplified Chinese are available for written material and delivery, subject to the agreed schedule.

Staffing and response targets are contract-specific, not blanket promises.