Built for serious technical work.
Our work often involves proprietary ideas, sensitive workflows, internal systems, or strategic technology plans. We handle engagements with appropriate discretion, documentation, and confidentiality controls. We treat confidentiality as a baseline for serious research — not a marketing feature.
How serious technical work is handled.
Appropriate discretion
Our engagements often involve proprietary ideas, sensitive workflows, or strategic technology plans. We sign NDAs when required and handle all client material with professional discretion as a baseline, not a feature.
Controlled access
Project materials live in a per-engagement workspace with named access only. We do not pool data across clients or use one engagement's outputs to inform another's.
Secure development practices
Code is developed in encrypted environments with current secret-handling, dependency review, and access logging. Client-controlled environments are supported when an engagement requires them.
Private documentation
Written artifacts are produced for the client. They are not used as marketing material, case studies, or training inputs without written approval.
Client-owned outputs
Where the engagement defines it, all deliverables — including source code, models, evaluation harnesses, and documentation — are owned by the client at handoff.
No public disclosure by default
We do not announce, list, or imply the existence of any engagement without written approval. Engagements that need to remain private remain so indefinitely.
From first contact to handoff — how the engagement is structured.
Initial contact
Inquiries can be deliberately high-level. You don't need to disclose anything sensitive before professional terms are in place.
NDA where appropriate
When an engagement requires it, we sign either party's NDA before technical specifics are discussed. Our standard template covers mutual confidentiality, residual obligations, and a clear definition of confidential information.
Scoped discussion
Once terms are in place, we discuss the actual problem in technical detail, including data, environment, and operational constraints.
Written scope
The engagement scope, deliverables, ownership, and confidentiality terms are documented in a written agreement before work begins.
Engagement execution
Work is performed in an isolated workspace. Communication channels and storage locations are explicitly named in the scope document.
Closeout
At handoff, materials are transferred to the client per the agreed terms, and access to working environments is closed unless retention is explicitly required.
Things GET will not do, regardless of contract value.
A professional baseline only works if some lines are non-negotiable. The list below applies to every engagement.
- ✕We do not retain copies of client data beyond the engagement without explicit written instruction.
- ✕We do not use client materials as training data or as input to internal models.
- ✕We do not name clients in proposals, talks, or marketing without written approval.
- ✕We do not transfer engagement details between unrelated client conversations.
- ✕We do not knowingly take engagements that would create a substantive conflict of interest with an active client.
Have a technical challenge worth investigating?
Bring us the problem. We will help determine what is possible, what is practical, and what should be built next.
Response within two business days · NDAs available when required