1. The short version
The Lot is a Windows application published by Wigley Studios LLC. It puts the software you already use — your logged-in Claude, ChatGPT, Cursor and anything else you name — onto screens inside a 3D world, with a secretary who runs your instructions on them. This policy covers the desktop application and the parts of wigleystudios.com/thelot that serve it.
Wigley Studios receives one thing from The Lot: a bug report you pressed a button to send. There is no telemetry, no analytics service, no crash beacon and no phone-home. Everything else the app does either stays on your machine or goes to a provider you configured yourself, for something you asked for in that moment.
Every honest description of this app reads a little like a description of malware, because putting your real software inside a game engine requires real access. The rest of this page is that access, itemised, with the limit on each one — the same list the app's own README gives you before you install it.
2. What the application does on your computer
All of this happens locally. None of it produces data that reaches Wigley Studios.
config\pinned_apps.json, and the image is handled on the GPU. Nothing is uploaded, ever — not to us, not to anyone.
localhost. That connection never leaves your machine and is not reachable from your network.
3. What leaves your machine
The entire list. The first three exist only if you configured them; the fourth is off when voice is off; the fifth happens only when you press a button.
There is no sixth host. Every host above serves something you asked for at the moment you asked for it, and none of them is contacted on a schedule, at startup, or in the background.
The web screens are a real browser
Some in-world screens are web pages rather than mirrored applications, drawn by an embedded Chromium browser. When you use one it behaves exactly like a browser: it connects to whatever site you open, and that site sets cookies, keeps you signed in, and sees you the way it would in Chrome. Those connections are yours and are governed by the privacy policy of the site you visited. Your in-world browsing profile — cookies, sessions, local storage — is written to disk next to the application and never transmitted to us.
A default set of tabs ships with the app so the world is not empty on first run. Opening one is a normal visit to that site; removing it stops that.
4. Your voice stays here
Speech-to-text runs entirely on your own CPU, using a local faster-whisper model. The model files ship inside the download, so the app has nothing to fetch and does not contact the model host at all in a released build. Audio captured while you hold F9 or F10 is transcribed in memory and discarded; it is not written to disk, and it is not sent anywhere.
One deliberate detail: the model loader is pinned to local files whenever the model is present, because the underlying library otherwise checks the model host for a newer revision on every single load — a network call nobody asked for, against a file already on disk. The host list above is a promise, and that was the one place it could have quietly become untrue.
5. Bug reports — the one thing we receive
Press F11 in the app, or accept the crash offer after a crash, and you get a form. Nothing is sent until you submit it, and the form shows you the contents first. A report contains exactly these fields:
- What you wrote — a category, a one-line summary, and an optional longer description.
- An email address, only if you type one. It is optional, it is used to reply to you about that report, and it is used for nothing else — no mailing list, ever.
- Which build — version, commit and build date.
- Where you were — the environment you were in and your position and camera angle in it, so the bug can be walked to.
- What the app was doing — input mode, whether the world was idle, frame rate, how long the session had been running, and a small block of context and performance data.
- What you were running it on — GPU model, Windows version and screen resolution.
- A screenshot, rendered with the screen surfaces deliberately culled, so the contents of your actual applications are not in the picture.
- Your IP address, recorded with the report and used to rate-limit abuse of the endpoint.
Reports are stored on our server in a location the web server cannot serve, and are readable only through an authenticated administrative view. They are used to fix the software and for nothing else. They are not sold, not shared, not used for advertising, and not fed to any third party. We keep them while the issue is open and for up to 24 months afterwards, so that a bug which comes back can be matched to the last time it happened; ask and yours will be deleted sooner.
The screenshot is culled on your machine before it is sent, not on ours. That is the honest version: our server stores what it is handed and does not attempt to verify what is in it. If a report would embarrass you, don't send it — describe the bug in words instead. The form's whole purpose is to let you see that decision before you make it.
6. The download page
The playtest build is behind a password. When you submit it, our server checks the password and records your IP address in its request log, which is used to rate-limit guessing and is retained for up to 30 days. No account is created, no cookie is set for the download itself, and nothing about your machine is collected.
The rest of wigleystudios.com — including this page — is covered by the site-wide privacy policy and the cookie policy, which describe the site's analytics and your consent controls. The application itself uses none of that.
7. What is stored on your own machine
Everything the app remembers lives next to the executable, in plain files you can read, edit or delete:
config\
Which apps exist and where they sit, which world you are in, where you were standing, your key bindings and preferences. Delete a file to reset that part; it is written fresh on the next launch.
orchestrator\.env
Your API keys. Pasted by you, stored in one plain file on your own disk, sent only to the provider each key belongs to. Wigley Studios never receives them and has no mechanism that could.
orchestrator\data\
The secretary's memory of your conversations, so she is not a stranger every morning. Local, and yours to delete.
Screenshots\, Logs\
Your own captures, and diagnostics. Logs are read by nobody unless you attach one to a bug report yourself.
Uninstalling with the installer removes the application and its logs but deliberately leaves config in place, so an upgrade does not throw away your room. To remove everything, delete the folder afterwards.
8. Your rights, and how to use them
Because the only record we hold is a bug report you chose to send, exercising your rights is unusually simple: email support@wigleystudios.com and say what you want.
- Access — we will send you every report we hold that is linked to you.
- Deletion — we will delete them, including screenshots.
- Correction — we will fix anything inaccurate.
- Objection and restriction — you can tell us to stop using a report at any time.
These apply whether or not the law where you live grants them; the GDPR (where our lawful basis is legitimate interest in fixing the software you are testing, and consent for the optional email address) and the CCPA/CPRA both do. We do not sell or share personal information, and never have. We respond within 30 days.
The Lot is not for children. It is a developer tool that installs system-level components and drives your real accounts; it is not directed at anyone under 16, and we do not knowingly collect anything from them. If a report reaches us from a child, tell us and it will be deleted.
9. This is a playtest build
The Lot is pre-release software distributed to a small invited group. Two consequences worth stating plainly:
- Behaviour changes between builds. This page carries the build number it was written against, and is updated when the answer changes — not when the wording could be nicer.
- If a future build ever adds a host to §3, that is a change to this policy and it will be announced in the release notes and the in-app README, not slipped in. The commitment is specifically that the list stays checkable.
10. Contact
Wigley Studios LLC, Georgia, United States — support@wigleystudios.com.
If something in this policy does not match what the application actually does, that is a bug in the policy and it is worth reporting like any other. It will be fixed and the change noted.