Security and privacy

Procurement documents are sensitive. They contain pricing, strategy, technical details, and sometimes personal data. Here's how we handle them.

Data storage

Documents are stored in Amazon S3 (AWS cloud storage) with encryption at rest. Access is restricted to your organization's account - other users can't see your files.

Analysis results, findings, scores, and metadata are stored in a PostgreSQL database, also encrypted at rest.

All connections between your browser and our servers use HTTPS (TLS encryption in transit).

Who can access your data

• Your organization members - everyone in your organization sees all procurements, documents, and results
• Platform administrators - for troubleshooting and support purposes only
• No one else - your data is not shared with other customers, and not used to train AI models

AI processing

When you run an analysis or composition, your documents go through two layers of isolation before they reach an AI model:

Per-run sandbox

Each AI run (bid analysis, RFP composition, RFP review, prep checklist, market research, etc.) runs inside a fresh, throwaway workspace called a sandbox — essentially a dedicated container created specifically for that one run. Your documents are uploaded into that sandbox at the start of the run, and only the agent driving that run can read them.

• Different runs (and different organizations) get different sandboxes — one run never sees another run's files.
• When the run finishes, the sandbox is destroyed. No state lingers.
• If a run pauses for clarification, the sandbox is preserved exactly as the agent left it (so you can resume later) but stays just as isolated.

AI provider boundary

The agent inside the sandbox calls AI services (language models) when it needs to reason or generate text. Here's what that means:

• Document text is sent to the AI provider in the conversation as the agent reads files and works.
• The AI provider doesn't store your data for training purposes. We use API access with data processing agreements that prohibit training on customer data.
• Processing happens in real time — text is sent, processed, and the response comes back. There's no persistent copy at the AI provider.

The AI providers we use (Anthropic, OpenAI, Google) all offer enterprise API terms with clear commitments about not using API data for model training.

Document parsing

Document parsing (PDF, Word, Excel, OCR for scanned files) happens inside the per-run sandbox using open-source libraries — your document content is not sent to a separate third-party parsing service.

• Originals are stored in S3 and uploaded into the sandbox at the start of each run
• Parsing runs entirely inside that sandbox
• The sandbox is destroyed when the run completes; no parsed copy is retained

Authentication and access

• Email and password authentication
• Organization-based access - you see everything in your organization, nothing from others
• No public access - all data requires authentication

Data deletion

When you delete a procurement, all associated data is removed:

• Uploaded documents are deleted from storage
• Analysis results, findings, and scores are deleted from the database
• This is permanent and cannot be undone

When you delete your account, all your data is removed.

What we don't do

• We don't sell your data
• We don't use your documents to train AI models
• We don't share your data with third parties (except the processing services described above)
• We don't access your documents unless you explicitly ask for support help