BinderDex API

Developer Privacy

Account data, API usage logs, and payment processing.

This page covers what the BinderDex developer console and API store about you. For BinderDex's main app and website, see the BinderDex privacy policy.

Account data

Signing up for a developer account stores your email address and, if you sign in with Google, the account identifier Google gives us. We use this to identify your account, send account and billing notices, and enforce the per-account key and rate limits described in rate limits and errors.

API usage logs

Each request to /v1 or the MCP server is logged with bounded metadata: which key made the call, the endpoint, the response status, and the timestamp, so we can enforce rate limits and quotas and diagnose problems. We do not log full request or response bodies, and we do not log your API key itself in plain text.

Payment processing

Paid plans are billed through Stripe. Stripe collects and stores your payment details; BinderDex never sees or stores your full card number. We keep the billing information Stripe reports back to us, such as your subscription status and plan.

Support contact

Questions about this page or a data request: [email protected].