Public connector pilot · October 12, 2026
Public facts. Limited inputs.
This notice applies to the Bidwell Health public information connector. It does not replace the policies of Claude or the privacy notices that apply to care on Bidwell’s website.
What the connector receives
The documented tools accept only a service identifier, state or territory code, a broad travel situation chosen from a fixed list, or no arguments. The service also receives the technical information needed to process a network request. Do not include patient details, symptoms, medical history, payment information or excerpts from your conversation.
What it does with those inputs
It checks the public service catalogue and reads the official information page for the selected service. The service selection determines which public page is retrieved; no state, symptoms, personal details or conversation text is sent to that page. It returns public information. It does not connect to patient records, payment systems or your Bidwell account. The connector application does not save raw tool arguments, conversation content or individual usage histories. Its prepared measurement design counts successful calls by day and tool, and separately counts availability checks by day and state. These counts cannot establish unique people or individual demand. Durable production measurement is not enabled. No advertising trackers or connector cookies are used.
Interactive symptom education and notes
The intimate health guide provides public education and descriptive symptom choices. Answers and the resulting symptom notes stay in the open page’s memory. They are not sent to the MCP, Bidwell, patient records or analytics, and are not saved in cookies, browser storage or a database. Reloading, leaving or closing the page clears them. No clinician monitors or receives the answers. Choices only select descriptive follow-up questions and assemble your own notes; they do not generate a diagnosis, likelihood score, urgency recommendation or treatment plan. Copying puts notes on your clipboard; printing can create paper or digital copies that remain outside the guide. Clear answers does not remove copies you made elsewhere. Opening the page downloads public assets from Netlify, which may process normal technical request records. Following a source link opens that organization’s website without guide selections or a referrer. Your AI platform separately handles anything you type in its chat under its own policies.
Hosting and AI platform processing
The connector is hosted on Netlify. Hosting and AI platforms may process technical records such as IP addresses, request times and operational logs under their own policies. Rejecting an unsupported field does not mean it was never transmitted to those systems. Our application writes only fixed operational failure codes, such as a public source being unavailable, with at most one entry per code per minute in each running instance. It does not write request bodies, raw tool arguments, request identifiers, IP addresses or exception details to application logs. Netlify manages infrastructure records under its own policies; retention depends on Netlify’s service settings and policies. No fixed deletion period is promised here. Claude separately processes the conversation and connector activity under its own privacy policy.
Links to the practice
Service links include the same general campaign label for everyone: Claude / connector / public care directory. They contain no patient identifier. Following a link takes you to Bidwell’s website, where its privacy notices and separate care process apply. Campaign referrals are not evidence of a completed or paid visit. The practice website already uses Plausible for campaign-tagged page visits and certain Start Visit clicks. Those events are approximate referral signals, not a joined patient journey. A separate browser attribution adapter has been prepared for the practice site but has not been installed. Its proposed session storage lasts up to 24 hours and contains only the fixed campaign and stage flags. Confirmed payments require a separate trusted server integration; patient-linked payment or visit identifiers must never be sent to the connector or public analytics.
Support
For connector questions or privacy concerns, contact support@bidwellhealth.com. Do not include medical details in a connector support request.