
The Conversational State Transition Model
A neurocognitive model of how conversation changes what becomes thinkable and actionable
Read the paperTrust & Security
Piloteer is built to improve team performance while protecting individual privacy, agency, security, and human judgment.

Why we built it
The promise of AI should not be to remove people from the equation. It should help us see each other more clearly, communicate better, make better decisions, and perform at a level that was harder to reach alone.
Piloteer was built around that belief. It gives people greater awareness in the moments that matter while keeping agency, privacy, and judgment where they belong: with people.
Trust by design
01 / Private
Piloteer is designed to give people private guidance and performance information that supports their own improvement.
02 / Aggregate
Organizational visibility is designed to show the broader patterns affecting team performance without turning private individual guidance into a management scorecard.
03 / Accountable
Piloteer supports judgment with evidence, context, confidence, and uncertainty. Accountability remains with people.
Clear by design
01 / User control
No hidden activation or background listening.
02 / Evidence before inference
Confidence, conflicting evidence, and what remains unknown stay visible. Low-evidence situations can result in no output rather than a forced interpretation.
03 / Human judgment
People remain accountable for the decisions that follow.
Enterprise trust
Direct answers
No.
Piloteer operates when the user activates it. Users can start, pause, and stop the system, and there is no hidden background listening.
No.
Individual guidance and scores stay private to the user. Leaders see aggregate team-level performance patterns rather than private individual feedback.
The Piloteer Console does not retain meeting audio or video recordings.
Audio and video may be processed to generate performance context, but the underlying Console meeting audio and video are not retained as recordings. If Piloteer Notetaker is used, it appears as a visible meeting participant and the recording behavior is clear.
Customer data does not train Piloteer’s shared AI models.
Piloteer uses approved customer context to deliver the product without using customer data to train shared models.
No.
Piloteer evaluates the Piloteer user. Other participants may provide context to the interaction, and how that context is represented can vary by product, but they are not individually evaluated or scored. When visual sensing is enabled, it applies only to the Piloteer user.
No. Piloteer does not rely on a single universal behavioral profile.
Piloteer can use the individual’s own baseline and authorized historical context to make guidance more contextual and reduce dependence on one fixed population-wide norm. This personalization occurs through contextual inference rather than training a new model on the user.
No.
Piloteer is built to improve performance and support human judgment. It does not autonomously make hiring, promotion, compensation, disciplinary, termination, or other consequential employment decisions.
Piloteer treats bias as a measurable system risk.
The system uses layered validation, evidence thresholds, contextual interpretation, controlled model changes, and human review rather than claiming that any AI system is inherently bias-free.
Piloteer supports enterprise security controls including SOC 2 Type II, encryption in transit and at rest, enterprise SSO, least-privilege access, audit logging, and enterprise deployment options.