Overview
This policy explains what information FetchSet processes, why we process it, how long we keep it, and the rights available to account users and people represented in business-contact data.
FetchSet is a data-resolution service. The production policy must distinguish account information, customer inputs, licensed business-contact data, service telemetry, and permanent suppression records.
Information we process
The final policy should identify each data class and its source rather than treating all information as one category.
- Account data
- Name, work email, organization, authentication events, plan, billing reference, and support history.
- Customer inputs
- Identifiers submitted to an API or workflow for resolution. Contract terms should define permitted use and retention.
- Business-contact data
- Professional profiles, company information, business emails, and other licensed fields, with provenance attached.
- Service telemetry
- Request metadata, outcome, timing, rate-limit state, fraud signals, and charge records.
How information is used
Information is used to provide and secure the service, resolve identifiers, validate results, administer accounts, meter usage, support customers, honor rights requests, and meet legal obligations.
- Return the requested result and explain its provenance.
- Prevent fraud, abuse, unlawful access, and repeated acquisition of suppressed records.
- Improve coverage and quality using appropriately licensed or aggregated signals.
Sources and transparency
The production page must disclose source categories, including customer-provided identifiers, public professional sources, licensed datasets, validation providers, and service providers. Where Article 14 applies, link to the dedicated source-transparency notice.
Do not publish a “sources may include” catch-all. Counsel should verify source categories, lawful basis, field-level license rights, retention, and required individual notice.
Sharing and subprocessors
Describe disclosures to infrastructure, billing, authentication, analytics, support, validation, and licensed-data providers. Link to the public subprocessor inventory and explain customer-directed disclosures.
Retention and security
State retention by data class. Suppression records may require longer retention because their purpose is to prevent reacquisition. Describe administrative, technical, and organizational safeguards without promising absolute security.
Rights and choices
Explain access, correction, deletion, objection, restriction, portability, sale/share opt-out, and appeal rights where applicable. Provide a conspicuous route to Your Privacy Choices.
- Honor Global Privacy Control signals where legally required.
- Delete eligible data and create a suppression record so it is not reacquired.
- Explain identity verification and authorized-agent handling.
Contact and updates
Questions about this policy or how FetchSet handles personal information can be sent to privacy@fetchset.dev.
Material updates will appear on this page with a revised “Last updated” date. Where appropriate, FetchSet will also provide direct notice before a change takes effect.