Skip to content

Security and trust

Know the boundary before you bring work inside.

BidLaunchPad is designed for public opportunity material and customer-confidential, non-CUI proposal work. We state what belongs in the system, what does not, and where people remain responsible.

01

Public data

Public SAM.gov notices, public descriptions, public attachments, and other public source references used for opportunity work.

02

Customer confidential

Company profiles, selected past performance, approved response knowledge, collaboration, drafts, and outputs within the workspace boundary.

03

Prohibited

CUI, classified information, ITAR/EAR-controlled material, authentication secrets, private keys, banking/EFT data, TIN, raw signatures, and equivalent sensitive content.

How the product is designed

Controls should be visible, not theatrical.

01

Workspace isolation

Customer profiles, evidence, drafts, collaboration, and outputs remain workspace-scoped. Shared public-source caching does not move customer judgments into shared tables.

02

File safety and owner attestation

Uploaded files are inspected, bounded, and malware-scanned before extraction. A file whose readable text, running headers and footers included, carries a CUI, export-control or classification marking is refused, and its text is never saved. Owners attest that manually supplied material contains no prohibited data.

03

Human-controlled facts

Imported or extracted company facts are candidates. Authorized people review and publish facts; the system does not silently overwrite verified values.

04

Traceable operations

Processing state, safe errors, evidence locators, immutable versions, and review decisions remain visible without putting source text or secrets into telemetry.

Current assurance posture

Specific claims, without certification theater.

BidLaunchPad stores customer records in US-hosted services and is designed to align with the FAR 52.204-21 basic safeguarding requirements associated with the CMMC Level 1 practice set.

BidLaunchPad does not claim FedRAMP authorization, CMMC certification, or NIST SP 800-171 compliance. It must not be used for CUI, classified information, or export-controlled material.

Security controls and hosted-provider configuration continue to be validated as the staging pilot develops. Ask us for the current boundary and control-mapping documentation when evaluating the product.

Report a vulnerability

Found a security issue? Tell us first.

Email support@bidlaunchpad.com with “Security” in the subject. Include the affected page or endpoint, the steps to reproduce, and what an attacker could do.

We confirm receipt within two business days, keep you informed while we fix it, and credit you if you want credit. We will not pursue good-faith research that avoids other customers’ data, stops at proof of the issue, and gives us reasonable time to fix it before disclosure.

Do not access, change, or keep data that is not yours, run denial-of-service or social-engineering tests, or upload CUI or other prohibited material.

Have a security or data-boundary question?

Create an account, verify your email, and begin guided company setup in your own workspace.