Use the directory without creating an account.
This page describes the data flows implemented in the current Access OS MVP. It is a plain-language product disclosure, not a promise that a third-party infrastructure provider keeps no technical logs.
Searches and browsing
You can search and browse provider pages without creating an account. Search filters are sent to the application to produce results. Provider pages use public directory fields such as names, locations, specialties, network evidence, and phone numbers.
The application does not ask for a member identifier to search. Do not put health information into a search field or URL.
Reports
A user report is stored with the provider, report type, selected plan when applicable, a normalized answer, and a timestamp. The member identifier is used at submission time to enforce the report gate and prevent duplicate reports; the stored signal uses a keyed hash rather than the raw identifier.
Report notes are stored as submitted subject to validation and length limits. Do not include names, diagnoses, appointment details that identify another person, or other sensitive information in a note.
Location services
If you sort by distance, a ZIP code may be sent to the Nominatim geocoding service operated by the OpenStreetMap community. On New York provider pages, subway proximity may send the provider's public address, city, and state to Nominatim. Access OS caches the resulting coordinates to avoid repeat lookups.
Access OS does not request your home address for the subway feature. See the OpenStreetMap attribution and usage information for that third-party service.
Technical error reporting
When the client catches an application error, it may send a truncated error message, stack information, component context, and the current URL to the application's error endpoint so the service can be operated. Avoid putting sensitive information in URLs or report notes.