Skip to main content

Support

Support and safe document handling

Reviewed public guidance for protecting identity, financial records, and certificate information until an authenticated case-support channel is available.

Case access
Not available publicly
Secret factors
Never disclose
Current help
Reviewed public guidance
S / 14Evidence over claims
Shielded customer session with identity and access checkpoints
Verified channel · Private factors · Protected support

Support availability

No case access is implied without a secure support path.

Authenticated case support and a verified public support channel are not active yet. This page can guide safe next steps, but it cannot inspect an account, request, payment, or document.

Public help

Start with reviewed, non-sensitive information

These routes explain the product without requesting private case material.

Protect yourself

Financial support must be safe before it is convenient

Urgency is not a reason to move identity or financial records into an unverified conversation.

Do not share sensitive data publicly

Never send identity documents, bank records, audited statements, payment secrets, or signed links through a public message.

Use only verified channels

A future support interaction should identify its purpose, recipient, case reference, access scope, and audit trail.

Keep authentication factors private

A support agent should not ask for an OTP, password, or full secret to diagnose an issue.

Secure-support contract

A secure interaction should prove its context

Before sharing anything, confirm that all five checks are present.
  1. 01

    Purpose

    Why support needs the information.

  2. 02

    Recipient

    Who is authorized to receive it.

  3. 03

    Reference

    Which exact case is being discussed.

  4. 04

    Scope

    Which minimum records are relevant.

  5. 05

    Audit

    How the interaction is recorded.

Current help

Use the reviewed resource library.

Browse public guidance