Confidentiality and data protocol for Bali investigations
Confidentiality Protocol

Confidentiality & Data Protocol

Minimum data. Clear scope. Proportionate output.

In sensitive cases, safety starts before investigation. The right first step is not sending every file, but clarifying the objective, area, timeline, and decision that needs protection.

Core principles

  • Start with a summary, not sensitive documents.
  • Additional data is requested only after scope and legal boundaries are clear.
  • Unsafe requests are rejected before the process begins.
  • The final report includes only information relevant to the verification objective.

Confidentiality protocol

Data minimization protocol for sensitive Bali cases

The goal is simple: enough information to assess scope, without exposing the client, related parties, or the legal position unnecessarily.

1. Initial intakeCase type, area, short timeline, urgency, and the decision that depends on verification.
2. Legal screeningRequests involving hacking, spyware, illegal interception, doxing, or intimidation are rejected.
3. Written scopeAdditional data is requested only when it is needed for the agreed output.
4. Limited outputReports focus on facts, red flags, gaps, and safer next steps, not unnecessary exposure.

What not to send first

Do not send yet

Passwords, OTPs, account access, card data, full identity documents, child data, or sensitive files not requested.

Safe for initial intake

Case type, Bali area, short timeline, urgency, relationship to the parties, and the decision you need to make.