ORNX.PRO
ORNX.PRO / CONFIDENTIALITY

Confidentiality starts before the first file.

Trust is built through clear boundaries: what we accept, who may see it, where it is kept and when its use ends.

Written-onlyHuman reviewClear scope
Information confidentiality
Scope · trust · delivery
THE PRINCIPLE

Send only what is needed for the question, and agree a safer channel before sharing sensitive material.

Email or Telegram are useful for first contact, but no channel should be treated as automatically safe for private keys, seed phrases, passwords or information that grants access to assets.

HOW INFORMATION IS HANDLEDA practical baseline for minimisation, separation and controlled access.
  1. Minimisation. We start with context and do not ask for more data than the agreed result requires.
  2. Separation. Materials from different projects are kept separate in working notes, files and outputs.
  3. Limited access. Access is given only to a person or contractor who needs it for a defined stage and is bound by confidentiality duties.
  4. Written record. Scope, sources, assumptions and decisions are kept so the client can understand what was done.
  5. AI and external tools. Supporting tools may assist research operations; confidential materials are not sent to external systems by default. Material processing is agreed in writing or excluded.
  6. Retention. Working copies are closed or deleted after the agreed stage, except material that must be kept for a contract, law, accounting or dispute requirement.
  7. Exceptions. Disclosure occurs only with written client consent or when required by law, court, regulator or necessary to prevent immediate harm.
WORKING CHOICES

Confidentiality is not an absolute guarantee

01

What you may send

The decision context, public links, redacted data, financial assumptions, timing and the required output format.

Read the principle →
02

What not to send

Private keys, seed phrases, passwords, API secrets, recovery phrases or documents ORNX.PRO should not access.

Read the principle →
03

How to strengthen protection

Use an agreed secure channel, encrypt archives, send the password separately and agree the confidentiality level first.

Read the principle →
PROJECT IDENTITY

Confidentiality is not an absolute guarantee

We use reasonable organisational and technical measures, but email, Telegram, cloud systems and the internet cannot provide absolute protection. For higher-risk material, agree a separate channel, NDA or handling restriction first.

ORNX.PRO is presented on this site as an independent project. This page describes a working practice and does not replace tailored legal advice or a confidentiality agreement.

Editorial basis: 20 public confidentiality, privacy and client-data protection references.

Confidentiality starts before the first file.
Confidentiality starts before the first file.
Evidence trail

This page separates the primary signal, independent checking and the limitation that should remain visible.

Source register

Detailed citations and source dates are confirmed in the written research brief.

Limitation

A decision remains conditional where evidence is incomplete or time-sensitive.

CHOOSE YOUR NEXT STEPThe four central routes through the ORNX.PRO method

A CLEAR WAY TO WORK TOGETHERFour pages that define a clear, safe working relationship