Every document read. Every answer cited. Nothing leaves unencrypted.

Upload policies, contracts and audit reports once. Secani reads them, finds the passages that matter and drafts findings and vendor records for you to accept, each with the page it came from.

30 Minutes

Read once, use everywhere.

Documents become evidence, findings and vendor records without retyping.

01

Ask across documents

Put up to 20 questions to up to 500 documents and get a table: one row per document, one column per question, every cell cited.

Each answer is checked against the source text and links to its document version, page and passage.

02

Audit reports become tasks

Secani reads an audit report and proposes each finding with its source passage. A reviewer accepts it, and it becomes a task linked to that report version.

No AI output reaches the workspace until a person accepts it; the report version stays pinned.

03

Contracts fill the vendor record

Secani extracts term, notice period and data-processing clauses from a contract. You pick the vendor and accept; the vendor profile, contract and open checks are written for you.

Accepting writes the vendor profile, a contract record and five checks, with tasks for every check that is still open.

What stops being manual.

The reading, retyping and re-uploading around every document.

Reading 80 contracts to fill a comparison spreadsheet

One review table, every answer cited to its page

Typing audit findings into the task list

Findings proposed with their passage, accepted by a reviewer

Copying contract dates into the vendor record

Extracted, reviewed and written to the vendor profile

Uploading the same file again as evidence

A vault document becomes evidence without a second upload

Count the reading.

How many documents does your team read to answer a recurring question?

Hours per year spent reading

75

Your numbers, multiplied: documents × minutes. Nothing of ours goes into the result.

Read by AI, decided by you.

Every proposal waits for a person, and every file is encrypted on its own.

A key per document

Files are encrypted in 8 MiB chunks with AES-GCM under a key per document, wrapped by a KMS master key. A workspace can opt into its own key and have it destroyed verifiably.

Citations you can check

Search results and review table answers point to the document version, page and passage, and access is checked again for every hit.

Reviewers decide

Findings and contract data reach the workspace only after a reviewer accepts them. Unclear OCR pages go to review instead of being guessed.

Questions about Vault

Each document gets its own 256-bit key. The file is encrypted in 8 MiB chunks with AES-GCM, and the document key is wrapped by a KMS master key. Workspaces can use a dedicated KMS key.

Up to 500 MiB per file, up to 1,000 files per upload batch. Processing reads up to 500 pages per run.

No. Findings from audit reports and data from contracts are proposals. A reviewer corrects, accepts or rejects them before anything is written.

Yes. It becomes an evidence artifact without uploading it again, and that version is put under legal hold so the evidence cannot drift.

Stop reading the same documents twice.

Let Secani read them once and cite every answer.