Loading...
AES-256-GCM at rest with keyVersion rotation, TLS 1.2+ in transit, an immutable audit log, and every flag cross-linked to a specific regulatory provision across 19 international frameworks spanning G7, EU, GCC, and African markets. A Fortune-500 security questionnaire finishes in minutes, not weeks.
keyVersion stamp so keys can be rotated without bricking historical data.Every enterprise security questionnaire probes the same five things. This is how Decision Intel answers each one today, with code paths, not aspirations.
What a Fortune 500 vendor-risk register asks for once the technical posture passes review: issue date, auditor identity, observation window, and scope. Decision Intel's product-level Type I is targeted (not yet issued); each sub-processor's Type II report covers the surface that holds customer data, and we name the auditor + the verification path so a reviewer can confirm independently.
Every audit log entry is immutable, append-only, and timestamped at write. Entries are queryable via the AdminAuditLog UI inside the customer account and exportable as a single JSON bundle via the account-data export endpoint (Enterprise tier). The retention window starts at the entry write timestamp; expired entries are archived to cold storage for an additional 90 days before cryptographic destruction. When a customer leaves the platform, the active retention window survives the contract end-date so post-departure regulatory queries can still be answered.
A Fortune 500 vendor-risk register works in question→answer→verification triples and circles every gap in red. Below: the ten rows that recur on every SIG (Standardized Information Gathering), VSA (Vendor Security Assessment) and CAIQ (Cloud Security Alliance Consensus Assessment Initiative Questionnaire) that lands on a CSO or GC desk. Copy answers row-for-row into the questionnaire; each verification path resolves to a public trust portal or a contractual commitment in the pilot agreement.
Aviation Crew Resource Management crossed from "exercise" to compulsory practice in 1990 when the FAA Advanced Qualification Program made it the standard. Corporate M&A is at the same inflection — three structural conditions converging: a liability shift in motion (EU AI Act Article 14 enforceable August 2026 + Basel III Pillar 2 ICAAP live + SEC AI disclosure rulemaking), friction collapse unlocked (sub-cent per render via deepseek-v4-flash through the AI Gateway), and the status reframing of structured decision support from "false precision" to "elite operational hygiene." Decision Intel produces the Decision Provenance Record the August 2026 enforcement deadline calls for, today.
Human oversight + record-keeping mapped onto the DPR's hashed input + judge variance + meta-verdict trail.
Qualitative decision documentation requirement satisfied by the DPR — every flagged bias attaches a Basel III provision citation.
Model lineage + prompt fingerprint + judge variance documented per the DPR's methodology section.
Every DPR field maps onto the 11 internationally-recognised AI governance principles.
Buy the audit before the regulator forces it. The artefact is the same either way; the difference is whether your audit committee is staring at a clean DPR or scrambling to produce one mid-enforcement.
Evidentiary standard · Your EU AI Act Article 14 and Basel III Pillar 2 ICAAP audit trail is constructed on these fingerprints. Any change to the audit standard — methodology version, weight resolution, or scoring engine — produces a different fingerprint and is versioned and disclosed against the prior records. The continuity is the point: once an audit committee has built a multi-year reasoning-provenance trail on a consistent evidentiary standard, moving the same decisions to a different audit method is not a silent switch — it is a documented change of evidentiary standard a regulator can see across the record series. See the fingerprint construction (also bound contractually as Terms §10I + the DPA template).
Three regulatory waves are already in force or on the enforcement calendar. Each one asks for exactly the artifact the Decision Provenance Record produces. The reasoning behind a decision, the model lineage that shaped it, and the evidence that it was reviewed, not just generated. We built for this on purpose.
Positioning note for CSOs evaluating us: the Decision Provenance Record is the record your AI-augmented decision-making is supposed to produce anyway under these frameworks. We ship it on every audit so your procurement conversation starts at “here is the control” instead of “we’re working on it.”
Every row in an encrypted column carries an integer keyVersion stamp. Swapping keys is a four-step protocol with no big-bang migration, no data loss, no customer-visible pause.
scripts/rotate-encryption-key.ts. Resumable, batched, idempotent. Dry-run mode available.Every flag the pipeline surfaces carries a regulatory citation across G7, EU, GCC, and African markets. Your GC doesn't take the tool on faith. They walk into the audit committee meeting with the memo, the flags, and the framework sections attached.
What is available today across every plan, and what is unlocked on Enterprise.
The commitment isn't that incidents never happen. It's what you'll hear from us when one does, and in what timeframe.
The numbers a Fortune 500 security questionnaire opens with. Recovery objectives, backup cadence, and redundancy posture, sized against what the production-tier infrastructure SLA actually delivers, not what would sound nice.
The 16-year-old solo-founder continuity question, answered in the form a Fortune 500 GC or vendor-risk-register reviewer expects. Each provision is documented in the relevant pilot or subscription agreement; nothing here is aspirational.
The data-leak objection M&A and corp-dev professionals raise first. Maximum trial retention, one-click hard-purge, mutual NDA template, and the contractual no-training-on-customer-data commitment, packaged here so a procurement reader can quote the exact guarantee in their vendor-risk register.
The cohort-calibration moat (per-org Brier-scored recalibration, the answer to Cloverpop's data-advantage attack vector) requires outcome metadata across consenting organisations. Document content, persona names, and deal terms are NEVER part of the cohort signal. Below is the contractual ownership posture, mirrored in the DPA and every pilot agreement.
Documents auto-soft-delete at the end of your tier's window. A 30-day grace window applies before permanent purge: recoverable via support during the grace, irrecoverable after. Self-serve Delete is on every document detail page and on the post-upload reveal card.
Documents auto-soft-delete 30 days after upload. Recoverable via support during the grace window, then permanently purged.
Documents auto-soft-delete 90 days after upload. Same grace window, same support-recoverable path.
Quarter-after-quarter retention for team-level Decision Knowledge Graph. Auto-soft-delete at 365 days; same recoverable grace.
Default matches Strategy; per-Order-Form overrides for legal-hold, SEC, or Basel III obligations. Configurable in either direction.
Right-to-delete (GDPR Art. 17) requests are processed within 30 days. Send to privacy@decision-intel.com or use the in-app Delete button on any document.
Transparent processor list with each vendor's certification posture and hosting region. Updated in lock-step with our vendor agreements.
Responsible disclosure is a first-class contract with our users. Report vulnerabilities to security@decision-intel.com (first response within 48 hours, every time). For DPA requests, SOC 2 reports, or a security questionnaire response, reach the same inbox and reference your organisation name.