Sheet 1, sub-processors
Due Badger runs on a deliberately small set of providers. Each one only receives the data it needs to do its job. This is the complete list.
What it does: Workers for hosting and compute, D1 as the
database, KV for sessions and rate limiting, Durable Objects for the daily scheduler and the
MCP connection, and Turnstile for bot protection on sign up and sign in, once switched on.
Data handled: All service data: your account, your register and its
history.
Where: Served from Cloudflare's global network.
What it does: Sends reminder emails, and account notices such
as a password change.
Data handled: The recipient email address and the content of the email.
Where: United States, under Resend's own safeguards.
If you connect an AI assistant to Due Badger over MCP, for example Claude, that is your own tool and your own agreement with that provider, so it is not a sub-processor I impose on you. There is no advertising or analytics provider anywhere in Due Badger, and no payment processor, since Due Badger takes no payments.
I will update this page whenever the list changes. Questions? Email dalemooney50@gmail.com.