How this list works
The production list must identify every provider that processes personal data on FetchSet’s behalf. Data vendors belong here alongside infrastructure, billing, authentication, support, validation, and analytics providers.
The rows below are structural examples, not an approved vendor list. Replace them with signed vendors, exact purposes, processing locations, transfer mechanisms, and notice dates.
Provider inventory
| Provider | Category | Purpose | Location / transfer |
|---|---|---|---|
| [Cloud provider]To be confirmed | Infrastructure | Compute, database, storage, logging | Approved regions · transfer basis pending |
| [Billing provider]To be confirmed | Billing | Checkout, subscription, invoices | Location and transfer basis pending |
| [Authentication provider]To be confirmed | Identity | Login, OAuth, security events | Location and transfer basis pending |
| [Licensed data vendor]To be confirmed | Data source | Licensed business-contact dataset | Field scope and redistribution grant pending |
| [Validation provider]To be confirmed | Validation | Email or carrier validation | Location and transfer basis pending |
Changes and objections
State how customers subscribe to updates, the advance-notice period, the objection process, and the outcome when a reasonable objection cannot be resolved.
Entry requirements
Before listing a provider, record its DPA, security review, purpose, data fields, retention, processing locations, transfer mechanism, onward processors, incident obligations, and termination plan.
Questions
Route vendor-list questions and objections to the approved privacy or legal contact. Maintain a dated change log so customers can compare versions.