Understand the details
What happens to the conversation?
FluentCare’s published privacy policy separates application storage from provider processing. Review both before evaluating the app. Healthcare/provider arrangements and clinical language evaluation are still being verified.
Follow the conversation
Processing and storage
are separate questions.
Audio from the conversation
Translation processing
The translated response
FluentCare’s application does not save conversation recordings or transcripts in its own storage. Provider processing and retention depend on applicable agreements and settings.
Audio and captions
Audio is sent to OpenAI to provide translation. The policy states that FluentCare does not save conversation recordings or transcripts in its own application storage. Optional on-screen captions clear when you pause or end a session.
That does not mean no provider processes audio or that provider retention is zero. Processing and retention depend on applicable agreements and settings. Verify those arrangements for your intended use.
Account and usage information
FluentCare retains account, clinic, membership and usage information needed to operate the service and administer access and billing. These records are separate from conversation recordings and transcripts.
For the full description of data handling, read the application privacy policy. The policy is the reference for the app; this page is a short explanation.
Current release limits
The published policy says to use only non-patient information during release testing. Do not submit patient information until applicable agreements and settings are confirmed. We do not claim that a general product description establishes healthcare compliance or clinical accuracy.
Public app-store downloads are coming soon. Ask the team about the current release, evaluated languages and requirements before introducing the product in your clinic.
Optional website statistics
If you choose “Allow”, we send website journey statistics to PostHog in the US: public pages visited, traffic-source categories, referring-site domain groups, recognised platforms, approved campaign labels, button destinations and placements, sections viewed, scroll milestones and approximate active time. We also record broad browser and device categories.
A random identifier is stored in this browser for up to 30 days. It helps connect visits in the same browser; clearing storage or switching devices breaks that continuity. Visits are grouped per tab, restarting after 30 minutes without a tracked action or after 24 hours. The first source we observe after permission and each visit’s entry page travel with later actions.
We send only known public page addresses, without query strings, and fixed interaction labels. We do not send form contents, raw referrer addresses or subdomains, arbitrary UTM text, conversation content, staff or clinic identifiers. We do not enable session recordings or person profiles. Like other network services, PostHog receives connection information such as your IP address and browser information.
Use “Analytics choices” in the footer to change your choice. “No thanks”, Global Privacy Control and Do Not Track stop capture and remove stored journey identifiers. This does not erase statistics already received. Previous permission for the simpler tracking does not enable this expanded version; we ask again. Without permission, these events are not sent.
This setup measures the public website. A dashboard, support or download-link click is not proof of signup, a stored request, an app download or a translation session. App analytics remains separate.
Ask before you evaluate
Contact FluentCare with your questions about the current release, provider arrangements or data handling. You can also review the terms and get-started options.