Know where your data goes.
This page describes how the current BotSims application handles information. Optional cloud AI requests have a different data path from your locally saved robot projects.
Last updated: 24 October 2026
Who operates this project
The project is presented as BotSims project. A separate legal entity, postal address and privacy contact have not been published in this application. Use the contact page to send a question to the private administrator inbox. No location-specific legal entitlement or compliance certification is claimed here.
Information used by the application
| Registered profile and access role | Railway persistent database. | Your verified Google identity, email, display name, role, plan/status fields and timestamps. Administrative access is derived on the server; members cannot grant themselves that role. |
| Information | Where it goes | What to know |
|---|---|---|
| Robot projects and modules | Browser local storage; files when you export them. | Parts, wires, controller source, names, objectives and configuration may be included. Clearing site data can remove local work. |
| Workbench preferences | Browser local storage. | Panel layout, assembly settings and related interface choices help restore your workspace. |
| Dedicated AI API key field | Current tab memory; site's server and selected provider for an explicit cloud request. | The application excludes this field from projects, modules, reports and action traces. Reloading or changing provider clears it. |
| AI action observation | Selected provider, through the same-origin server proxy; or directly to local Ollama when chosen. | Reduced sensor values, battery values, named servo angles, objective and optional rendered camera image. Project source and microphone audio are not attached by this connector. |
| Model discovery | Selected provider through the proxy, or direct local Ollama. | Uses the current key where required; does not send the robot objective, sensor readings or camera frame. |
| Contact request form | Draft in browser memory; submitted request in the application persistent database. | Topic, subject, message, verified sender identity, status and timestamps. Only authorized administrators can list and update support requests. Copy/download creates a separate local file or clipboard copy. |
| Application assets | Browser HTTP cache and the versioned PWA cache where supported. | These retain an informational offline page and selected public assets, not authenticated page HTML, API responses or project data. They are separate from browser-local projects. |
Google sign-in, accounts and hosting
BotSims uses Google OpenID Connect for login and registration. We verify Google's signed identity response and store your Google identifier, verified email, display name and free account status. We never collect your Google password or retain Google access or refresh tokens.
A random session token is held in a Secure, HttpOnly, SameSite=Lax cookie for up to seven days. Only its hash is stored on the server. Signing out revokes the current session. A separate ten-minute cookie binds the one-use sign-in state, PKCE verifier and nonce to your browser.
The website runs on Railway. Account, session and support records are stored in its persistent database volume. Authorized administrators can review support submissions and membership records. Robot projects remain in browser storage unless you explicitly export or share them; account registration does not upload them.
Subscription fields prepare future features. No checkout, paid subscription or card storage is active. To request access to or deletion of server records, use the privacy topic on the contact page.
Optional AI services
Live AI is optional. The offline action fixture does not need a provider key. If you choose a cloud provider, its own retention, billing, geographic availability and account rules apply. A provider's model catalogue can include models that do not support this simulator's action format.
The application does not persist the dedicated key field or log it in application code. This does not imply that browsers, hosting infrastructure or providers never retain operational information. The hosting and access layer may process request metadata such as IP address, user agent and access events under its own policies.
Do not put API keys or other secrets into source code, component names, objectives, model IDs or contact messages. Those ordinary content fields can appear in saved projects, exports, observations or feedback. Learn the exact request contents in the AI connector guide.
Cookies, analytics and access
BotSims does not currently include application marketing analytics, advertising pixels or application advertising cookies. The hosting infrastructure may use its own essential cookies and session mechanisms; they are not controlled by the simulator's local project settings.
Installing the PWA does not create a cloud project account or a durable server backup. Access can still require the site's existing sign-in and audience permissions. See Cookies and local storage for practical controls.
Your controls and retention
You can update your profile display name on the account page. Clearing browser data does not delete database profile, Google-link or support records. To request access, correction or removal of a server record, send a privacy request through Contact with its request ID where relevant. Administrative review is required; no automatic deletion deadline or fixed retention period is promised.
- Use Export project and Export module to keep copies of work you want to retain.
- Clear the dedicated key field, change provider or close/reload the tab to discard the in-memory key.
- Clear site storage in your browser to remove local projects, module presets, preferences and caches. Export needed files first.
- Uninstalling an installed PWA may not clear its browser storage. Check the browser's site-data controls separately.
- Delete exported files and shared copies through their actual storage locations or recipients. Clearing this website does not remove those copies.
No fixed retention period for operational hosting logs or third-party provider records is promised by this application. For information held by those services, consult the service's published controls and policies.
Updates and questions
This notice reflects the current application described above. New cloud storage, analytics, account features or media integrations require corresponding updates to the data explanation. The date at the top identifies this version.
Use Contact to send a privacy question. Include the type of data and the service involved, without sending credentials or confidential content.
Turn an idea into a working model.
Start from a robot preset or bring your own design to the workbench.