Trust · Uploaded data
What happens to a file we upload?
Uploads are bounded in size and number, stored under the organisation's own prefix, and read only by a sandboxed extractor. Some things are not done, and they are listed here too.
No certification, audit or independent assessment is held. Each statement below shows how sure the project is of it.
What exists, and how sure we are
- Tested locallyAn upload is bounded by size and count, stored under the organisation's own prefix with opaque keys, and read by a bounded sandboxed extractor.Recorded in the data access assessment.
- Tested locallyDuplicate files are detected, and deleting a file respects a legal hold.Recorded in the data access assessment.
- Reviewed in codeThe file type and size are checked before an upload link is issued, and checked again when the upload finishes.Recorded in the security assurance record.
- Tested locallyNo download link is issued to a browser for customer media: the bytes pass through routes that check who is asking.Recorded in the security assurance record.
- Not in placeScanned pages are not read: there is no optical character recognition.Recorded in the data access assessment.
- Not in placeUploads are not scanned for malware.Recorded in the security assurance record.
- Needs checking on a live systemThat the storage bucket is private, with credentials limited to it, depends on the cloud account's configuration and has to be checked there.Recorded in the security assurance record.
See it in an example
Simulation. A scripted example on fictional data. The wording is scripted and no model is called; the figures are computed from what you decide, and a person’s approval covers exactly what you decided.
Review an upload batch before it is read
- What happened
- The records team at Calder Housing (fictional) has dropped a batch of nine files into AutoDiscover, and the platform's own checks have flagged some of them.
- The question
- Which files should be left out of the batch, and which can proceed? Asked by: Records manager at a customer (fictional).
Review an upload batch before it is readEach flagged file has a reason. Mark it to leave out, or to let it proceed; the number of pages that would be read is recomputed from your decisions.Open
Each flagged file has a reason. Mark it to leave out, or to let it proceed; the number of pages that would be read is recomputed from your decisions.
Review each flagged record: confirm it or dismiss it. The totals and the answer below follow your decisions.
File Type The platform's check Pages that would be read Finding Decision Tenancy policy.docx Word document Readable text 24 Matched None needed Repairs log 2025.xlsx Spreadsheet Readable text 12 Matched None needed Scanned lease bundle.pdf PDF Scanned pages, no text layer 86 A scan with no text layer: the platform reads no scanned pages Tenant complaints.csv CSV Readable text 40 Matched None needed Policy v3 copy.docx Word document Identical to another file 24 Identical to a file already in the batch Board minutes.pdf PDF Marked restricted by the customer 18 Marked restricted by the customer: whether it may be read is the customer's decision Contractor invoice.exe Program file Type not allowed 1 A program file: the type is not allowed and the upload is refused Estates map.png Image An image 4 An image: no text is read from it Case file 114.docx Word document Looks like a personal record 7 Looks like a personal record: confirm the customer has a reason to include it - Flagged
- 6 of 9 · 140
- Leave out
- 0 · 0
- Let it proceed
- 0 · 0
- Undecided
- 6 · 140
6 of 9 files were flagged; you left out 0 (0 pages) and let 0 proceed.
The platform checks type, size and duplicates itself and reads only a text layer, never a scan [S1]. Whether a restricted or personal file belongs in the batch is the customer's decision, recorded here before anything is read [S2].
Malware scanning is not done [S3]: uploads are limited by type and size, read only in a bounded sandbox and never executed. 6 flagged file(s) are still undecided.
Relies on: S1 · Upload batch report from the platform's checks (fictional)S2 · The records team's upload instruction (fictional)S3 · The platform's stated upload limits
The customer's records manager decides. Approving records which files may be read from this batch. It does not read any file itself, and files can be deleted later unless a legal hold applies.
Not ready. 6 flagged files are still undecided. Confirm or dismiss each one first.
Not done here. It does not scan files for malware, read scanned pages, or decide that a personal record may be included: the first two are not done, and the last is the customer's decision.
What a reviewer can have, and what not yet
- We can hand overThe upload limits, the list of file types that are read, and the tests of tenant isolation and of the extractor's bounds.
- We cannot yetMalware scanning, reading of scanned pages, and proof of any of this on a deployed environment.
The capabilities behind this
- AutoDiscover from a folder you approveNobody has time to organise years of files before they can benefit from any tool.
- The ways your information can reach the platformOrganisations differ in what they will share, with whom, and how.
The other nine
- Customer-controlled accessAccess by organisation, role and location, decided on the server, and what stops when it is withdrawn.
- Read-only database connectionsWhat a read-only connection proves before every use, what it cannot do, and what a customer's administrator should check first.
- AI provider disclosuresWhich features can send content outside the platform, what they may send, and what has not been established.
- Encryption and access controlsWhat protects sign-in, sessions and secrets, and the controls that only a live inspection can settle.
- Audit evidenceA tamper-evident decision record, what it proves, and what it cannot.
- Human approvalsWhat an assistant may draft or propose, what it refuses, and how a person's decision is recorded.
- Data retention and deletionWhat can be deleted now, what must wait, what is kept by design, and what is not finished.
- Customer-hosted and dedicated deploymentUpload, read-only connection, natural-language questions, a customer-hosted connector and a dedicated environment: what exists.
- Pilot security requirementsThe twenty-item gate, what it counts, and what is open.