Privacy

We process information you choose to submit and limited site usage data as described below.

CareOpenly is owned and operated by PageOne Lab, Inc., the company responsible for the information described in this policy. For privacy questions, contact leo@pageonelab.com.

Information requests

Lead submissions store your contact details, selected communities, broad care preferences, consent text and version, submission source, and audit timestamps. We do not ask for detailed diagnoses in this flow.

If you ask a selected community to contact you, we may hold the request while that community verifies its official delivery address and accepts our direct-lead rules. Before verification, an invitation tells the community that a user selected it but does not disclose your name, phone number, or email. After verification, we send your request only to the communities you selected.

AI connector searches

Our public MCP connector receives the location, care category, community name, or public ID needed for a search. It returns public community information. For nearby searches using a place name, such as a hospital or landmark, we send that place name to an external location lookup provider to resolve its coordinates. City and ZIP searches may use our own location inventory instead. The connector does not receive your full assistant conversation, collect contact details through its tools, or submit an information request. If you choose to use the linked CareOpenly form, the information-request terms above apply.

See the connector privacy policy for its data handling and log retention details.

Security and abuse prevention

Submission limits use a one-way keyed request fingerprint. Raw IP addresses are not stored in lead or correction records.

Site analytics

We record privacy-bounded page and product events to understand aggregate site usage. An anonymous identifier lasts only for the current browser tab session. We store page paths without query strings and a server-computed bot flag; we do not retain raw IP addresses or user-agent strings with analytics events.

We also use PostHog for anonymous product analytics and session replay on public pages. Session replay captures interactions such as navigation, clicks, and scrolling; form input values are masked before replay data leaves the browser. PostHog is not initialized on administrative or partner portal pages, and URL query strings are removed from captured analytics events.

Corrections

Correction requests store the evidence and contact details needed for human review. Contact data is not published on community pages.