Trust Center

Trust Should Not Require Blind Faith.

The CCFE Group handles confidential construction information differently from public AI workflows. Our operating model is built around controlled project-document processing, limited access, human oversight, and defined information boundaries.

This page documents the operating environment rather than a marketing position. Statements about processing, infrastructure, access, and security are published only where CCFE can demonstrate them. It does not replace the Privacy Notice, the Terms and Conditions, or a project-specific agreement.

Customer data ownership

Clients retain ownership of the project information they provide, subject to applicable contracts and agreements.

Human oversight

Authorized human review remains part of the CCFE workflow. Final estimating, scope, risk, and bid decisions remain human.

Limited access

Project information is available only to authorized personnel, approved CCFE systems, and approved project workflows.

Transparent boundaries

Public website and administrative services are documented separately from construction-document processing.

Construction Data Processing Commitments Intelligence Systems Security Access & Retention Ownership & Oversight Processing Categories Research & Boundaries What We Do Not Claim Evidence Contact

01Construction Data Processing

Where Project Information Goes.

Processing environment

A restricted CCFE review workflow. Documents are accepted only after email-verified authorization, held in private access-controlled storage with no public URL, and made available to the review workflow through time-limited links.

Purpose

Construction-document storage, analysis, estimating support, and Construction Intelligence for the requested engagement.

Information may include

Drawings
Specifications
Addenda
RFIs
ASIs
Contracts
Schedules
Estimates
Takeoff information
Scope information
Product information
Pricing
Bid information
Client-provided project files
Derived Construction Intelligence

This list reflects the document types a client may provide for review. It is not a statement that every project includes all of them.

Processing standard

Submitted documents are used to perform the requested engagement and are not published, sold, or treated as public material.
Access to submitted documents is limited to authorized personnel, approved CCFE systems, and approved project workflows.
Project documents are not requested through ordinary website lead forms. Document submission is a separate workflow.
CCFE publishes a boundary statement, including any statement about where project information is and is not processed, only after the operating environment has been verified to support it. The verification record is maintained internally.

02Commitments

Six Commitments We Can Be Held To.

Stated plainly, so they can be checked against what actually happens.

Confidential by Agreement

Project information is handled under confidentiality and nondisclosure agreements, and under project-specific terms where they apply.

Used for the Requested Work Only

Documents submitted for an engagement are used to perform that engagement, not repurposed for unrelated work.

Not Sold and Not Brokered

CCFE does not sell confidential project documents or personal information, and does not operate as a data broker.

Stated Boundaries Only

CCFE does not publish processing, infrastructure, access, or security claims that it cannot demonstrate. Boundaries are stated precisely rather than implied.

Human Authority on Findings

Every consequential finding is subject to experienced human review, and can be challenged, corrected, or rejected.

Sensitive Intake Files Are Not Stored

Resumes and comparable intake files are transmitted for review and are not retained as files in our systems. Submission records hold applicant and transaction information only.

03Construction Intelligence Systems

The Systems That Read Project Information.

SQUARES AI™

The Construction Intelligence engine. Connects project documents, estimating information, scope, risk, contradictions, and commercial context.

WATSON

Pre-bid intelligence. Evaluates document quality, bid viability, document confidence, scope clarity, commercial exposure, estimating effort, procurement and schedule conditions, and identified project risks.

HOLMES

Specification, product, scope, and commercial document intelligence. Owns the Exhibit Q deliverable.

ROGUE IQ

The research and technology system behind the engines, built around construction workflows and human-governed intelligence.

How the review runs

When these systems review confidential project information, the review runs through the restricted CCFE review workflow described above, under CCFE oversight, with access limited to authorized personnel and approved systems. These are not public chatbots, and project documents are not published.

Public research stays separate

Public manufacturer, technical, standards, and product research may be gathered separately where required. Confidential contract text, proprietary project wording, and client documents are not used as public search input.

04Security

Security Before Automation.

Automation exists where the benefit justifies the risk and the controls exist. Some functions remain intentionally human.

Access is limited to the people who need the information for the engagement.
Project files are held in controlled storage and shared through time-limited access links rather than public URLs.
System credentials are held server-side and are never exposed to a browser.
Review records identify the documents submitted for a review, the requesting party, and the resulting report, so an authorized person can establish what occurred.
A data source, workflow, integration, or function can be isolated when something goes wrong.
Vendor and model selection is evaluated before it is relied upon, not after.

