Trust · Analyzer Privacy
What happens to uploaded files.
The RFP analysis workflow accepts confidential past proposals and active RFPs. Here's exactly what happens to each — no marketing language.
- deletion control
- Admin
- workspace access
- RBAC
- training use
- 0
in-product or assisted
role-based permissions
covered by Grounded-AI Pledge
Analyzer lifecycle
Data retention timeline
- T+0s Signed upload URL writes the file to US-region R2.
- T+60s Source object deleted after extraction completes.
- T+24h Session-scoped content blocks and embeddings expire.
- T+90d Non-content audit events age out.
Consent required
Before you upload anything, the app requires you to confirm that you have the right to upload the documents and that you understand the never-train-on-data policy.
- What's uploaded?
- Past proposals, RFP/RFQ/RFI documents, security questionnaires, policy documents, and other source material you add to a trial or paid workspace.
- Where is it stored?
- Cloudflare R2 object storage and the workspace database in the US region. Files are written via signed URL with a short upload TTL.
- How long does it live?
- Workspace files, extracted text, embeddings, and generated artifacts stay available until a workspace administrator deletes them, exports and closes the workspace, or requests assisted deletion.
- Can I delete it faster?
- Yes. Workspace administrators can delete uploaded material in-product or request assisted deletion at privacy@bidforge.com.
- Who can access it?
- Authorized users in your workspace according to their permissions. PursuitAgent staff do not read workspace uploads except under documented support or break-glass incident response, both logged with audit retention.
- Is it used to train any model?
- No. The Grounded-AI Pledge §4 applies to workspace uploads. We contract with all model providers (Anthropic, OpenAI, Google) to forbid training on API inputs, including inputs derived from customer workspaces.
- What if I sign up?
- Trial workspaces convert in place. Your uploaded material, extracted content, embeddings, KB blocks, citations, and drafts remain in the same workspace when you choose a paid plan.
Timeline, step-by-step
- T+0s You upload a file via signed URL. R2 stores the file; Postgres records an `analyzer_uploads` row.
- T+1–60s Backend extracts the file's text and embeddings, inserting content blocks into `analyzer_content_blocks` (session-scoped, isolated from any other data).
- T+60s R2 object deleted. Only the extracted text + embeddings remain.
- T+24h Hatchet TTL sweeper deletes the session and all its content blocks + analyses. Row-level cascade; no orphans.
- T+90d Audit-log entries for the session (deleted_at, bytes, request_id) age out. No content was ever retained in the audit log.
Privacy contact
Immediate deletion requests, DSAR/erasure under GDPR, or audit questions: privacy@bidforge.com
We reply within 2 business days. GDPR erasure requests process within 30 days.
Run the workflow with your own material.
Start a trial workspace, upload source material, and keep the resulting requirements, KB blocks, and cited drafts if you convert.