Subprocessors
Four parties can see some portion of what the service holds. Here is each one, exactly what reaches it, and why it is worth the exposure.
The list
| Subprocessor | Purpose | What it receives | Location |
|---|---|---|---|
| Anthropic, PBC | Relevance scoring and written rationales (Claude API) | Solicitation text and metadata; your firm profile; your firm memory. Names, emails, comments, sessions and audit records are never sent. | United States |
| Render Services, Inc. | Application hosting, compute, persistent storage, server logs | Everything the service stores, since the database runs on their infrastructure. Also request logs including IP addresses. | United States |
| [ email provider, TBC ] | Transactional email: invitations, confirmations, notifications | Recipient name and email address, and the contents of the message sent. | United States |
| Google LLC | Typeface delivery (Google Fonts) | Your IP address and user-agent, as part of the browser request for font files. No cookie is set. | Global CDN |
On the model provider specifically
Anthropic is the subprocessor a prospective customer should look at hardest, because the data it receives is the most sensitive thing we hold: your firm profile, including how you describe your own capabilities and past performance, and the record of what you have won and lost.
A deterministic pre-filter runs before any model call, rejecting solicitations against your own stated criteria: hard exclusions, contract value window and deadline. Those rejections never reach the model at all. The filter exists to control spend, and its privacy consequence is worth stating: most of the corpus is never transmitted anywhere.
Data sources are not subprocessors
We read from public procurement sources: SAM.gov today, other portals and feeds later. Data flows from them to us. They do not receive your firm's data, they are not told which firm a solicitation was scored for, and they are not subprocessors of your data.
Changing this list
Before a new subprocessor begins handling your data, we will update this page and give account administrators at least 30 days' notice by email. If you object on reasonable data-protection grounds, write to privacy@purceivo.com; if we cannot resolve it, you may terminate without penalty and export your data first.
We require each subprocessor to be bound by data protection terms no less protective than ours, and we execute Standard Contractual Clauses where a transfer out of the UK or EEA requires them.
Data processing agreement
A DPA is available for firms that need one on file, including SCCs where applicable. Ask at privacy@purceivo.com. During pre-release this will be a draft, as the counterparty entity is still in formation.
Related: Privacy Policy · Security · Terms of Service