Sensitive by default

Your documents are part of the file.
Not marketing material.

Cross-border matters can involve passports, powers of attorney, title records, bank statements and family documents. The first intake should collect the situation first and sensitive originals only when they are actually needed.

● minimum necessary● purpose first● provider roles visible
The rule

Do not send a passport archive before anyone knows why it is needed.

We start with the outcome, identify the route, then request the records necessary for the next real step.

01Situation before documents

The first message can usually be plain language. A scan is requested when it helps decide or execute a concrete step.

02Minimum necessary set

We avoid asking for a full archive when a single page, data point or document is enough for the current stage.

03Know who receives what

When a notary, lawyer, translator, bank, authority or other provider needs a document, that role should be clear before the document is shared.

04Do not reuse client files casually

Client documents should not be repurposed as testimonials, examples or marketing content without a separate, appropriate basis and permission.

Document lifecycle

A sensitive document should move only when its job is clear.

Version, purpose, owner and next recipient matter as much as the file itself. This keeps an early draft from quietly becoming the document someone signs, translates or ships.

01Start with the situation, not the archive.

Describe

Location, outcome, deadline, people involved and a description of what already exists.

02Use the smallest copy that helps decide the next step.

Working copy

A page, screenshot, redacted working copy or specific data point can be enough before execution begins.

03Request the sensitive or original document when the real provider or recipient needs it.

Execution copy / original

The purpose, version and intended recipient should be clear before an original starts moving.

04Know what left the file and what came back.

Handoff + record

Keep the final executed/authenticated/translated package, delivery evidence and completion record needed for later proof.

Useful file log

Five fields beat a folder named “final-final-2”.

  • Document: what this file actually is.
  • Version: draft / signed / notarized / apostilled / translated / final.
  • Purpose: what fact or action it serves.
  • Owner: who currently controls the next action.
  • Next recipient: who must accept, file or rely on it.
Never send as routine intake

Credentials are not documents.

  • Bank passwords, one-time codes or full online-banking credentials.
  • Email or social-account passwords.
  • Crypto private keys, seed phrases or recovery codes.
  • A whole cloud drive “just in case”.
  • Unrequested original passports or irreplaceable originals.
First contact

What is safe to start with?

  • Your location and the location of the matter
  • The result you need in plain language
  • Who is already involved
  • Any deadline
  • A description of documents already available
Before sharing sensitive files

Confirm the purpose and recipient.

The appropriate transfer method and retention obligations can depend on the provider handling the step, the nature of the document and applicable professional or legal requirements. Those details should be confirmed for the actual file rather than replaced by a generic website promise.

Privacy notice →
Start without the document dump

Tell us what needs to happen.
We’ll ask for what matters next.

Start a Case →