Your bid intelligence stays yours.
Tender packs can contain pricing assumptions, methodologies, commercial positions, people data and years of institutional bid knowledge. Tender Intelligence is being designed around customer data isolation and customer control, not a shared pool of bid content.
One customer's competitive intelligence must never become another customer's advantage.
Customer workspaces are isolated from one another. Source material, requirements, evidence and historical bid knowledge remain within the relevant customer boundary, and are not intended to be used as another customer's workspace or AI context.
Permanent response projects and stored source files use tenant scoped boundaries. Application controls block cross tenant reads rather than relying on users to avoid the wrong folder.
Source files are stored only if you create a shared workspace. When a shared workspace is created, original source files are retained in workspace scoped Cloudflare object storage so the same tender record can be reopened and audited by authorised team members.
Private preview access is authenticated and workspace writes are permission controlled. Broader enterprise SSO and fine grained RBAC are part of the later enterprise security layer.
Source, export, reopen and deletion activity uses the existing audit trail, while material findings are kept linked to their underlying source wherever the documents allow it.
Retrieval and analysis are scoped to the active project or customer context. Customer bid history is intended to strengthen that customer's institutional intelligence, not another customer's.
Do not upload confidential or commercially sensitive tender material here. Production customer environments are provisioned separately and the enterprise controls below are roadmap commitments, not claims about this staging site.
A document uploaded to the free Tender Risk Scan is sent to our AI provider (OpenAI) to be read for that one scan and is not currently retained by Tender Intelligence afterwards. We do store the email address, company and tender title you provide, so we can follow up with the results. It is protected by Cloudflare Turnstile human verification and server side rate limits, not by account authentication.
What the customer should control
The long term product standard is simple: the customer owns its bid data and controls who can use it.
- People: who can enter the workspace and what role they have.
- Data: what tender packs, evidence, historical bids and institutional knowledge are retained.
- Access: which users can view, change, export or delete customer information.
- Lifecycle: retention periods, export and verified deletion when the customer leaves.
- AI context: customer information remains scoped to the relevant customer environment and is not exposed to competing TI customers.
Enterprise Data Control
For larger organisations, TI will move beyond logical workspace isolation to stronger customer specific deployment controls. These capabilities are deliberately positioned as later enterprise work and will not be represented as live until implemented and verified.
How findings stay traceable
Material findings, requirements, mandatory conditions, risks and evidence gaps, are linked back to the source document, section and page they were identified from wherever the source material makes that possible. Analysis results are independently checked before the workspace is presented for review.
Human accountability remains
Tender Intelligence does not replace legal, commercial, estimating, engineering, procurement or governance review. It organises and traces the work so the right people can make those decisions from the authoritative tender documents.