Sub-processors
The companies that process data on DebugGo's behalf, what each one does, and what can reach it.
Last updated: 2 November 2026
How to read this list
Every vendor below is engaged under its own data processing terms. Two of them, Stripe and GitHub, only see data in situations you opt into. None of them receives data for its own advertising or profiling.
| Vendor | Purpose | Data that can reach it | Location |
|---|---|---|---|
| Database (Postgres), authentication, private file storage, Edge Functions that receive widget submissions, scheduled jobs (retention purge, email digest). | Everything the service stores: account and organization records, feedback and review comments, console and failed-request logs, element snippets, screenshots and review attachments, hashed secret keys. Edge Function request logs include the submitting IP address for the vendor's log retention period. | United States (AWS us-east-2, Ohio) | |
| Hosting of debuggo.dev (website, dashboard, API routes), cookieless Web Analytics on debuggo.dev only, request logs. | Request logs for debuggo.dev and the dashboard API: IP address, user agent, requested URL, timestamps, kept for the vendor's log retention period. Analytics are aggregate page views without cookies. The widget on a customer's site contacts Vercel only to download the widget script and, for review-link holders, to call the review API. | United States (Vercel edge network; functions in the US East region) | |
| Transactional email: the hourly feedback digest sent to the addresses a project configures, and account emails. | Recipient email addresses the customer configures, and the digest content: feedback messages, reviewer display names, page paths and project name. | United States | |
| Subscription billing for paid plans. | Billing name, email address, payment method and invoice history. Card numbers are entered on Stripe's hosted checkout and never reach DebugGo's servers; DebugGo stores the Stripe customer and subscription identifiers. | United States | |
GitHub GitHub, Inc. (Microsoft) Only when you connect a repository or sign in with GitHub. Privacy terms | Issue creation and two-way status sync through the DebugGo GitHub App. | For reports turned into issues in a connected project (automatically for bug reports, or manually): the message, the reporter's email if given, page path, browser string, viewport, console and failed-request logs (redacted) and element snippets are written into the GitHub issue body. Screenshots are not embedded. Sign-in with GitHub shares your GitHub account identifier and email with DebugGo. | United States |
Changes to this list
Before a new vendor processes customer data we update this page and email the owners of every organization at least 30 days in advance. The data processing agreement sets out your right to object. To be notified at an address other than your account email, write to support@debuggo.dev.
| Date | Change |
|---|---|
2026-11-02 | Vendor locations confirmed: every vendor processes data in the United States. |
2026-10-31 | First published list: Supabase, Vercel, Resend, Stripe (billing only), GitHub (only when connected). |
What is not on this list
- No advertising networks, pixels or data brokers.
- No session-replay or product-analytics vendors on customer sites. Vercel Web Analytics runs on debuggo.dev only and is cookieless.
- No AI or machine-learning vendors receive customer data from the service itself. If you run an agent against the agent API with your own secret key, that is your vendor, under your terms.