Privacy isn’t a policy pageIt’s the architectureIt’s our number one priority

aptAIvisor sits between competing buyers and sellers by design. Every part of the platform — where your contracts live, who can open them, and how a benchmark gets built — is designed around a core principle: keep it as your data isolated within your organization’s environment.

Buyer & seller data

Buyer & seller data

Cryptographically segregated, per tenant

A benchmark appears

A benchmark appears

Once 5 or more companies have contributed

Your contracts & profile

Your contracts & profile

Designed to keep your contracts and profile data separate from shared-model training.

Encryption

Encryption

AES-256 via AWS KMS — at rest & in transit

How a data point becomes a benchmark

A negotiated price is sensitive. A percentile band computed across five or more companies isn’t. Everything in between is where the design work happens.

Your Tenant

Contracts & deal termsEncrypted, isolated

↓ With consent

Anonymization Floor

Strip company & contract IDsGeneralize deal size & dateOnce 5 or more companies have contributed

↓ Anonymized Fields

Aggregate Pool

Anonymized fieldsCohort-level statisticsNo line items are included in the aggregated pool

↓ As a range

Benchmark

Shown to the other side of the deal

The Anonymization Floor is designed to send only structured, anonymized fields to the aggregate pool, rather than raw contracts, company names, or individual deal values.

Eight controls, not an afterthought

Each of these is a real component in the platform, not a claim layered on top of it afterward.

ControlWhat it does
Tenant data segregationEvery buyer and seller organization gets its own encrypted store. A requests are scoped to your organization, with database-level controls designed to prevent unauthorized access to or modification of another tenant’s data.
Encryption everywhereContracts, deal records, and generated documents are encrypted at rest and in transit using AWS Key Management Service, with keys scoped and rotated independently of application code.
Role-based accessAccount Manager, Deal Desk, Finance, Legal, and Executive roles each see only what their function needs. Access is set by your admins, not by default.
The anonymization floorBefore any deal term can inform a benchmark, it passes through four gates: identifying fields are stripped, sensitive values are generalized into bands, a human reviews it, and it is held back until at least five independent companies have contributed a comparable deal.
Consent-gated contributionData enters the benchmark pool only with explicit adminstrator consent. Each deal is opted in explicitly, and that consent can be scoped or withdrawn going forward.
Private profile embeddingsThe preferences your team teaches the assistant live in your own tenant's namespace. They personalize your suggestions and are designed to remain within your tenant rather than being pooled or used for shared-model training.
Multi-model oversightAnswers are checked across more than one AI provider and carry a confidence score. Low-confidence answers ask follow-up questions instead of guessing, and every output can be overridden by a human.
Full audit trailLogins, uploads, AI requests, and approvals are logged and reviewable by your admins — and the log itself cannot be edited, only read.

What design partners
ask us

Individual deal terms are designed to remain restricted to your tenant. Benchmarks are intended to be generated only after at least five independent companies have contributed comparable, anonymized deals. The resulting data is presented as a range rather than an individual deal record.

Want the long-form version

Our full technical specification — architecture, the anonymization algorithm, and data-flow diagrams — is available under NDA for procurement and security review.