Privacy Policy
QueueSim, a ChiAha™ product · Last updated 2026-11-20
The short version
QueueSim is a free queueing simulator. There's no signup, no account, no payment. We collect the minimum metadata needed to run the service, prevent abuse, and keep the lights on. If you use the AI chat, we store your questions and its answers to improve the service, with no IP address attached, and we measure chat usage in Google Analytics. We do not sell, rent, or share your data with advertisers, and we do not use your inputs to train AI models. Telemetry on QueueSim’s own server is automatically purged after 90 days.
Contents
1. What we collect
1.1 Operational telemetry (every visitor)
Every HTTP request to queuesim.com generates standard server logs:
- IP address — processed in memory by the rate limiter (20 simulation requests / 60 seconds per IP) and appears in Fly.io's platform HTTP access logs (retained per Fly's standard log window, up to 30-90 days). The IP is not written to any of our durable JSONL files; those store a non-reversible session hash (SHA-256 of IP + user-agent bucket, first 16 hex chars) for same-client correlation within the retention window.
- User-agent string — bucketed into broad categories (
claude.ai,chatgpt,cursor,smithery,browser,(other)) for usage analytics. Only the bucket label is written to durable storage; the full UA string lives only in Fly's transient HTTP access logs. - Timestamp, request path, response status, response time — standard HTTP access logging.
- Country of your IP address — looked up in memory on every request to apply US export controls (we refuse service in US-sanctioned countries; see the Terms). Only the country code and the path of a refused request are logged, never the address. IP Geolocation by DB-IP (CC BY 4.0).
1.2 Simulation inputs you submit at / or /models/{id}
- The numerical parameters you enter or that come from a hero scenario (arrival rate, server count, distribution choice, schedule, simulation days). These are abstract numbers about a hypothetical queue and do not constitute personal data.
- We do not link these inputs to your identity because we do not have one for you.
- For server-restart reconstruction and abuse audits, a single-line record per simulation run is appended to a server-side file (
/data/site-events.jsonl) containing the run timestamp, a non-reversible session hash (SHA-256 of your IP + user-agent bucket, first 16 hex chars), a user-agent bucket (e.g.browser,claude.ai), the referer's origin only (query strings stripped so click-tracking parameters are not captured), and the parameter ranges (min and max across the 24-hour input arrays plus distribution names). Retained for up to 90 days.
1.3 On-page AI chat (the floating Q bubble on queuesim.com)
If you open the chat widget and send a message, the following happens:
- Your message is sent to Anthropic via their Messages API to generate a response from Claude Haiku 5.5. Anthropic's API does not train its public models on traffic from API calls by default; see Anthropic's data-use policy linked below.
- Chat questions and answers are stored to improve the service. Each turn (your question, the AI's answer, token counts, which tools it ran, whether it succeeded, 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 is stored with them. Chat questions and answers are kept for up to one year, then deleted automatically. To have yours deleted sooner, email queuesim@chiaha.com. Please don't type anything into the chat you wouldn't want us to read.
- On QueueSim's own server we also keep per-turn metadata only: timestamp, a non-reversible session hash (SHA-256 of your IP + user-agent, first 16 hex chars), the scenario you were on, input/output token counts, and a count of how many proposal cards the AI generated. This metadata feeds the aggregate counters at /api/chat-stats and is automatically purged after 90 days.
- Chat usage is measured in Google Analytics (chat opened, message sent, response received, tools run, links clicked). These events carry counts, lengths and outcomes, never the text of your messages.
- Chat is rate-limited to 20 messages per rolling 24 hours per IP and capped at a monthly inference-spend budget.
- Report button. Each assistant response has a small Report this response link. If you click it, a modal opens; if you submit it, we also save that specific exchange with your free-text note and the page-state snapshot at the time of the click (plus the same session hash described above) to a separate file (
/data/reports.jsonl) for product debugging. Reports are subject to the same 90-day retention.
1.4 Public MCP API (queuesim.com/mcp/v1) — the Model Context Protocol server
QueueSim publishes a public Model Context Protocol server at queuesim.com/mcp/v1, listable in the OpenAI app directory, the Anthropic MCP registry, Smithery, Glama, and similar catalogs. It exposes fourteen read-only, pure-compute tools. Every tool takes abstract queueing parameters and returns simulation results — no tool reads from or writes to any persistent user store, and no tool accepts personally-identifying information as input.
| Tool | Required inputs | Optional inputs | Returns |
|---|---|---|---|
simulate_mmc |
arrivalRate (number, > 0, ≤ 200), serviceRate (number, ≥ 0.01, ≤ 10000), servers (integer, 1-50) |
arrivalDistribution (Exponential/Constant), serviceDistribution (Exponential/Constant/Normal/LogNormal), serviceCoV (0-5), simulationDays (1-30) |
Per-hour and overall avg wait time (minutes), peak wait, max wait, queue length, utilization, throughput, plus an artifact link to the interactive chart on queuesim.com |
simulate_scenario |
name (one of single, coffee, grocery, callcenter) |
overrides object with arrivalRate, servers, serviceTimeMinutes, simulationDays (1-30), distributions, and serviceCoV |
Same shape as simulate_mmc |
recommend_staffing |
arrivalRate, serviceRate, targetAvgWaitMinutes |
maxServers (1-50), simulationDays (1-30), distributions, serviceCoV |
Smallest server count whose simulated avg wait does not exceed the target, plus the trial points the search probed |
interpret_result |
arrivalRate, serviceRate, servers, avgWaitMinutes |
none | A plain-English queueing-theory explanation of the result; pure text computation, no engine call |
list_scenarios |
none | none | The four preset scenarios with key, title, and description |
describe_scenario |
name (one of single, coffee, grocery, callcenter) |
none | The scenario's full configuration (hourly arrival rates and staffing) plus the list of supported overrides |
explain_queueing_theory |
none | none | Static textbook-level explainer on M/M/c, Little's Law, utilization, variance |
explain_advanced_patterns |
none | none | Static explainer covering six complexity patterns beyond M/M/c |
What we log per tool invocation: tool name, success/failure, duration in milliseconds, a non-reversible session hash (SHA-256 of your IP + user-agent bucket, first 16 hex chars), the user-agent bucket, the calling MCP client name (e.g. claude.ai, chatgpt, cursor, smithery), and the numerical input parameters you supplied (truncated to 1 KB). These rows go to /data/mcp-tool-calls.jsonl on the application server's encrypted volume and are automatically purged after 90 days. The session hash lets us correlate same-client repeat traffic for abuse forensics within the retention window without storing the IP itself. The input parameters are anonymous numbers (arrival rates, server counts) and do not constitute personal data.
Building a QueueSim Cloud model through an AI assistant. Three of the tools (queue_model_guide, check_queue_model, run_queue_model) check and run a model with several steps that the assistant builds from what you describe. The model is checked and run in memory and not stored; for these two tools the log row records only the number of nodes and staff groups, not the model or its names. The reply includes a link that opens the model in QueueSim Cloud; the model travels in the part of the link after #, which your browser never sends to a server.
There is no authentication, signup, account, or payment surface on the MCP endpoint. The endpoint is rate-limited per IP to prevent abuse.
1.5 Newsletter signup (only if you opt in)
- If you submit your email through the "Join our list" form on the site, we pass it to ActiveCampaign for transactional and product-update emails.
- You can unsubscribe at any time via the link in any email we send.
- The email + a signup timestamp are retained until you unsubscribe.
1.6 Analytics (Google Tag Manager + GA4)
- We use Google Tag Manager (container
GTM-NL7VDMTV) and Google Analytics 4 to count pageviews, traffic sources, and aggregate usage. GA4 collects standard browser/device fingerprints; IP anonymization is enabled where supported by the platform. - Aggregate counters (total simulations run, top tools called, total chat turns) are also exposed at /api/mcp-stats, /api/chat-stats, and /api/abuse-signals. These endpoints expose only aggregate numbers and contain no individually identifiable data.
1.7 QueueSim Cloud accounts (app.queuesim.com, subscribers only)
QueueSim Cloud’s Free plan needs no account. Only people who subscribe sign in. For them we keep:
- Email address and plan. Your sign-in email, whether it is on the Free or paid plan, the FastSpring subscription id that set it, and when it last changed.
- Sign-in codes. A 6-digit code is emailed to you through Resend. We keep only a salted hash of it, in memory, for 10 minutes. A short sign-in log records the email and time of each sign-in.
- Saved models (paid plan): the models you choose to save, with their names, until you delete them.
- Purchase events from FastSpring: event type, email, product and subscription id (no card or bank details).
- Bot check: the sign-in form uses Cloudflare Turnstile.
- Sign-ins and subscription changes are recorded with your email in our customer records (CRM) and team notifications.
Models you build without signing in stay in your own browser; they are sent to us only to check and run them and are not stored.
Through ChiAha Cloud. If you use QueueSim Cloud from an AI assistant connected to ChiAha Cloud (app.chiaha.com), ChiAha Cloud sends us your signed-in email and the model. We use the email only to look up your plan here (a QueueSim Cloud subscription on the same email gets the larger limits), check and run the model in memory, and send the results back. Neither server stores the model or logs it.
1.8 QueueSim games (Staff the Day, One Line or Four, The Cliff, Hold or Hang Up: the QueueSim games phone app and their pages on queuesim.com)
You can play without signing in, in the app or on the web page: the move you send (a schedule, your guesses, or agents and a hold limit) is scored and nothing is stored. Staff the Day and Hold or Hang Up each have their own all-time board, and the same sign-in works for both. One Line or Four and The Cliff have no board: they are scored and shown to you, and nothing from them is ever stored (no board file). To put your name on a board, you sign in with Apple in the app, or on the web page with a 6-digit code we email you. The app and the web page share one board. The board is all-time: it shows each player’s best play ever. Then we keep:
- Your board entries (
/data/staff-the-day-plays.jsonl,/data/hold-or-hang-up-plays.jsonl, one file per game with a board): the name shown on the board (first name and last initial), the company you typed, your move (the schedule, or agents and hold limit), its score, the time and the month. Each entry carries a one-way code made from your email, not the email itself. Your best play in each game is kept while your account exists, so it stays on that game's all-time board; your other plays are deleted after 90 days. Deleting your account removes them all at once. - Your app sign-in lives in a token on your phone (your email from Apple, the name and company you typed, and whether you ticked the email box). We keep no account row. Apple may give us a private relay address instead of your real one.
- On the web page, the email code: we email a 6-digit code to the address you type (sent through our email provider, Resend). We keep only a scrambled (hashed) copy of the code, in memory, until it is used or expires 10 minutes later. Once the code checks out, your sign-in lives in a token kept in your browser (local storage) for up to 180 days: your email, the name and company you typed, and whether you ticked the email box. We keep no account row. The form has a Cloudflare Turnstile bot check. Web board entries are stored exactly as app ones (above), marked as coming from the web, with the same retention.
- Sign-ins and new personal bests are recorded with your email in our customer records (CRM) and team notifications, as other ChiAha sign-ins are. Apart from the web sign-in code, you get no email from us unless you ticked the box.
- Build this for my operation (a button in the app and on the web page) sends your name, email, company, any job title you type, the play you were looking at and your best board score to our customer records (CRM) and team notifications, so we can contact you about a model of your own operation. On the web page you can send it without the email code by typing your name, company and email (with the Turnstile bot check); then we record no email-marketing consent and send you no automatic email. Nothing more is stored on queuesim.com.
- Delete my account (in the app, or “Delete my board entries” on the web page) removes your board entries in both games with a board, ends every token for your email, revokes the app’s Apple sign-in (app only), and asks our team to remove your CRM contact. Report this name on a board row sends the name (nothing about you) to our team, who can take it down.
The app has no ads and no analytics or crash-reporting tools, and does not use Apple’s advertising identifier; we may look at plays in aggregate (for example, which schedules people try).
1.9 QueueSim Builder (iPhone and iPad app)
The QueueSim Builder app runs its simulations on our server: each time you check, run or animate a model, the app sends the model to app.queuesim.com, as the web app does. The model is checked and run in memory and not stored, unless you save it. The Free plan needs no account. If you sign in (Sign in with Apple; needed before subscribing), we keep:
- Your app account (
/data/queuesim-cloud.db, separate from QueueSim Cloud web accounts): Apple’s user id for this app, the email Apple gives us (possibly a private relay address, or none), the first and last name Apple shares on your first sign-in, a random purchase id the app puts on your subscription purchases (Apple’s appAccountToken), and an encrypted Apple sign-in token we keep only to revoke it when you delete your account. - Your subscription status: the product (monthly or yearly), Apple’s original transaction id, until when it is paid, whether you are in the free week, whether it will renew, and whether it was bought in Apple’s test (sandbox) system. Apple takes the payment; we never see card or bank details or your Apple Account. Apple tells us when it renews, ends or is refunded (App Store Server Notifications); we log each notice with its type and your account’s internal id, no email (
/data/queuesim-builder-asn.jsonland/data/queuesim-builder-subscriptions.jsonl, 90 days). - Saved models (subscribers): the models you save, with their names and node and staff-group counts, until you delete them or your account.
- Sign-ins and subscription starts and ends are recorded with your email in our customer records (CRM) and team notifications, as other ChiAha sign-ins are. You get no email from us for them.
- Delete account (in the app, Account › Delete account) deletes your account row and every saved model at once, revokes the app’s Sign in with Apple, and asks our team to remove your CRM contact. It does not cancel an Apple subscription: Apple bills it, so cancel it in your Apple Account settings first.
An app subscription is not linked to a QueueSim Cloud web subscription (FastSpring), and a web subscription does not unlock the app.
2. What we do NOT collect
- No account data for the free tools. queuesim.com and QueueSim Cloud’s Free plan have no signup or login. Only QueueSim Cloud subscribers (section 1.7), QueueSim Builder app users who sign in with Apple (section 1.9) and Staff the Day players who sign in (with Apple or an emailed code) to join the board (section 1.8) have an account.
- No payment card data. QueueSim Cloud payments are taken by FastSpring, our payment partner and the merchant of record; we never see card or bank details.
- No IP address with chat content. Chat questions and answers are stored without your IP address.
- One advertising tracker, US only. The LinkedIn Insight Tag runs for visitors in the United States (see Cookies). It never runs for visitors outside the US or on signed-in app pages, and we use no other ad network.
- No cross-site tracking beyond what GA4 does for its own pageview attribution.
- No sensitive personal information. We do not request or collect race, religion, sexual orientation, health, financial, biometric, precise geolocation, or other categories defined as sensitive under California's CPRA.
3. How we use what we collect
- Run the simulator, chat, and MCP features.
- Detect and prevent abuse (rate-limit floods, scraping, validation attacks).
- Compute aggregate usage statistics (total simulations, top tools, turns per day) to inform product decisions.
- Investigate reported quality issues when a user explicitly submits a report via the Report button.
- Send you product emails if you opted into the newsletter.
- Comply with US export controls: when you sign up for QueueSim Cloud, buy a subscription or ask us to build a model, the email, name, company and country you gave us go to ChiAha's own gateway, which checks them against the US government's Consolidated Screening List. A possible match is held for a person at ChiAha to review.
Apart from the LinkedIn retargeting described in Cookies, we do not use the data we collect for advertising. We never use it for profiling or for automated decisions that produce legal or similarly significant effects on you.
4. Who we share data with
- Fly.io — hosts the application and stores logs and the encrypted volume that holds the JSONL files described above. fly.io/legal/privacy-policy
- Anthropic — processes your on-page-chat messages, and processes MCP tool invocations when you call the MCP from a Claude/Anthropic client. anthropic.com/legal/privacy
- OpenAI — if you invoke our MCP from ChatGPT, the ChatGPT App Directory, or another OpenAI platform, your inputs pass through OpenAI's pipeline before reaching us; OpenAI's privacy policy governs that leg of the journey. openai.com/policies/privacy-policy
- Other MCP clients — if you invoke our MCP from Cursor, Smithery, Glama, or any other third-party MCP client, that client's privacy policy governs its handling of your inputs before they reach us.
- ActiveCampaign — receives your email for the newsletter (only if you opted in). activecampaign.com/legal/privacy-policy
- Google (Tag Manager + Analytics 4) — receives aggregate site analytics. policies.google.com/privacy
- Apple — Sign in with Apple for the QueueSim Builder and Staff the Day apps, and the App Store, which sells and bills QueueSim Builder subscriptions and tells us their status. apple.com/legal/privacy
- FastSpring — runs QueueSim Cloud checkout and billing as merchant of record, and tells us when a subscription starts, renews or ends. fastspring.com/privacy
- Resend — delivers QueueSim Cloud and Staff the Day sign-in code emails. resend.com/legal/privacy-policy
- Cloudflare (Turnstile) — the bot check on the chat, the newsletter form, QueueSim Cloud sign-in and the Staff the Day web page. cloudflare.com/privacypolicy
We do not sell, rent, or trade your data to anyone. The US-only LinkedIn retargeting may count as "sharing" for cross-context behavioral advertising under California law; you can opt out as described in Cookies.
5. AI model training
- We do not use any of the data we collect to train AI models. The on-page chat, the MCP, the newsletter, and the analytics are not used to train Claude or any other model on our side.
- Anthropic processes on-page chat messages and MCP traffic that reaches them via Claude clients. Per Anthropic's published policy, Anthropic does not train its public models on API traffic by default. See their commercial terms.
- OpenAI processes MCP traffic that reaches them via ChatGPT or other OpenAI clients. OpenAI's data-use policy governs that traffic.
- Other MCP clients have their own data-use policies. If you connect the QueueSim MCP from a third-party client, review that client's terms.
6. Cookies
QueueSim sets first-party cookies for analytics. The only advertising cookies are LinkedIn’s, for visitors in the United States (see Your choice below).
| Cookie | Source | Purpose | Lifetime |
|---|---|---|---|
_ga |
Google Analytics 4 (via GTM) | Distinguishes unique visitors for aggregate analytics | ~2 years (Google default) |
_ga_<property-id> |
Google Analytics 4 (via GTM) | Session state for GA4 | ~2 years (Google default) |
LinkedIn cookies (for example li_sugr, bcookie, lidc) |
LinkedIn Insight Tag (via GTM), US visitors only | Retargeting on LinkedIn and ad measurement | Up to 1 year |
cf_chl_*, cf_clearance (occasional) |
Cloudflare Turnstile (anti-bot for the chat endpoint) | Verifies the chat POST originates from a browser rather than a scripted client | Session / short-lived |
qsc_session |
QueueSim Cloud (app.queuesim.com, only after you sign in) | Keeps a subscriber signed in. Strictly necessary; holds your email and a signature, nothing else | 30 days, or until you sign out |
Browsers in the EU/UK that have not signaled consent for analytics cookies may still receive standard server-log telemetry (IP, UA) but the GA4 cookies will not be set.
Your choice
Advertising cookies are off by default for every visitor, with one exception: visitors in the United States get the LinkedIn Insight Tag, 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 on signed-in app pages, 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.
Analytics cookies are handled by region. If you are visiting 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 we record only an anonymous, cookieless page count that cannot be linked to you or to any later visit. Either answer is stored in a single strictly-necessary cookie (chiaha_consent) for twelve months, and you can change it at any time using the Privacy settings link in the footer of any page.
If your browser sends a Global Privacy Control or Do Not Track signal, we detect it and disable analytics and advertising cookies automatically, without asking you.
7. Retention
Durable QueueSim-side logs are automatically aged out via a background retention service that runs every 24 hours. The 90-day window is enforced by code, not just promised. QueueSim Cloud subscriber accounts are the exception: they are kept while the account exists (last rows below).
| What | Where | Retention |
|---|---|---|
| HTTP access logs (IP, UA, path, status) | Fly.io platform logs | Up to 90 days (Fly's standard log window) |
| Site-event JSONL (per page hit + simulation run) | /data/site-events.jsonl |
90 days, enforced by retention cron |
| MCP tool-call JSONL (per tool invocation, includes anonymous tool inputs) | /data/mcp-tool-calls.jsonl |
90 days, enforced by retention cron |
| Chat-history JSONL (aggregate metadata only — no message content) | /data/chat-history.jsonl |
90 days, enforced by retention cron |
| Chat questions and answers (no IP address) | ChiAha operations server | Up to one year, then deleted automatically. To have yours deleted sooner, email queuesim@chiaha.com. |
| Reports (user-submitted chat content via the Report button) | /data/reports.jsonl |
90 days, enforced by retention cron |
| QueueSim games board entries (games app and web page; board name, company, your move, score, a one-way code from your email) | /data/staff-the-day-plays.jsonl, /data/hold-or-hang-up-plays.jsonl (One Line or Four and The Cliff have no board and store nothing) |
Your best play: while your account exists (it is the all-time board). Your other plays: 90 days, enforced by retention cron. All of them at once when you delete your account in the app. |
| In-memory rate-limit state and counters | Application memory | Resets on every server restart |
| Newsletter subscriber list | ActiveCampaign | Until you unsubscribe, after which the address is suppressed |
| GA4 aggregate analytics | Google Analytics property 433243670 | 14 months (configured GA4 default) |
| QueueSim Cloud account (email, plan, subscription id) and saved models | /data/queuesim-cloud.db |
While the account exists. Saved models until you delete them. Email queuesim@chiaha.com to delete your account and everything in it |
| QueueSim Cloud sign-in log and FastSpring purchase events | /data/queuesim-cloud-*.jsonl |
While the account exists, as the record of who has the paid plan and why |
| QueueSim Builder app account (Apple user id, email from Apple, name, subscription status) and saved models | /data/queuesim-cloud.db |
While the account exists. Saved models until you delete them. Delete account in the app removes everything at once |
| QueueSim Builder subscription notices from Apple (type, product, internal account id; no email) | /data/queuesim-builder-*.jsonl |
90 days, enforced by retention cron |
8. Your rights and how to exercise them
Because we do not link logs to an identity, there is usually nothing to "delete" beyond what ages out automatically: server logs within 90 days, chat questions and answers within one year. If you want to exercise a specific right, email queuesim@chiaha.com and include:
- What action you want. Common options: access (a copy of any data we hold on you), deletion, correction, opt-out of analytics, unsubscribe from the newsletter.
- Any identifier we'd have on file. For newsletter requests, that's your email. For chat or MCP requests, that's the approximate date/time (in UTC if possible) and either the IP you were using or a phrase from a message you remember sending — we can grep the relevant JSONL.
We respond within 5 business days. If you submitted a chat Report via the chat widget and want it withdrawn, include the approximate timestamp and the scenario you were on (e.g. "Coffee Shop, May 15 around 2pm Eastern") — the session hash plus the timestamp lets us find your specific row in /data/reports.jsonl and remove it.
9. International users (GDPR, UK GDPR)
QueueSim is operated from the United States. If you are accessing it from the European Economic Area, the United Kingdom, or another jurisdiction with similar data-protection laws, your data is transferred to and processed in the United States.
Our lawful bases for processing (under GDPR Article 6) are:
- Legitimate interest — for operational telemetry, rate limiting, abuse prevention, and aggregate analytics. The interest is operating the free service securely and improving it; we minimize what we collect to what's needed for those purposes.
- Consent — for newsletter signup (you submit the form) and for chat reports (you click Submit on the modal). You can withdraw consent at any time by emailing us or unsubscribing.
- Contract performance — not applicable; there is no contract because there is no account.
You have the rights of access, rectification, erasure, restriction, portability, and objection. See Section 8 above for how to exercise any of these. If you are not satisfied with our response, you have the right to lodge a complaint with your local data-protection authority.
10. California users (CCPA / CPRA)
If you are a California resident:
- Categories of personal information we collect: identifiers (IP address; the name, email and company you give when you sign in to the Staff the Day board, in the app or on the web; Apple’s user id, email and name for QueueSim Builder app accounts; your sign-in email for QueueSim Cloud), internet/network activity (user agent, request paths, GA4 cookies, and LinkedIn cookies for US visitors), and inferences drawn solely from aggregate usage patterns. We do not collect any sensitive personal information as defined under CPRA.
- Sources: directly from you (newsletter, sign-in, simulation inputs, chat messages, reports) and from automated server logs (IP, UA, timestamps).
- Purposes: see Section 3 above.
- Sale or sharing: we do not sell 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: you have the right to know, to delete, to correct, to limit use of sensitive personal information (not applicable since we collect none), and to opt out of sale or sharing (see above). To exercise any of these, email queuesim@chiaha.com.
11. Children's privacy
QueueSim is not directed to children under the age of 13. We do not knowingly collect personal information from anyone under 13. If you are a parent or guardian and believe your child has provided us with personal information, contact us at queuesim@chiaha.com and we will delete it.
12. Security
Infrastructure runs on Fly.io with TLS terminating at the edge and encrypted persistent volumes. There are no user passwords to compromise. Staff the Day board players, QueueSim Builder app users and QueueSim Cloud subscribers have accounts, but sign-in is by Apple or by a code we email you. The MCP and chat endpoints are rate-limited; the chat endpoint is additionally budget-capped. The retention service automatically purges rows older than 90 days from durable storage (the one exception is each Staff the Day player’s best board play, kept while their account exists; section 1.8). We do not make HIPAA or SOC 2 claims because we do not collect the kind of data those frameworks govern.
13. Changes to this policy
If we make material changes, we'll update this page and revise the "Last updated" date above. The free tools have no accounts, except the optional board sign-in for Staff the Day, and we do not notify those players individually; check back occasionally if it matters to you.
14. Contact
Questions, requests, or concerns: queuesim@chiaha.com. We aim to respond within 5 business days. Mailing address available on request.