§ TRUST CENTER
Review the deployment with your counsel and technical team.
Security reviewers usually want to know where data runs, who can access it, which controls are in place, and what records they can review.
The level is yours to set. Your counsel decides what obligations apply to your organization.
ASG does not give legal advice. Customers remain responsible for their professional, legal and compliance decisions and for conclusions drawn from outputs.
We label every claim. Planned: not yet verified. On request: scoped and confirmed for your deployment. Available: has a verified release record.
§ 01 — THE REVIEWER KIT
One packet for each person who reviews the decision.
FOR YOUR COUNSEL
Data-handling disclosure
Draft · owner review pending
Deployment mode, subprocessors, incident-notice terms, data return and deletion, audit rights.
Release pending owner review · Availability and scope confirmed on request.
Ask about this review material →See packet contents
Draft outline
- What this packet is
- Who you contract with
- The data bolde. handles
- Your security level
- Subprocessors
- Microsoft Entra apps and the permissions they request
- ASG personnel access
- Training and model use
- Model origin
- Incident notice
- Data return, deletion and credentials at the end of the term
- Audit rights
- Controls in place and controls forthcoming
- Security program
- Liability
- Who decides what
- Contacts
FOR YOUR BOARD OR INVESTORS
AI risk brief
Draft · owner review pending
The questions boards, investors and LPs ask about AI, answered in plain language with the record behind each one.
Release pending owner review · Availability and scope confirmed on request.
Ask about this review material →See packet contents
Draft outline
- Who is ASG, and what is bolde.?
- Where does our data go, and who can see it?
- Will our data train someone else's model?
- How do we know an answer is right?
- What can the agents do on their own?
- What happens if something goes wrong?
- What happens if we leave?
- Who owns what is built?
- What does it cost, and can the price go up?
- How long until it is running?
- Who is accountable?
- Which outside standards apply?
- What stays with your firm?
FOR YOUR IT TEAM OR PROVIDER
Connection spec
Draft · owner review pending
Identity, network and access steps for the environment agreed in your deployment. Hosting options are confirmed with your team.
Release pending owner review · Availability and scope confirmed on request.
Ask about this review material →See packet contents
Draft outline
- Who does what
- Before you start: checklist by level
- Identity
- Network, by level
- Hosting, by level
- Connecting bolde. to your systems
- ASG access
- Logging and audit
- Keys and secrets
- Moving up the security dial
- Go-live checks
- Offboarding
FOR YOUR CFO
Commercial terms summary
Draft · counsel review pending
How the order form sets out the subscription and implementation fees for your deployment. Prices are provided in the order form, not on this site.
Release pending owner review · Availability and scope confirmed on request.
Ask about this review material →
§ 02 — HARD QUESTIONS
The questions reviewers ask, answered plainly.
- Which customers can we speak to?
None we can name publicly yet.
- What happens to our data if we leave?
Data return terms are written into your order form. Planned
About this claim
- Owner
- Counsel
- Status
- Planned
- Required evidence
- An adopted data-return clause specifying the return format and period.
Not confirmed for your deployment.
- Who can see our data?
Personnel access, hosting and subprocessors are set for each deployment. On request — not yet verified for this site. See deployment choices →
- Do you hold a security attestation or certification?
Not yet.
§ 03 — GOVERNANCE
The governance questions we answer for each deployment.
- GOVERN
- Named owner and approval path for each deployed workflow.
- MAP
- The data each workflow touches and the rule that governs it.
- MEASURE
- Review question: which answers must link to their source records, and which of your own examples will check accuracy?
- MANAGE
- Review question: which outputs require a person's approval before action?
FRAMEWORK
Govern, map, measure, manage: we map our review questions to the four functions of the NIST AI Risk Management Framework. This mapping is not a certification or attestation.
§ 04 — COMMITMENTS
Commitments as stated on this site.
We listen to one workflow and one constraint and say if the platform is not the right fit.
How we work →No documents before a mutual NDA.
Briefing →No fee. No order form at the Briefing.
Briefing →Talk to Jason or Manbir.
Briefing →
The ASG publication keeps usage measurement off unless you turn it on.
§ 05 — VERIFIED EVIDENCE
Verified evidence.
0 of 18 claims verified.
None yet. Every claim below is pending owner verification.
§ 06 — RECEIPTS
Statements under review and the evidence each needs.
Each row shows the statement under review, its status, the evidence it requires, any evidence verified, the owner and the date checked. A missing check date means the owner has not recorded a verification. Compare wording across sites →
Your data
| Statement under review | Status | Required evidence | Verified evidence | Checked | Owner | Appears on | Cite |
|---|---|---|---|---|---|---|---|
| Not a current verified commitment. Your data is yours. You get it back when you leave. | Planned | An adopted data-return clause specifying the return format and period. | None recorded | Not checked | Counsel | Trust Center | #claim-05 |
| Not a current verified commitment. Each client's tuned model is never pooled with another's and never trains anyone else's. | Planned | A tenant-isolation design record and the corresponding contract term. | None recorded | Not checked | CTO | Trust Center only | #claim-07 |
Platform
| Statement under review | Status | Required evidence | Verified evidence | Checked | Owner | Appears on | Cite |
|---|---|---|---|---|---|---|---|
| Not a current verified commitment. Every answer shows its source, and every action is on the record. | Planned | A product release record showing source attribution and action logging. | None recorded | Not checked | CTO | Trust Center only | #claim-11 |
| Not a current verified commitment. The platform gets better every release, and every deployment gets those releases. | Planned | A release record showing release cadence and rollout to deployed tenants. | None recorded | Not checked | CTO | Trust Center only | #claim-12 |
| Not a current verified commitment. A named Deployment Engineer connects the platform to each of your systems and owns that connection after go-live. | Planned | An adopted Implementation SOW term naming an owner for each connection and carrying that responsibility into the subscription. | None recorded | Not checked | CTO | Trust Center only | #claim-19 |
| Not a current verified commitment. Living documents, slides and spreadsheets keep their figures and citations current as approved sources change, without overwriting your edits. | Planned | A product release record for bolde. Evergreen. bolde.ai/features lists Evergreen as a planned release target within one month (snapshot 2026-10-21). | None recorded | Not checked | CTO | Trust Center only | #claim-20 |
| A shared workspace brings people, agents and work together; owners set view or edit access, and an agent suggestion becomes an edit only when a person approves it. | On request | A dated release or deployment record for bolde. Space. bolde.ai/features lists Space as Phase I, in progress or shipping now (snapshot 2026-10-21); no record has been verified for this site. | None recorded | Not checked | CTO | Trust Center only | #claim-21 |
Deployment
| Statement under review | Status | Required evidence | Verified evidence | Checked | Owner | Appears on | Cite |
|---|---|---|---|---|---|---|---|
| Not a current verified commitment. Your security level is written into your contract. | Planned | An adopted Security Level Schedule, one for each level of the dial. | None recorded | Not checked | CTO | Field Note 01 | #claim-04 |
| Not a current verified commitment. We build on AWS, Azure, Google Cloud, on-premises and government cloud. | Planned | A reference deployment for each named environment. | None recorded | Not checked | CTO | Trust Center only | #claim-09 |
| Not a current verified commitment. The platform works with public models, private models or both. | Planned | A product release record and model connection list. | None recorded | Not checked | CTO | Trust Center only | #claim-10 |
| Not a current verified commitment. The same agents and controls run at every level of the dial, so you move up it without rebuilding your agents. | Planned | A release record covering agents and controls across security levels. | None recorded | Not checked | CTO | Trust Center only | #claim-13 |
Company
| Statement under review | Status | Required evidence | Verified evidence | Checked | Owner | Appears on | Cite |
|---|---|---|---|---|---|---|---|
| Not a current verified commitment. Your subscription is locked at the rung you join. | Planned | An adopted bolde. Order Form with the subscription term (template §2.2). The available template is a draft that requires counsel review. | None recorded | Not checked | Counsel | Trust Center only | #claim-01 |
| Not a current verified commitment. One agreement covers configuration (Phase 0 of your bolde. deployment), the Build and your subscription. Each phase has a fixed fee, set before work starts. | Planned | An adopted bolde. Order Form and Implementation SOW describing the subscription and implementation phases. The available templates are drafts that require counsel review. | None recorded | Not checked | Counsel | Home; How we work | #claim-02 |
| Not a current verified commitment. We price phases, not hours. | Planned | An adopted bolde. Order Form showing a monthly subscription and fixed implementation fees rather than hourly pricing. The available template is a draft that requires counsel review. | None recorded | Not checked | Counsel | Trust Center only | #claim-03 |
| Not a current verified commitment. The people named on this site hold the backgrounds we state. | Planned | Written confirmation from each named person of their own published background line. | None recorded | Not checked | CEO | Trust Center only | #claim-15 |
Market
| Statement under review | Status | Required evidence | Verified evidence | Checked | Owner | Appears on | Cite |
|---|---|---|---|---|---|---|---|
| Not a current verified commitment. 71% of financial-services firms plan to deploy AI agents within two years. | Planned | Deloitte, State of AI in Financial Services (2026); sample is financial-services firms already using AI. Deloitte also sells AI services. Source and bias note require owner verification. | None recorded | Not checked | CEO | Trust Center only | #claim-16 |
| Not a current verified commitment. ~23% have a mature model for governing AI agents. | Planned | Deloitte, State of AI in Financial Services (2026); sample is financial-services firms already using AI. Deloitte also sells AI services. Source and bias note require owner verification. | None recorded | Not checked | CEO | Trust Center only | #claim-17 |
| Not a current verified commitment. 24% of financial-services firms have moved 40% or more of AI experiments into production. | Planned | Deloitte, State of AI in Financial Services (2026), N=573; sample is financial-services firms already using AI. Deloitte also sells AI services. Source and bias note require owner verification. | None recorded | Not checked | CEO | Trust Center only | #claim-18 |
- #claim-06 · Retired
- #claim-08 · Retired
- #claim-14 · Retired
Stable claim IDs are permanent citation anchors. Retired IDs keep their anchor and are not reused. Market statistics are kept off the home page and require a source and bias note wherever used. The ledger holds 21 IDs.