Free cookie consent management tool by TermsFeed Update cookies preferences
IntelCS . MENU Request a demo
Compliance Manager How it works HaloRT Industries Security Company Investors Contact Request a demo
Security & infrastructure

Nothing leaves. There is no third party in the path.

The whole pipeline — ingest, redaction, repair, review, retrieval, generation — runs on infrastructure IntelCS owns and operates, on self-hosted models in an environment dedicated to your organisation. Your case material is processed by us and by no one else: no commercial AI provider ever receives it, holds it, or trains on it.

HOSTING MODEL

A single-tenant environment on infrastructure IntelCS owns and administers, with self-hosted models. Nothing is subcontracted to a commercial AI API, so the list of parties that can see your case data is one name long.

DATA RESIDENCY

Case material is stored and processed in the jurisdiction you nominate at contract, and stays there. Because models run inside our own estate, residency is a deployment fact rather than a provider's regional endpoint policy.

PII HANDLING

Redaction runs at ingest, before review. Entity resolution is PII-aware: identifiers can be matched without being surfaced in outputs or logs.

PER-CASE ISOLATION

Each case is its own container. No cross-case retrieval, so one client's material cannot inform another's review.

AUDITABILITY

Runs are recorded with their inputs, rule-set version, and outputs. A review can be reproduced and compared against a later run of the same bundle.

DATA LIFECYCLE

Bundles are transferred over encrypted channels, retained only for the agreed review and retention window, then deleted on a schedule you set — with deletion evidenced. Nothing is used to train models.

ACCESS CONTROL

Named-individual access on the IntelCS side, scoped to the engagement, logged per action, and revoked on completion. Your own users authenticate through SSO with role-based permissions your administrators set.

INTEGRATION PATH

Document sources and case systems connect over standard interfaces; outputs are structured, so reports land in the systems your team already use rather than in another portal.

For security reviewers

A technical one-pager covering our hosting topology, data flows, transfer and retention model, model hosting, and logging is available for procurement and security review — along with the sub-processor position, which is that there are none for inference.

Talk to our team