All privacy policies About TrafficLab+
TrafficLab+ — Privacy Policy
Effective date: October 31, 2026 (version 1.1.0).
Who we are
This policy covers TrafficLab+, a Windows desktop application published on the Microsoft Store by Dean Eaglin ("we", "us"), the publisher named on the app's Store listing. Contact: ron.eaglin@gmail.com.
Summary
TrafficLab+ turns a real intersection, or a corridor of them, into a web page with a live traffic simulation: a puzzle a student solves with a budget. You find the intersection on a map, the program brings in its roads, you set the traffic and the challenge, and it builds the page.
Your studies stay on your computer, and we never receive any of them. There are no accounts with us, no advertising, no analytics and no telemetry of any kind. The app sends nothing to us, ever.
TrafficLab+ provides features that use the internet, and requires none of them: the map and its roads (OpenStreetMap), place search (Nominatim), traffic counts for Florida roads (the Florida Department of Transportation), the AI features (the AI provider whose key you entered), publishing your pages (GitHub), checking for a new version (the Microsoft Store, only when you choose Help ▸ Check for a new version), and opening help pages and links in your web browser, each only when you use it. The pages TrafficLab+ makes send nothing anywhere. All of this is described in full below.
What we collect
Nothing. No personal information, no usage or diagnostic data, no device identifiers, no location. The app has no account of ours to sign in to and no in-app purchases, and we operate no server that TrafficLab+ talks to.
Your studies, and where they stay
Everything you make is written only to your own computer:
Documents\TrafficLabPlus\Studies— your studies (.trafficlab), unless you save them somewhere else. Each is an ordinary zip file holding the study, your notes, and — when you used them — the roads OpenStreetMap returned and the counts FDOT returned, so an opened study never asks for them again.Documents\TrafficLabPlus\Preview— the page built for the preview inside the app, rebuilt as you work.%LOCALAPPDATA%\TrafficLabPlus— the list of studies you opened recently, your settings (the author and course to fill in), and the working files of the built-in web view (see "The page and the map inside the app").Documents\AiManager— your AI settings, if you use the AI: your API keys (encrypted, see below), a log of what the app did, and a ledger of AI requests so the app can show you what you have used. The ledger records the date, provider, model, purpose and token counts of each request. It does not keep the text you sent.
None of it is uploaded or synchronised anywhere by the app, and none of it ever comes to us.
Uninstalling TrafficLab+ does not delete your studies: they are your files, and they stay until
you delete them. (When TrafficLab+ is installed from the Store, Windows may keep the
%LOCALAPPDATA% files under %LOCALAPPDATA%\Packages instead.)
The pages you hand out, and your players
A page made with TrafficLab+ is a single web page that runs entirely in the player's browser. It loads nothing from the internet (no fonts, no maps, no scripts from anywhere), contains no advertising or tracking, stores nothing on the player's device, and sends nothing anywhere — not to you, not to us, not to anyone.
- A player's name is optional. The page asks for it so it can be printed on the player's printout. It stays in that page, on that device, and is gone when the page is closed.
- The printout — the player's plan, its score and the traffic results — is made on the player's device. It goes anywhere only if the player prints it, saves it as a PDF, or hands it in themselves.
- The page's footer says "Created with TrafficLab+ · SoftwarePlus.ai", with a link to each (and "Road data © OpenStreetMap contributors" when the roads came from OpenStreetMap). The links are plain links: nothing is loaded from them unless the player clicks one, which opens that site in the player's browser.
- Where the pages live is up to you: e-mail, your learning management system, web space you control, or GitHub Pages. Whoever hosts a page is responsible for that hosting; a page on GitHub Pages is served by GitHub, under GitHub's terms and privacy statement.
The map, and the roads from OpenStreetMap
The Map step shows a map of the world and brings in the roads of the place you choose, from OpenStreetMap, a free map made by volunteers, run by the OpenStreetMap Foundation.
- The map pictures (tiles) are loaded from
tile.openstreetmap.orgwhile the Map step is open, as any web map loads them. OpenStreetMap's servers see an ordinary request from your computer (its address, and which part of the map is shown). - Search sends the words you type (a street and a town, for example) to
OpenStreetMap's place search, Nominatim (
nominatim.openstreetmap.org), only when you press Search. - Loading the roads sends the corners of the area shown on the map to
OpenStreetMap's road service, Overpass (
overpass-api.de, oroverpass.kumi.systemswhen the first is busy), only when you press Load the roads. The answer is the public road data for that area, kept in your study. - Every request says it comes from TrafficLab+, as OpenStreetMap's usage policies ask. Nothing else is sent: not your study, not your name. What OpenStreetMap does with these requests is governed by the OpenStreetMap Foundation's privacy policy, not by this one.
Traffic counts from FDOT
For a study in Florida made from the map, Look up FDOT counts for these roads sends the
corners of the study's area to the Florida Department of Transportation's public
traffic-count map, hosted by Esri ArcGIS (services1.arcgis.com), only when you press
that button. The answer is FDOT's published counts for that area, kept in your study. Nothing else
is sent. What FDOT and Esri do with the request is governed by their own policies.
The AI features, and your API key
TrafficLab+ has no AI of its own and no AI subscription bundled with it. To use an AI feature you supply your own key for the provider you prefer — Anthropic (Claude), Google (Gemini), OpenAI, Mistral or xAI.
- Nothing is sent unless you ask for it. The AI features are buttons, each saying it uses AI: Fill in with the AI (the network), Estimate traffic with the AI, Write the challenge with the AI, and Ask the coach about a traffic test. The app sends nothing in the background.
- What is sent is what that one request needs: the words you typed in that window, and a description of the study — its title and place, its intersections and roads (names, lanes, speeds, signal timing, turn lanes), its traffic volumes, its budget and the prices of the fixes. For the coach, also the results of your last traffic test on the page. Your notes, your other studies and any player's name are never sent.
- Where it goes. Directly from your computer to that provider's API. It does not pass through any server of ours, and we cannot see it.
- What comes back is never used without you. Every change the AI proposes is shown with its reason and applied only if you tick it and press Apply; one undo takes it back. The coach only explains; it changes nothing.
- What happens to your request at the provider is governed by that provider's terms and privacy policy, not by this one. Providers differ on whether they retain prompts, for how long, and whether they use them for training. Read the policy of the provider whose key you use.
- Your key is stored on your computer, encrypted with the Windows Data Protection API under your Windows user account, so another user of the same PC cannot read it. It is sent to that provider, and to nobody else. You can remove it at any time in the app's AI settings. The same key store is shared with other apps from the same publisher that you may have installed, so a key entered in one works in the others.
Publishing to GitHub Pages
When TrafficLab+ offers Publish, it puts your pages on GitHub Pages, GitHub's free web hosting, in one repository on the GitHub account you name, with a summary page linking to each study. Nothing is published unless you press Publish, and a study you mark "Don't publish" is never sent.
- What is sent to GitHub: the pages of your studies, the summary page, and a
small file saying the site was made by TrafficLab+. Your
.trafficlabfiles, your notes, your AI settings and the OpenStreetMap and FDOT answers kept in your studies are not sent. - A published page is public. Anyone with the address can open it. Do not put anything in a study you would not put on a public web page.
- Your GitHub token, if you save one, is stored on your computer, encrypted with the Windows Data Protection API under your Windows user account, and is sent only to GitHub. You can remove it at any time in the app, and revoke it on GitHub.
- Without a token, TrafficLab+ publishes with Git for Windows, if it is installed on your computer: Git sends the pages to GitHub, and if GitHub asks you to sign in, Git's own sign-in window (Git Credential Manager) handles it. TrafficLab+ does not see or keep your GitHub password.
- What GitHub does with your account and repositories is governed by GitHub's terms and privacy statement, not by this policy.
Until then, Save the page as a web page file writes the page to a folder you choose on your computer, and sends nothing.
The page and the map inside the app
TrafficLab+ shows the page you are building, and the map, inside its own window using Microsoft Edge WebView2, the web engine built into Windows. The page view shows only the page TrafficLab+ has just built on your computer; the map view loads the map pictures described above. WebView2 is a Microsoft component, and any information it shares with Microsoft follows your Windows settings and Microsoft's privacy statement, not this policy. Open in your browser opens the page in your own web browser, under that browser's settings.
Help, and links that open your browser
Help for each screen (the link at the top of a screen, or F1) and the links in Help ▸ About — the TrafficLab+ page and this policy on softwareplus.ai, the TrafficLab+ page on the Microsoft Store, and the list of all the programs — open in your own web browser, only when you click them. The program sends nothing with them; the website sees an ordinary visit from your browser.
Checking for a new version
Help ▸ Check for a new version asks the Microsoft Store, run by Microsoft, whether a newer TrafficLab+ is published, only when you choose it. If there is one and you say yes, the Store downloads and installs it. Nothing about your studies is sent. A copy not installed from the Store cannot ask, and offers to open the TrafficLab+ page on the Store instead. Microsoft's privacy statement covers the Store: privacy.microsoft.com.
Network use
TrafficLab+ connects only for what you ask: OpenStreetMap's map pictures while the Map step is open, its search when you press Search, and its road service when you press Load the roads; FDOT's count map when you press Look up FDOT counts; the API of the AI provider whose key you entered, when you press an AI button (and to list that provider's models); and GitHub, when you publish; the Microsoft Store, when you choose Help ▸ Check for a new version; and your web browser, when you open help or a link. It does not check for updates on its own, report errors, or contact us. The Microsoft Store also handles installation and updates on its own, as it does for every Store app.
Permissions
The Store package declares runFullTrust, the standard capability for any full desktop
(Win32) application, which is what lets TrafficLab+ read and write your own study files through
ordinary Windows file access, and internetClient, which is what lets it reach the
services above. It is not used to reach any other application's data, and TrafficLab+ never needs
administrator rights.
Third parties
Only these can receive anything from TrafficLab+, chosen by you and only as described above: the OpenStreetMap Foundation's servers (map pictures, search, roads), FDOT's count map on Esri ArcGIS, the AI provider whose key you entered, and GitHub, when you publish. Microsoft provides the WebView2 component and operates the Store you downloaded TrafficLab+ from, which also answers Check for a new version; Microsoft's own privacy statement covers these.
Retention and deletion
Because nothing is stored on any computer but yours, there is nothing for us to retain or delete. Deleting your studies, or uninstalling the app, removes what it holds on your machine. Anything you sent to an AI provider is held, or not held, under that provider's policy; ask them. A page you published stays on GitHub until you delete it there.
Children
TrafficLab+ is a tool for instructors and students, usually at a university. The pages it makes are built so that they collect nothing: a player's name is optional, stays on their own device, and leaves it only on a printout they choose to hand in. Neither TrafficLab+ nor its pages collect information from anyone, so they collect none from children.
Changes to this policy
Updates will be posted on this page with a new effective date. If a future version of the app does something this policy does not describe, this page will say so before that version ships.
Contact
Dean Eaglin — ron.eaglin@gmail.com