What we will not say

We will not claim that any technology environment is unhackable, risk free, or one hundred percent secure. Risk is reduced, managed, detected, and contained — not eliminated.

05Access & Retention

Who Can Reach Project Information, and for How Long.

Access control

Access to confidential project information is limited to authorized personnel, approved CCFE systems, and approved project workflows.
A submitted document receives no public address. It is held in private storage and referenced only through time-limited links issued to a verified session.
System credentials are held server-side and are never exposed to a browser.

This page does not claim zero-trust architecture, hardware-key enforcement, specific multi-factor technology, specific encryption methods, or third-party certifications. Those statements would require verification that CCFE does not currently publish.

Retention & deletion

Retention follows the Privacy Notice, applicable agreements, insurance requirements, and legal requirements.

CCFE does not publish a retention period it cannot demonstrate, and the environment supports deletion of project information under the approved policy. A formal retention schedule is an administrative definition rather than a published number.

Backups containing project information are expected to remain within the same operating boundary as the retained records. CCFE does not publish detailed backup architecture.

06Ownership & Oversight

Your Documents Remain Yours.

Customer Data Ownership

Clients retain ownership of the confidential project information they provide to CCFE, subject to applicable contracts and agreements.

CCFE’s processing of project information does not transfer ownership of the client’s original construction documents to CCFE.

Human Oversight

Construction Intelligence does not eliminate professional review. CCFE uses human oversight as part of its estimating, document-analysis, and Construction Intelligence workflows.

Final estimating, scope, risk, and bid decisions remain subject to authorized human judgment.

AI Training

CCFE does not knowingly authorize confidential client construction documents or derived project intelligence to be used to train publicly available general-purpose AI models.

Internal development, benchmarking, evaluation, and improvement are governed separately from client project work.

07Processing Categories

Three Categories, Kept Distinct.

Ordinary website and business technology may support the public site without ever being part of construction-document processing. CCFE does not claim that no outside party supports its operations — hosting, telecommunications, email, and similar services are ordinary business infrastructure.

Confidential Construction Information

Processing environment: Restricted CCFE review workflow
Purpose: Construction-document storage, analysis, estimating support, and Construction Intelligence.

Accessed only by authorized personnel, approved CCFE systems, and approved project workflows.

Public Website Services

Processing environment: Website and application platform — Base44
Purpose: Public website hosting and delivery, website security, transactional email delivery for inquiries and submissions, and basic site analytics.

These services support ordinary website functions. Their presence does not mean those providers are authorized to receive confidential construction-document packages.

Administrative Services

Processing environment: Ordinary business functions
Purpose: Business email, accounting, banking, communications, and other administrative operations. Payments are not currently processed through this website.

Administrative providers are named only after their actual use has been verified. These functions are separate from Construction Intelligence work.

08Research & Boundaries

Public Research, Private Projects.

Data minimization

Collect only the information required for the immediate purpose.
Lead forms collect contact details, the service requested, and a general project description — not project documents.
Project documents are requested only when a review actually requires them, through the separate secure submission workflow.
Documents are not replicated across systems for convenience.

Public research boundary

Public manufacturer, technical, standards, and product research may be gathered separately where appropriate.
Approved research terms describe products and standards — for example, a manufacturer, a product, and its installation requirements — rather than a client, a project, or contract wording.
Public research and confidential project processing remain separated.

What We Don’t Do With Protected Project Information

01
We do not intentionally expose confidential project content to public search engines.
02
We do not use confidential contract text or proprietary project wording as a public search term.
03
We do not treat confidential construction packages as public research material.
04
We do not permit public website analytics to capture protected document content.
05
We do not request project documents through ordinary marketing or lead forms.
06
We do not publish processing, infrastructure, or security claims that we cannot demonstrate.

09Limits

What We Do Not Claim.

A trust page that only lists strengths is a marketing page. These are the boundaries of what we do.

01
We are not lawyers and do not provide legal advice.
02
We do not act as a client’s fiduciary, trustee, agent, or legal advisor.
03
We do not claim certifications, audits, or ratings we have not obtained. Where an engagement requires a specific standard, it is addressed in the agreement.
04
We do not replace independent verification of the documents provided to us.
05
We do not present findings as complete where documents were missing, superseded, or never provided.
06
Our work reflects the information available at the time of review.

10Evidence