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
  2. What we do NOT collect
  3. How we use what we collect
  4. Who we share data with
  5. AI model training
  6. Cookies
  7. Retention
  8. Your rights and how to exercise them
  9. International users (GDPR, UK GDPR)
  10. California users (CCPA / CPRA)
  11. Children's privacy
  12. Security
  13. Changes to this policy
  14. Contact

1. What we collect

1.1 Operational telemetry (every visitor)

Every HTTP request to queuesim.com generates standard server logs:

1.2 Simulation inputs you submit at / or /models/{id}

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:

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.

ToolRequired inputsOptional inputsReturns
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)

1.6 Analytics (Google Tag Manager + GA4)

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:

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:

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:

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

3. How we use what we collect

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

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

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).

CookieSourcePurposeLifetime
_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).

WhatWhereRetention
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:

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:

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:

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.