PRIVACY
Simple, clear handling.
This site provides Clinopilot information, a free browser-based Workflow Closure Snapshot, and a separate beta AI Implementation Stress Test. The pilot workspace supports private process-level review and a synthetic offline demonstration.
What the site receives
The site has no analytics tags or tracking cookies. Its host may process routine technical request information to deliver and protect the pages.
Free snapshot
The snapshot answers are processed in your browser to make a downloadable text file. The page does not send those answers to Clinopilot or save them to a Clinopilot database. Use process-level or fictional examples only. Do not enter patient information, credentials, or production data.
If you choose the email option, your email app opens a draft that may include the snapshot and any source/campaign labels on the link you followed. Nothing is sent to Clinopilot unless you review and send that message.
Pilot workspace and offline demo
The pilot workspace processes notes in the open page. It does not upload them, record calls, save an automatic copy or send them to an AI provider. Exported JSON and readable notes are private working files under your control. Use role labels and public, synthetic or authorized process-level descriptions. Patient records, real patient examples, identifiable images and record screenshots are excluded, including material with names removed that could still identify someone.
Before using client information, record the deployment jurisdiction, responsible organization, permitted purpose and scope, authority, storage/access locations and retention review. Pending fields prevent a handoff from being marked client confirmed. These are preparation controls, not a legal compliance certification. Keep downloaded files in an approved location and apply the agreed retention policy.
Beta AI Implementation Stress Test
The AI Implementation Stress Test uses Clinopilot’s application service on this website’s hosting and Groq for AI generation. Clicking Run Stress Test sends the form inputs to that service for evidence matching, simulated stakeholder perspectives, and AI synthesis. Choosing a follow-up sends the run ID, selected risk and question, implementation context, matched case IDs, and simulated roles. Choosing Send feedback sends the run ID, selected response, and any feedback text to Clinopilot’s hosted database; this feedback feature does not send it to Groq.
Entering text, opening the page, or selecting a feedback rating alone does not submit those inputs. Clinopilot stores run identifiers, follow-up counts, cooldown metadata, and submitted feedback. It does not store the implementation form inputs or generated briefs in its application database. The hosting service and Groq process submitted inputs to provide the service and may retain information under their own policies. Submit only public organizational information, synthetic examples or process steps without patient or personal data. Do not include patient records, real patient examples, staff names, contact details, credentials, production data or confidential material. Run, follow-up and feedback submissions require an explicit data-scope acknowledgment. This acknowledgment cannot detect personal information, establish legal consent or guarantee that a submission meets local law.
Simulated personas and generated risk briefs are hypotheses to validate with real stakeholders. They are not real stakeholder validation, validated readiness scores, clinical guidance, or certification. This notice does not promise a retention period or deletion schedule for submitted beta inputs; contact main@clinopilot.com with handling questions before submitting.
Calls and jurisdiction-specific handling
Recording and transcription are off by default. Before any permitted capture, agree the specific purpose, tool/provider, storage and access locations, participants, access permissions and retention/deletion review; obtain participant permission and offer an unrecorded discussion with minimal written notes. Permission to record a participant does not authorize collection of patient information. Do not show real patient screens in a demonstration.
Current assessments exclude patient information. Any expansion requires a separate written scope, verified authority, local privacy/legal review, appropriate data agreements and agreed security controls before collection. Applicable rules depend on the actual deployment, parties and information, not only the vendor’s headquarters. See the data-handling process.
Business enquiry form
When you choose Send fit-check request on the enquiry form, Clinopilot stores the organization, work email, role, jurisdiction, workflow category and short operational goal you submit. It also stores the request reference, source page, submission time, data-boundary acknowledgement and an optional AI run identifier. We use this information to review and respond to the enquiry and manage agreed work. It is not added to a marketing list by this form.
The hosting service stores these business enquiry records in Clinopilot's application database. Owner-authorized operational tools can read them; there is no public enquiry lookup. A keyed technical identifier limits repeated submissions without storing the raw IP address in this table. The form returns a receipt reference only after storage is confirmed. Copy and email alternatives remain available.
Keep this form to business contact and process information. Do not send patient or clinical records. Contact main@clinopilot.com to request access, correction or deletion; retention and any required records are reviewed when an enquiry or engagement closes. Local information-handling requirements and approved methods are agreed before accepting additional client material.
Payment notification records
Stripe sends signed payment events to Clinopilot's service. Clinopilot stores event and checkout identifiers, the payment stage, amount and currency, a matching agreement reference when supplied, and payment status for operational verification. It does not store card details or copy the full event or billing contact record into this application database. A payment notification does not accept a scope or begin delivery; the owner checks the authoritative provider record against the written agreement.
Messages and purchases
If you email main@clinopilot.com, Clinopilot receives the information you choose to send and uses it to respond to your request. Payments for the 5D Healthcare Transformation Readiness Sprint are active through Stripe. Payment links are shared only after written agreement on scope, dates, the data boundary, and cancellation/rescheduling terms. Stripe processes payment details under its privacy terms, shown at checkout before payment. Kit checkout remains paused.
For a privacy request, contact main@clinopilot.com.