Legal
Subprocessors
The service providers that can receive personal data from Scrappy, and what each one is for.Last updated: October 1, 2026
Scrappy is operated by AW3 Technology, Inc. We use the providers below to run the service. Some receive data whenever you use Scrappy; most only receive data when you use a particular feature, or when you connect your own account with them. Our privacy policy explains how we handle personal data.
| Provider | Used for | Data it receives | When |
|---|---|---|---|
| Fly.io | Hosting: application servers, database, cache and the cloud browsers (United States, San Jose region) | All data stored in or passing through Scrappy | Always |
| cred.diy and its payment processor | Credit balance, usage billing and the hosted checkout for buying credits | Account identifier and email, credit usage, purchase details. Card details are entered on the hosted checkout and are not seen or stored by Scrappy | Always |
| Resend | Sending email: account messages, alerts, and outreach email you send from Scrappy | Recipient address and the content of the email | Always |
| Anthropic | AI features: the chat agent, extraction, matching, email drafting | The prompts you write and the lead, profile and page content you ask the AI to process | When you use the feature |
| Perplexity | AI source discovery, LinkedIn URL lookup and some AI validation and matching | Search descriptions and the lead or profile content sent for the lookup | When you use the feature |
| OpenAI | Alternative AI provider for email validation and matching | The lead or profile content sent for the check | When configured |
| Webshare | Proxy network that cloud browser and scraping traffic leaves through | The network traffic of browser sessions and scraping jobs (encrypted in transit where the destination site uses HTTPS) and the sites they connect to | When you use the feature |
| SerpAPI and Serper | Web search | Search queries | When you use the feature |
| 2Captcha, Anti-Captcha and CapSolver | CAPTCHA solving | The page address and the challenge to be solved | When configured |
| Hunter | Finding and importing email addresses | Names and company domains being looked up | When configured |
| NeverBounce, ZeroBounce and Kickbox | Third-party email verification | Email addresses being verified | When configured |
| AngelSend | Cold email outreach and warmup, when you connect your AngelSend account; and the chat widget on our public pages, once you open it | Leads and email content you send to AngelSend; for the chat widget, what you type into it and your browser's connection details | When you connect it |
| GitHub | Sign-in with GitHub | Your GitHub profile name, email address and avatar | When you connect it |
| 1Profile | Sign-in with 1Profile | Your profile name and email address | When you connect it |
| Gmail integration, and fetching a Google Sheet you link for import | The Google account you connect and the email you send through it; the address of a sheet you import | When you connect it | |
| IP lookup services (ipinfo.io, ipwho.is, ipify) | Working out the timezone and address of a cloud browser's proxy exit | The proxy's IP address only. No account or lead data | When you use the feature |
What this list does not cover
- Sites you visit with Scrappy. A scraping job or a cloud browser session connects to the websites you point it at. Those sites are not our service providers.
- Destinations you set up. Webhooks, data destinations and exports send data where you tell them to.
Changes
We update this page when we add or remove a provider. Questions: will.schulz@aw3.tech.