Trust and compliance
Trust sits inside the workflow.
Built for teams that need speed without getting casual about boundaries. Suitability, scope, records, permissions, and auditability are part of how the work runs.
Checkpoints
Every gate explicit, brief to library.
Compliance posture is a series of explicit gates, not a paragraph in the footer. Each gate produces a small artefact you can audit later.
- 01
Brief filed
Suitability, scope, and restricted subjects screened before scheduling
- 02
Routing
Conflicts cleared by partner; any hold surfaced with a reason
- 03
Shortlist approved
Boundaries acknowledged in writing by buyer before sourcing closes
- 04
Interaction
Consent recorded; expert briefed 36 hours ahead
- 05
Transcript review
Expert reviews and may redact before library indexing
- 06
Library
Permissioned access, access logged, AI stays in bounds
- 01
Scope and restricted subjects.
Every engagement runs against a brief screened for fit, conflicts, and restricted subjects. Experts declare what they cannot speak to — current employer, named clients, MNPI-adjacent windows — and acknowledge the scope before the call is scheduled.
- 02
Consent and recording.
Recording is opt-in by the expert on every call. Consent terms are presented before scheduling, restated at the start of the call, and revocable for a defined window after.
- 03
Source trail.
Every claim in a synthesis links to the expert, the timestamp, and the caveat. There is no anonymised aggregate that has dropped its source.
- 04
Review and escalation.
Disputes (content, scope, or compensation) go to a named person at True Primary, not a ticket queue. We commit to a first response inside two working days and a substantive reply inside five.
- 05
Permissions, access, and security.
Briefs, transcript summaries, and library entries are visible only to the right team members. Internal access is least-privilege. Access to every transcript is logged and reviewable.
- 06
AI stays in bounds.
AI is workflow support, not the evidence source. It can help structure a brief, route sources, support summaries, and retrieve prior evidence. It does not widen what is permissible to say, store, surface, or share.
Have a compliance question?
Data-residency requirements, audit bindings, or sector NDAs. We would rather hear them before onboarding than after.