Scope of this page
This page covers privacy expectations for the public marketing site and demo-intake workflow. It does not define production deployment data handling for hospital environments.
Information submitted by visitors
When a visitor submits a request-access form, Turing may receive work email, organization, role, EHR vendor, and use-case context shared by the requester.
This information is used to route the right follow-up conversation and prepare a review path aligned with the stated use case.
Website interaction data
The site may capture basic visit and interaction metadata (for example, page path, referrer, and campaign attribution fields) to support launch analytics and conversion troubleshooting.
Collection and downstream tooling are configured per environment and reviewed during launch setup.
Retention and operational review
Request-intake records are retained according to the operating workflow selected during launch and reviewed during pilot planning. Final retention policy is defined in formal engagement documentation.
Contact and revision metadata
For privacy questions, use your active Turing contact path from the demo or pilot conversation workflow so your request can be routed to the right owner.
Last updated: March 1, 2026