Security and trust
Your contracts stay in your house.
ContractSense is installed in your own environment. Contract data is stored only there. The few hosted services we run reach your data only through a connector on your side that polls outward, so you never open an inbound port.
Hosting model
Who runs what.
| Component | Where it runs | What it holds |
|---|---|---|
| Web app, lifecycle API, intelligence service and workers | Your environment | All contract records, versions, files, search indexes and audit trail |
| Customer connector | Your network | Nothing stored. Runs fixed read operations with the requesting user's permissions |
| Packs server | Hosted by Ninth Quadrant | Industry packs (clauses, templates, prompts, skills) and the usage and cost ledger |
| AI model providers | The provider you choose | Content in transit for a single call. Per-organisation keys and model choice |
The connector
Outbound only. Fail closed.
When a hosted service needs to read a contract, it never connects into your network. Instead it leaves a job, and your connector collects it.
Request
A hosted service asks for a contract read through the packs gateway.
Check
The gateway checks the token and scopes, logs the usage and queues a job for your tenant.
Collect
Your connector polls outward over HTTPS, claims the job and runs a fixed operation with that user's permissions.
Return
The result returns by the same route. If no connector has polled for two minutes, the call fails immediately.
Design rules
Built in, not bolted on.
The AI never writes final state
Every AI draft or edit becomes a new, immutable version with visible change tags. A person decides what is kept.
Playbook first
Counter-proposals come from your own playbook before any model suggestion. Reviews pair AI verdicts with deterministic phrase rules.
AI reads, rules decide
AI extracts terms into structured data. A deterministic, non-AI rules engine does every calculation, so findings can be reproduced.
Traceable by design
Every change maps to a version, a user and a reason. The audit trail is hash-chained and signed PDFs are sealed.
Your data stays with you
The full platform runs in your environment. A connector on your side polls outward, so you open no inbound port.
Content over code
New industries arrive as versioned packs of clauses, templates, prompts and skills, not as custom code.
Controls
What protects your data today.
- Tenant isolation. Every query is scoped to your organisation and every route has a role check.
- Roles and per-contract access. People see only the contracts they are allowed to.
- PII redaction. Personal data can be redacted before text leaves the trust zone.
- AI spend caps. Usage is reserved before each AI call and fails closed when a budget is reached.
- Hash-chained audit trail. Tamper-evident and independently verifiable.
- Sealed signatures. Executed PDFs are PAdES-sealed with a certificate.
- Private by default. Only the edge proxy is public. Everything else sits on a private network.
- Strict start-up checks. The platform refuses to start in production if signing secrets are missing or weak.
On the roadmap: single sign-on, multi-factor authentication and platform-level encryption at rest. Ask us for the current status and timeline.
Deployment
Two ways to install.
Single server
- One-command installer writes configuration
- Automatic TLS certificates at the edge
- Bundled database, cache, object storage and PDF services
- Scripted backup and restore
Your Kubernetes
- Uses your ingress, secret store and backup tooling
- Connects to your own database, cache and object storage
- Stateless services scale horizontally
- Workers scale by adding queue consumers
Talk to us about your security requirements.
Run a proof of concept on three to five of your highest-value contracts. Measurable findings in eight weeks, on your data, with read-only access.