> Source: https://txtfetch.com/subprocessors
> Plain-text twin — every page on txtfetch.com has one. https://txtfetch.com/text

---

# Sub-processors

The infrastructure and service providers txtfetch relies on to run the API and the site — nothing more.

**AWS Lambda**: us-west-2 (Oregon) · Runs the extraction engine (Tika/Tesseract) and the API itself · data: Document bytes, in memory only, for the duration of a single request

**AWS CloudFront**: Global edge network · CDN and TLS termination for the site and API edge · data: Request metadata (no document content)

**AWS S3**: us-west-2 (Oregon) · Transient large-file upload buffers, plus static site assets · data: Document bytes for large uploads (transient); compiled site files

**AWS SES**: us-west-2 (Oregon) · Delivers /contact form submissions by email · data: Name, email address, and message text you submit via /contact

**AWS ACM / CloudWatch**: us-west-2 (Oregon) · TLS certificate management and operational logging/metrics · data: Certificates; operational logs and metrics (no document content by design)

**Google Analytics**: Global (Google infrastructure) · Website traffic analytics for txtfetch.com and app.txtfetch.com · data: Cookies and per-visitor identifiers, per Google's standard Analytics data collection — see Google's privacy policy

Last updated 2026-07-16. This list is referenced by the [Data Processing Addendum](https://txtfetch.com/dpa) — any addition will be reflected here first.