The short version
QSimHealth is run by ChiAha, Inc. It simulates staffing for emergency departments, walk-in clinics and appointment offices. We keep what we need to run your account, the app and billing. QSimHealth does not ask for patient information and is not built to hold it. The simulator works on counts, rates, times, shifts and costs, not on patient records. We do not sell your data and we do not use it to train AI models. Our own logs are deleted after 90 days; AI chat questions and answers are kept for up to one year; your account record is kept as described in section 7.
Patient information: QSimHealth is not built to hold protected health information (PHI) and is not a HIPAA-regulated system. Do not enter patient names, identifiers or anything else that identifies a real patient, in the app, the chat or through an MCP server (see section 4 of our Terms).
1. What we collect
1.1 Every visitor
- IP address. Used in memory by our rate limiters. It also appears in our server logs (for example on lines about calls to the public MCP server) and in our error log (section 1.9).
- Server logs. Our server writes a log line for each request: the time, the method, the full web address requested (including anything after the
?), the status code and how long it took. Some lines about account events (a sign-up, a payment event, an emailed notice) include the email address involved. These logs are held by our host, Fly.io. - User agent. On our own files we keep only a rough category (for example browser or claude.ai), not the full string.
- Session hash. Where our files need to tell repeat visits apart, they store a one-way hash of your IP address and that user-agent category (SHA-256, first 16 hex characters) instead of the IP address itself.
1.2 Signing in and your account
- How you sign in. There are no QSimHealth passwords. You sign in with a Microsoft or Google account (whichever the sign-in page offers). From that sign-in we receive your email address, your first and last name and, for Microsoft, your directory's tenant ID and your user object ID. The tenant and object IDs are kept only in your sign-in session, in server memory.
- Confirming your email. If the sign-in does not already prove you own the address, we email a one-time 6-digit code to it, and account features turn on once you enter it. The code is kept only in server memory, as a salted hash, for at most 10 minutes.
- Your account record. Once your email is confirmed, we keep a record in a file on our server (
/data/qsh-subscription-state.jsonl): your email address, your status (trial, paid, lapsed or deleted), the date you first signed in, payment and lapse dates, and FastSpring subscription IDs for the app and the AI chat add-on. - Customer records and team notifications. Your first confirmed sign-in, later sign-ins, purchases, cancellations and an account deletion are sent, with your name and email, to ChiAha's customer records (CRM) and to our team's notification channels (Slack and an internal email).
- Deleting your account. Delete my account on your account page ends your access, adds a deleted entry to your account record and tells our team, who mark your CRM contact. It does not erase the earlier entries in your account record, and it does not cancel a FastSpring subscription: cancel that first. To have your remaining records erased, email us (section 8).
1.3 Simulation inputs
- The app (
/app) and the scenario preview (/embed) send staffing numbers to our server to run the simulation: arrival rates, provider counts (MD / PA / Locum), treatment times, shifts, costs and the number of days to simulate. - These inputs are run and the results returned to you. We do not write them to our files.
- The app saves your current inputs and display settings in your own browser (section 6), not on our server.
- The preview's simulation endpoint (
/api/embed-simulate) needs no account. It is limited to 10 requests per minute per IP address, accepts at most 64 KB and refuses requests from other websites.
1.4 AI chat in the app
The chat in the app is open to people on the free trial and to subscribers with the AI chat add-on. When you use it:
- Your messages in the conversation, together with the scenario currently on the page, are sent to Anthropic through its API to get an answer from Claude. To run simulations, Claude calls our public MCP server, and those calls are logged as in section 1.5.
- Chat questions and answers are kept to improve the service. Each turn (your question, the answer, token counts, the tools it ran, whether it worked, how long it took, the page you were on and a random ID your browser makes for that tab) is sent to ChiAha's own operations server. No IP address and no user agent are sent with it. These are deleted automatically after one year. Questions you send when the chat is over its limit are logged the same way.
- On the QSimHealth server we also keep, per turn: the time, the session hash, the scenario context and the token counts (
/data/chat-history.jsonl, 90 days). - Report this response. If you use the Report link under an answer and submit it, we save that question, that answer, your note and the facility type to
/data/reports.jsonlwith the session hash (90 days). - Chat use is counted in Google Analytics (chat opened, message sent, answer received, tools run, links clicked). These events carry counts, lengths and outcomes, never the text of your messages.
- Chat is limited to 20 messages per 24 hours per IP address and has a monthly spending cap. A Cloudflare Turnstile bot check runs before each message.
1.5 Public MCP server (qsimhealth.com/mcp/v1)
Our free public Model Context Protocol server lets AI assistants such as Claude run the QSimHealth demo (MD-only staffing, a flat 24-hour arrival rate). It needs no account. For each tool call we store, in /data/mcp-tool-calls.jsonl: the time, the tool name, the session hash, the user-agent category, the name the MCP client reports, a source tag, whether it worked, how long it took, and the tool's inputs (staffing numbers, cut to 1 KB). This file is deleted after 90 days. Our server logs also record the IP address of each call. Tool calls can also be counted in Google Analytics (tool name, client type and name, whether it worked, how long it took; not the inputs or the IP address).
1.6 Personal MCP URL
With an account, the Connect to Claude page can give you a personal MCP URL. It contains your email address and a key worked out from it, so we do not store the key. Because the URL holds your email address, our server logs record that address each time the URL is used. Calls on this URL are not written to our MCP file. Keep the URL to yourself.
1.7 Payments (FastSpring)
- Subscriptions are sold through FastSpring, our merchant of record. FastSpring takes your payment and billing details directly; we never see or store card numbers.
- FastSpring tells us when a subscription starts, renews, fails to charge or ends. From those messages we keep your email address and the FastSpring subscription ID (section 1.2).
1.8 Emails and forms
- Account emails. We send the sign-in code, a welcome email when your trial starts and a notice two days before it ends. To send the trial notice only once, we keep your email address and trial end date in
/data/qsh-trial-ending-sent.jsonl. - Join our list. The form on the home page sends your email address and any name you type to our CRM and team notifications, and we email you a welcome with an unsubscribe link.
- Instructor kit. The form on the educators page sends your name, email address, school and course to our CRM and team notifications, so a person can send you the materials.
- Both forms use a Cloudflare Turnstile bot check.
1.9 Error log
When a request fails with a server error, we write a record to /data/error-log.jsonl: the time, the page path, the method, the status code, the IP address and the technical error. It is deleted after 90 days.
1.10 Analytics
We use Google Tag Manager (container GTM-NL7VDMTV) and Google Analytics 4 to count page views, where visits come from, button and link clicks, sign-ups, purchases and chat use. These events never include your email address, your name or what you type in forms. Section 6 covers the cookies and your choices.
2. What we do not collect
- No patient information. The app asks for staffing numbers, not patient records. Do not enter PHI.
- No card numbers. Payment details go directly to FastSpring.
- No passwords. You sign in with Microsoft or Google.
- No IP address with chat text. Chat questions and answers are stored without your IP address.
- One advertising tracker, US only. The LinkedIn Insight Tag runs on our public pages for visitors in the United States (see Cookies). It never runs for visitors outside the US or in the app once you are signed in, and we use no other ad network.
- No sensitive personal information such as race, religion, health, biometric data or precise location.
3. How we use it
- Run the app, the simulations, the chat and the MCP servers.
- Sign you in, run your trial and check your subscription.
- Prevent abuse (rate limits, bot checks, spending caps) and fix errors.
- See, in aggregate, how the site and its tools are used, and improve them.
- Send account emails (sign-in code, trial welcome, trial-ending notice) and, if you joined our list, product updates.
- Contact you about your account, a purchase or a request you sent us.
Apart from the LinkedIn retargeting described in Cookies, we do not use your data for advertising. We never use it for profiling or for automated decisions that have legal or similarly significant effects on you.
4. Who we share it with
- Fly.io hosts the application, its server logs and the encrypted volume that holds the files named on this page. ChiAha's operations server, which keeps chat questions and answers, also runs on Fly.io. fly.io/legal/privacy-policy
- Microsoft and Google handle your sign-in. Their privacy policies govern that step.
- Anthropic processes chat messages and the scenario sent with them, through its API. anthropic.com/legal/privacy
- FastSpring runs checkout and billing as merchant of record and tells us when a subscription starts, renews or ends. fastspring.com/privacy
- Resend delivers our emails: the sign-in code, the trial emails, the list welcome and our team's internal notification emails. resend.com/legal/privacy-policy
- Slack carries our team's notifications of sign-ups, sign-ins, purchases, cancellations, account deletions and form requests, with the name and email address involved. slack.com/trust/privacy/privacy-policy
- Cloudflare (Turnstile) runs the bot check on the chat and on the two forms. cloudflare.com/privacypolicy
- Google (Tag Manager and Analytics 4) receives site analytics. policies.google.com/privacy
- Your MCP client. If you call our MCP servers from Claude, ChatGPT, Cursor or another client, that client's own privacy policy governs what it does with your inputs before they reach us.
We do not sell, rent or trade your data. The US-only LinkedIn retargeting may count as "sharing" for cross-context behavioral advertising as California law defines it; you can opt out as described in Cookies.
5. AI model training
- We do not use the data we collect to train AI models. Chat messages, simulation inputs, account data and analytics are not used to train Claude or any other model.
- Anthropic processes chat traffic through its API. Anthropic's published policy is that it does not train its models on API traffic by default. See its commercial terms.
- Other MCP clients have their own data-use policies.
6. Cookies and browser storage
| Name | Set by | What it does | How long |
|---|---|---|---|
| QSimHealth session cookie | QSimHealth | Keeps you signed in. HttpOnly and Secure. The session itself is held in server memory and ends after 30 days without use, or sooner when the server restarts. | Until you close the browser |
.AspNetCore.Cookies | QSimHealth | Sign-in ticket after Microsoft or Google sign-in | Until you close the browser, at most 14 days |
.AspNetCore.Correlation.* | QSimHealth | Protects the sign-in handshake | About 15 minutes |
chiaha_consent | QSimHealth | Remembers your analytics choice | 12 months |
_ga, _ga_<id> | Google Analytics 4 (via Tag Manager) | Tell visits apart and keep GA4 session state | Up to 2 years |
LinkedIn cookies (for example li_sugr, bcookie, lidc) | LinkedIn Insight Tag (via Tag Manager), public pages, US visitors only | Retargeting on LinkedIn and ad measurement | Up to 1 year |
The only advertising cookies are LinkedIn’s, for visitors in the United States on our public pages (see below). FastSpring's checkout window on the upgrade page and Cloudflare's bot check are run by those companies under their own policies.
Browser storage. The app keeps your current scenario inputs and display settings (theme, text size, panel layout) in your browser's local storage, and a random chat ID for each tab in session storage. These stay on your device; clear your browser's site data to remove them.
Your choice
Advertising cookies are off by default for every visitor, with one exception: visitors in the United States get the LinkedIn Insight Tag on our public pages, which sets LinkedIn cookies so we can show our LinkedIn posts and ads to people who visited (retargeting). It never runs for visitors outside the US (the EEA, the UK and Switzerland included) or in the app once you are signed in, and we use no other ad network.
To opt out of the LinkedIn retargeting, choose Reject under Privacy settings in the footer; the LinkedIn tag then does not load for you. You can also turn off ads based on other sites in your LinkedIn ad settings.
If you visit from the EEA, the UK or Switzerland, we set no analytics cookie until you choose Accept on the notice at the bottom of the page. Choose Reject and Google records only a cookieless page count that cannot be linked to you or to a later visit. Your answer is kept in the chiaha_consent cookie for 12 months, and you can change it at any time with the Privacy settings link in the footer.
If your browser sends a Global Privacy Control or Do Not Track signal, we turn off analytics and advertising cookies without asking you.
7. How long we keep it
A background job on our server runs every 24 hours and deletes rows older than 90 days from the log files marked below. Account records are not logs, and that job leaves them alone.
| What | Where | How long |
|---|---|---|
| Server logs (requests, IP addresses on some lines, email addresses on account-event lines) | Fly.io | Fly.io's log retention period |
| Chat turn metadata (no message text) | /data/chat-history.jsonl | 90 days |
| Chat reports you submit | /data/reports.jsonl | 90 days |
| Public MCP tool calls | /data/mcp-tool-calls.jsonl | 90 days |
| Error log (includes IP address) | /data/error-log.jsonl | 90 days |
| Chat questions and answers (no IP address) | ChiAha operations server | One year, then deleted automatically. Email us to have yours deleted sooner. |
| Account record (email, status, dates, FastSpring IDs) | /data/qsh-subscription-state.jsonl | No automatic deletion. Deleting your account adds a deleted entry but does not erase earlier ones; email us to have them erased. |
| Trial notices sent (email, trial end date) | /data/qsh-trial-ending-sent.jsonl, /data/qsh-trial-welcome-backfill.jsonl | No automatic deletion; erased on request |
| Sign-in codes, sign-in sessions, rate-limit counters | Server memory | Codes 10 minutes; sessions up to 30 days without use; all cleared when the server restarts |
| CRM contact and its events (name, email, what happened) | ChiAha CRM | No automatic deletion; removed on request |
| Team notifications | Slack and our internal email | No automatic deletion |
| Billing records | FastSpring | FastSpring's retention policy |
| Analytics | Google Analytics | 14 months (our GA4 property setting) |
| Scenario inputs and display settings | Your browser | Until you clear them |
8. Your rights and how to use them
Email qsimhealth@chiaha.com and include:
- What you want. For example: a copy of what we hold on you, deletion, a correction, leaving our mailing list, or help cancelling a subscription (cancelling itself is done in FastSpring's customer portal, linked from your account page).
- The email address you sign in with, which is how we find your account record and CRM contact. For chat or MCP records, also give the approximate date and time and the scenario or a phrase you used, so we can find the rows.
We aim to respond within 5 business days. On a deletion request we remove what we hold for that email address in our files and our CRM. FastSpring keeps its own billing records under its policy. You can also leave our mailing list with the unsubscribe link in any list email.
9. International users (GDPR, UK GDPR)
QSimHealth is run from the United States. If you use it from the EEA, the UK or another place with similar data-protection laws, your data is transferred to and processed in the United States.
Our lawful bases under GDPR Article 6:
- Contract for your account, sign-in, trial, subscription and the account emails that go with them.
- Legitimate interest for server logs, rate limits, bot checks, abuse prevention, error records, chat records used to improve the service, and aggregate analytics where consent is not required.
- Consent for our mailing list, analytics cookies where we ask first, and chat reports you choose to submit. You can withdraw consent at any time.
You have the rights of access, rectification, erasure, restriction, portability and objection (section 8), and the right to complain to your local data-protection authority.
US export controls: we look up the country of each connection (from its IP address, not stored) to refuse service in US-sanctioned countries, and we screen the name, company, email and country of sign-ups and orders against the US Consolidated Screening List. IP Geolocation by DB-IP.
10. California users (CCPA / CPRA)
- Categories we collect: identifiers (name, email address, Microsoft tenant and object IDs, IP address); commercial information (trial and subscription status, FastSpring subscription IDs); internet activity (pages and requests, user-agent category, analytics events and cookies, and LinkedIn cookies for US visitors on our public pages); and what you type in our forms (school and course for the instructor kit). We collect no sensitive personal information.
- Sources: you (sign-in, the app, chat, forms), Microsoft or Google (at sign-in), FastSpring (billing events) and our own server logs.
- Purposes: see section 3.
- Sale or sharing: we do not sell your personal information. The US-only LinkedIn retargeting may count as sharing for cross-context behavioral advertising. Opt out with Reject under Privacy settings in the footer, or with a Global Privacy Control signal, which we honour.
- Rights: to know, to delete and to correct. To opt out of sharing, see above. Email qsimhealth@chiaha.com.
11. Children's privacy
QSimHealth is not directed to children under 13. We do not knowingly collect personal information from anyone under 13. If you are a parent or guardian and believe your child has given us personal information, email qsimhealth@chiaha.com and we will delete it.
12. Security
QSimHealth runs on Fly.io, with TLS to the browser and an encrypted volume for the files named on this page. There are no QSimHealth passwords: you sign in with Microsoft or Google, and an email address counts only once it is proven, by that sign-in or by the emailed code. Session cookies are HttpOnly and Secure. The chat, the public MCP server, the sign-in code and the preview are rate-limited, and the chat has a monthly spending cap. FastSpring's messages to us are checked with a shared-secret signature. We make no HIPAA or SOC 2 claims, because QSimHealth is not built to hold the kind of data those frameworks govern.
13. Changes to this policy
If we make material changes, we will update this page and its "Last updated" date. We may also email account holders about significant changes.
14. Contact
Questions, requests or concerns: qsimhealth@chiaha.com. We aim to respond within 5 business days.