Symentrio

Trust & data

Useful evidence, within a clear boundary.

What is collected, why, and who can see it: agreed before any data flows.

Pre-launch. Demo figures are synthetic.Capability status

Intended data boundary

Design commitment

Standard data contract · Locally processed, allow-listed metadata

Approved metadata

Crosses the line

  • Usage counters, model, and timestamps
  • Minimum approved identity mappings
  • Repository, commit, and PR identifiers
  • Delivery states and work relationships
  • Device health and collection coverage

Excluded from the standard contract

Stays out

  • Prompts, responses, and reasoning
  • Source text and raw diffs
  • Tool arguments and outputs
  • Native transcripts and databases
  • Provider credentials and configuration files

Metadata can still be sensitive. Repository identities, work timestamps, and spending require appropriate access, retention, and employee transparency.

Our direction

Deliberately limited collection.

Symentrio is built around locally processed, allow-listed metadata. Prompts, responses, source text and raw diffs are excluded from the standard contract.

These are design commitments, verified with you before a pilot. This page is not a certification or compliance claim.

People need context, too

Reports about teams, not leaderboards.

Developers can see their own records, add context and request corrections. Individual drill-down needs explicit permission.

  1. 01

    Collect with a purpose

    Fields, repositories and sources are agreed before data flows.

  2. 02

    Keep access explicit

    Who can see named evidence is a decision, not a default.

  3. 03

    Make the limits inspectable

    Payloads, coverage, retention and deletion are open to review.

Before a pilot

Straight answers.

Is Symentrio SOC 2 certified?

No, and we don’t claim to be. Certification, hosting and operational requirements are discussed directly during qualification, with current evidence provided for review.

Can security review what is collected?

Yes. The pilot process includes the field inventory, sample outbound payloads, a data-flow diagram and permission requirements. Shipped behavior is verified before customer data flows.

What about retention and deletion?

Retention, export and deletion are part of the pilot review. The intended policy minimizes detailed evidence retention and excludes raw content. Exact terms are confirmed for each engagement.

Symentrio

See the work behind
your AI spend.

Start with one team and the coding tools your developers already use.

Talk to us

A scoped pilot: usage, costs and delivery evidence.