Security for RFP and Bid Documents
BidCompliance is built for sensitive proposal content. This page explains how we protect uploaded files, extracted text, and generated compliance reports.
What this means for proposal teams
Bid teams often upload pricing schedules, delivery plans, legal responses, technical methods, and annexes that cannot be exposed broadly. BidCompliance is designed so those materials are processed only to generate your compliance matrix and supporting citations.
Encryption
All files are encrypted in transit and at rest. Uploaded documents, extracted text, and generated outputs are protected during transfer and storage.
- TLS for data in transit
- AES-256 protection for data at rest
- Azure Blob Storage for secure file storage
Limited use of your files
Documents are processed only to extract requirements, compare bid content, and build the compliance report you requested.
- Files are not reviewed for unrelated business purposes
- Outputs are tied to your account access
- Only the data needed for analysis is sent to processing services
Not used for model training
Uploaded bid and RFP documents are not used to train AI models. This is a core trust requirement for handling confidential proposal material.
- No training on your uploaded content
- No resale of your bid material
- No broad sharing of proposal content
Deletion controls
You retain control over uploaded files and results. Delete analyses and associated files from the product, or choose deletion immediately after analysis completion.
- Delete analyses from your workspace
- Request full account deletion
- Optional post-analysis file deletion
Infrastructure and controls
BidCompliance runs on mainstream cloud infrastructure and payment/authentication providers chosen for security and operational maturity.
- Azure-backed storage and infrastructure
- Clerk for authentication controls
- Stripe for payment processing
Related policies
For the full legal and data-handling details, review the policy pages below.