The vetted third-party providers we use to run TextSight, what each does, and the data involved. We keep this list current and update it when it changes.
To provide TextSight, we rely on a small set of trusted third-party providers ("subprocessors") for hosting, payments, AI processing, email, analytics, and support. Each is used for a specific purpose and only receives the data needed for that purpose. We choose established providers with their own security and privacy programs.
| Provider | Purpose | Data involved | Region |
|---|---|---|---|
| Cerebras | Generates most rewrites in the humanizer | Text submitted to the humanizer | US |
| Anthropic (Claude) | Paraphrasing, summaries, grammar, citations and plagiarism-risk checks; fallback for humanizing and scoring | Text submitted to those tools | US |
| OpenAI | Voice humanizer on the web app, and a fallback scorer | Text submitted to those tools | US |
| Hetzner | Servers running our own AI-detection models | Text submitted for detection (transient) | EU (Germany) |
| Vast.ai | Rented GPU running our own AI-detection models | Text submitted for detection (transient) | US / EU |
| Sightengine | Image AI detection | Uploaded image files | EU |
| DigitalOcean | API hosting | Account & application data (submitted text in transit) | US |
| Supabase | Primary database - your account and your saved scan history | Account data and saved scan content | US |
| Vercel | Marketing site, web app and tools hosting | Usage / request data | Global edge |
| Cloudflare | DNS, TLS, CDN & edge security | Request metadata | Global edge |
| Stripe | Payments & subscription billing (web) | Billing & payment data | US / EU |
| RevenueCat | Subscriptions bought inside the mobile apps | Purchase and entitlement data | US |
| Apple / Google | App Store and Play billing, and sign-in if you use it | Purchase and account identifiers | US |
| Postmark | Transactional email | Email address, message content | US |
| Google Analytics (GA4) | Website analytics | Usage data, cookies | Global |
| Meta (Pixel) | Advertising measurement (marketing site) | Usage data, cookies | Global |
| PostHog Cloud | Product analytics | Usage / event data | US |
| Sentry | Error monitoring (no submitted text is attached to reports) | Diagnostic / error data | EU |
| Google Firebase | Mobile apps only: crash reports and messaging | Diagnostic data, device identifiers | US |
| Crisp | Live chat & support | Messages you send us | EU |
Regions reflect where each provider typically processes data; some operate global infrastructure. Where data leaves your region, transfers rely on appropriate safeguards (see our GDPR notice).
The text you submit for AI detection is processed by our own self-hosted model (Hetzner, EU). Audio you upload to the voice detector is also processed by our own self-hosted model, on our own GPU servers — it is not sent to any third-party analysis provider. Text you send to generative or rewriting tools is processed by Anthropic; images you upload for detection are processed by Sightengine. None of these are used to train TextSight's models, and scans you run without signing in are not stored. See Content Handling.
We may add or replace subprocessors as the service evolves. When we make a material change, we will update this page and the "Last updated" date above. Business and Enterprise customers who have a data processing agreement with us can request advance notice of new subprocessors — see our DPA.