Supported production builds are confirmed during scoping.
Questions that clarify scope and boundaries before access is granted.
Settle scope, access, evidence, data and support boundaries in writing for each engagement.
01
Access and scope
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.
What evidence is useful first?
A bounded time range, the observed symptom, relevant changes and the system boundary are usually more useful than an unfiltered export.
Do you replace vendor support?
No. We organise evidence across system boundaries; third-party vendors remain responsible for their products.
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; model and provider choices follow 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, language and support terms
Final terms, language arrangements and support boundaries 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 handover?
Only within an explicitly agreed service window, scope and escalation model. Named engineers and response targets are engagement-specific, not blanket promises.
Which languages are available?
Written materials are provided in English, Traditional Chinese and Simplified Chinese. Meeting, incident-handling and training language is agreed for each engagement.
Staffing and response targets are engagement-specific, not blanket promises.