# [Sub-processors](https://rebilder.com/legal/subprocessors) > Every third party that processes data on Rebilder’s behalf, what each one is for, what it sees, where it runs, and whether it is contracted yet. - **Updated:** 2026-08-05 - **Author:** Rebilder LLC - **Description:** Every third party that processes data on Rebilder’s behalf, what each one is for, what it sees, where it runs, and whether it is contracted yet. - **Section:** Legal - **Publisher:** Rebilder LLC ## Summary A short list, kept short on purpose. Each entry states the purpose, the category of data involved, the country of processing, and its contracting status. We update this page before a new vendor starts processing anything. ## How to read this page - **In use** — Processing Rebilder data today under the vendor’s data-processing terms. - **Not yet contracted** — Provisioned in our configuration and required by a feature that is being built, but no data-processing agreement is signed yet. It is listed here before it processes anything, not after. We post a new sub-processor on this page before it starts processing, and email account holders at least 30 days beforehand, unless the change is required by law or is a response to a live security threat. If you object to a new sub-processor within those 30 days, write to privacy@rebilder.com and you may terminate the affected service for the remainder of your term. A data-processing agreement is available for signature on request from legal@rebilder.com. ## Infrastructure - **Vercel, United States (in use)** — Purpose: application hosting and CDN for rebilder.com and the Rebilder API. Data category: HTTP request metadata (IP address, user agent, path, timestamps) in standard platform logs, and cached page bodies. It does not hold database contents. - **Supabase, United States (in use)** — Purpose: the Postgres database behind the Console and the scanner, plus authentication for Console sign-in. Data category: Console account and organisation records, API key hashes, gateway events, scan records, scanner leads with their consent records, and hashed IP rate-limit buckets. This is the same cluster MUMM uses, under a separate schema and a separate database role that has no access to MUMM data. ## Email delivery - **Resend, United States (not yet contracted)** — Purpose: the guide-offer welcome message, outbound campaign email, contact-form forwarding, and the weekly Console digest. The scan report is not emailed. Data category: your email address, the message we send you, and delivery events (delivered, bounced, complained). Rebilder uses its own API key, its own sending domain, its own consent record and its own suppression list, entirely separate from MUMM’s, a shared sending identity would put two unrelated audiences in one reputation and one bounce list. ## Bot challenge - **Cloudflare (Turnstile), United States (not yet contracted)** — Purpose: the challenge that stands between the free scanner and being used as an attack tool. It is the fourth layer of the rate-limit ladder. It is never shown for a first scan, only after repeated scans from one address or under heavy global load. Data category: your IP address and browser signals, collected by Cloudflare directly from your browser, plus a challenge token we verify server-side. We do not receive the signals; we receive a pass or a fail. ## Website analytics - **Ahrefs (Web Analytics), Singapore (not yet contracted)** — Purpose: counting visits to the public pages of rebilder.com, so we know which writing is read and where readers come from. It runs on pages anyone can read, and not on the Console, our internal operator pages, or the sign-in screens. Data category: the URL viewed, the referring page, user-agent and language strings, and a city-level location that Ahrefs derives from your IP address and discards rather than stores. It sets no cookie and no persistent identifier, so it cannot follow you between sites or between visits, and we see aggregate counts rather than individuals. This is the only third-party tag on the site, and the only vendor here that exists for our benefit rather than yours. We think a cookieless counter is the smallest version of knowing whether anyone reads this, but it is a real third party seeing a real request, so it is named here rather than folded into hosting. ## What is deliberately not on this list - No model provider. No LLM is called on any request-serving path, and none is called anywhere in the scoring path, the score is a pure function of a content-addressed evidence bundle, with no model, no randomness and no clock in it. - No advertising pixel, no retargeting tag, and no cross-site tracker on rebilder.com. The one analytics vendor we do use is Ahrefs, named above; it is cookieless, it is confined to the public pages, and it is the whole of the list. - No third-party error-tracking service holding Rebilder data today. - No data broker, enrichment vendor, or list provider, ever. We do not buy contact data and we do not sell yours. Stripe, Inc. (United States) processes card payments and subscription billing. It receives your billing email and payment details directly; we store only a customer and subscription identifier, and card numbers never reach our servers. ## Changes to this list New vendor, new category of data, or a change in country of processing: posted here first, and emailed to account holders at least 30 days ahead unless the law or a live security threat requires it sooner. If you object to a new sub-processor, tell us at privacy@rebilder.com before it takes effect and we will work it out or let you leave with a refund of the unused period.