BrinkerAdvisor MCP Privacy
This policy covers BrinkerAdvisor Rates, BrinkerAdvisor Reading Guide, and Ask Bob: Moneytalk Archive. These public, anonymous services provide current public RATES information, publisher book metadata and existing reading paths, and reviewed historical Moneytalk metadata, respectively. The services do not require a BrinkerAdvisor account, set application cookies, or access subscriber, payment, financial-account, or private-research data.
Tool inputs and outputs
Tool inputs are processed transiently to return search, record, reading-path, episode-list, comparison, or illustrative ladder results. Search text, record identifiers, filters, hypothetical amounts, prompts, raw URLs, IP addresses, user agents, cookies, click identifiers, and user, account, or session identifiers are not stored in application telemetry.
The Reading Guide and Moneytalk tools use fixed public metadata sources and keep validated snapshots only in process memory. They do not persist catalog tool inputs, outputs, or usage counters, and their requests do not enter the Rates aggregate tool counters. Moneytalk searches only reviewed topic and broadcast-date labels and uses opaque clip identifiers. Original caller titles, summaries, transcripts, recordings, and external recording links are excluded from its tool results and searchable fields.
Public Moneytalk source metadata may contain original titles and summaries. The service processes that source metadata transiently during validation and removes those fields before building its searchable catalog and tool results. Request quotas and catalog snapshots are held in memory; no per-user catalog history is created.
The linked Books website separately discloses its Amazon affiliate relationship. The Reading Guide MCP returns canonical BrinkerAdvisor catalog links, not Amazon purchase links, and does not make purchases or track affiliate activity.
Aggregate measurement
Rates tool calls update privacy-safe operational counters. The Rates application stores UTC daily aggregate counts using fixed tool, outcome, data-freshness, result-count, and latency bands. It also stores aggregate qualified-use and completeness counts. It never creates durable request-level histories. Daily aggregates are retained for 90 days. Final pilot receipts and evidence hashes may be retained for 13 months; temporary extracts are removed within seven days after a receipt is generated.
A separate aggregate counter records only the UTC date and number of completed visits to the support page, including automated visits. It stores no request details or identifiers. Its completeness is unknown; these totals do not measure unique visitors, installations, or conversions.
Hosting providers may process ordinary network and security access data under their own policies. BrinkerAdvisor does not import provider access logs into MCP pilot analytics. External monitoring calls only the data-free health endpoint and records aggregate availability, latency, service name, and version.
Purpose and limits
Aggregate evidence is used to evaluate service reliability and whether the public tools are useful. It is not joined to subscriber or payment data and does not establish attribution, conversion, causality, or a personalized financial profile.