TruePrimary

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.

Trust checkpointsAll gates required
  1. 01

    Brief filed

    Suitability, scope, and restricted subjects screened before scheduling

  2. 02

    Routing

    Conflicts cleared by partner; any hold surfaced with a reason

  3. 03

    Shortlist approved

    Boundaries acknowledged in writing by buyer before sourcing closes

  4. 04

    Interaction

    Consent recorded; expert briefed 36 hours ahead

  5. 05

    Transcript review

    Expert reviews and may redact before library indexing

  6. 06

    Library

    Permissioned access, access logged, AI stays in bounds

Every gate explicitAccess loggedReviewable end to end

On this page

  1. 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, and any period in which they may hold material non-public information, such as an earnings blackout window. They acknowledge the scope before the call is scheduled.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 07

    What your compliance team can require.

    Each item below is already part of how an engagement runs. Put it in the brief and it is held on every routing.

    1. 01Named-company exclusions written into the brief and applied on every routing.
    2. 02Buyer sign-off on the shortlist, with boundaries acknowledged in writing before sourcing closes.
    3. 03Expert scope acknowledgement recorded before each call.
    4. 04Recording with the expert's written consent, given before scheduling and restated at the start of the call.
    5. 05Retention of transcript summaries to your team's documented rules.
    6. 06Handling terms documented in writing at onboarding, including where the engagement letter provides for True Primary to act as processor on your behalf.

Have a compliance question?

Data-residency requirements, audit bindings, or sector NDAs. We would rather hear them before onboarding than after.

Contact compliance