Subprocessors

Last updated 2026-10-14

These companies process personal data on our behalf to run Tabductor. Each receives only what its job needs. The Privacy policy explains what we collect and why.

Before we add or replace a subprocessor we update this page. Business customers with a data processing agreement can ask to be notified; write to ammar@tabductor.com.

Current subprocessors

Subprocessors, their purpose, the data they receive, location and transfer safeguard
Company	Purpose	Data	Location and safeguard
Amazon Web Services	Hosting: servers, managed browsers, database, file storage, encryption keys and the content delivery network. Always.	All service data, including account records, workflows, run records, screenshots, browser profiles and encrypted secrets.	Sydney, Australia (AWS ap-southeast-2); content delivery edge locations worldwide. Standard Contractual Clauses in the AWS Data Processing Addendum.
Clerk	Sign-in, account management and session cookies. Always.	Name, email address, sign-in identifiers, IP address, browser and device details.	United States. EU-US Data Privacy Framework or Standard Contractual Clauses (to verify).
PayPal	Payment processing, refunds and fraud screening. When you add funds.	Name, email, PayPal payer ID, country and transaction records. Card and PayPal account details stay with PayPal; we receive order, payment and refund records.	United States and worldwide (to verify). Standard Contractual Clauses (to verify).
OpenAI	AI models that plan, run and summarize workflows. When a workflow uses an OpenAI model.	Prompts, workflow definitions, and page content and screenshots from the sites your workflows visit.	United States. Standard Contractual Clauses or EU-US Data Privacy Framework (to verify).
Anthropic	AI models that plan, run and summarize workflows. When a workflow uses an Anthropic model.	Prompts, workflow definitions, and page content and screenshots from the sites your workflows visit.	United States. Standard Contractual Clauses or EU-US Data Privacy Framework (to verify).
IPRoyal	Residential proxy network for browser traffic. When a browser profile uses a proxy.	Browser traffic to the sites your workflows visit (encrypted end to end for HTTPS sites), chosen exit country, proxy usage totals.	Lithuania (to verify); exit addresses worldwide. Within the EU/EEA (to verify).
Decodo	Residential proxy network for browser traffic. When a browser profile uses a Decodo proxy.	Browser traffic to the sites your workflows visit (encrypted end to end for HTTPS sites), chosen exit country.	Lithuania (to verify); exit addresses worldwide. Within the EU/EEA (to verify).
CapSolver	CAPTCHA solving. When a workflow meets a CAPTCHA.	The challenged page's address, the CAPTCHA's site key and parameters, browser user agent, and the browser's proxy address and credentials.	To verify. To verify.
2Captcha	CAPTCHA solving. When a workflow meets a CAPTCHA.	The challenged page's address, the CAPTCHA's site key and parameters, browser user agent, and the browser's proxy address and credentials.	To verify. To verify.
Anti-Captcha	CAPTCHA solving. When a workflow meets a CAPTCHA.	The challenged page's address, the CAPTCHA's site key and parameters, browser user agent, and the browser's proxy address and credentials.	To verify. To verify.
Google Fonts	Web fonts for this website. Every page view.	Your IP address and browser details when a page loads its fonts.	United States and worldwide. EU-US Data Privacy Framework (to verify).
Google Analytics	Website analytics, and the amount of each top-up, to see how people find and use Tabductor. Page views, only after you allow analytics in the EU, EEA, UK and Switzerland.	A random identifier stored in cookies, pages visited (private links and payment references removed), device and browser details, approximate location, and top-up amounts with our purchase reference.	United States and worldwide. EU-US Data Privacy Framework (to verify).
Google Ads	Measures whether our ads lead to top-ups (conversion tracking only; no ad targeting or remarketing). When you add funds, only after you allow analytics in the EU, EEA, UK and Switzerland.	Ad click identifiers stored in cookies, and for each top-up its amount, our purchase reference and whether it is your first.	United States and worldwide. EU-US Data Privacy Framework (to verify).
Cloudflare	DNS for our domain (DNS only; our web traffic does not pass through Cloudflare). When our hostname is looked up.	DNS lookups for our hostnames, which come from your DNS resolver.	Worldwide. Standard Contractual Clauses or EU-US Data Privacy Framework (to verify).
Resend	Sends the email after each scheduled run of your workflows, receives email sent to a workflow's address, sends the reply with the run's result, and sends the email when a run needs you. After every scheduled run, when a workflow's email trigger is on, and when a run asks for a person.	Your account email address, the workflow's name, the run's status, summary and result, and the workflow's store as an attachment when you turn that on. For a workflow's email address: the emails sent to it (sender, recipients, subject, text and attachments), and the reply to the sender with the run's result, the store rows it changed and the files it produced. When a run needs you: what it needs, the agent's note, the site's host name and a link to the browser.	United States (to verify). EU-US Data Privacy Framework or Standard Contractual Clauses (to verify).

Websites your workflows visit

The sites your workflows open are not our subprocessors. They receive the browser traffic a workflow sends them, as they would from any browser, and handle it under their own policies.