A clear view of what stays on your device.
BotSims uses browser storage to restore your work and interface preferences. That is different from an optional AI request, an exported file or your secure BotSims sign-in session.
Last updated: 24 October 2026
What the application stores
| Storage | Purpose | How to control it |
|---|---|---|
| Project local storage | Restore the current assembly, connections, source code and project configuration. | Export your project before clearing browser site data. |
| Module library local storage | Retain your saved reusable component groups. | Export modules individually for a portable backup, or delete a saved module in the library. |
| Interface preferences | Remember panel visibility, assembly tool settings and related local UI choices. | Change the controls in the workbench, or clear site data. |
| HTTP and PWA asset caches | Retain selected static application resources and an informational offline page. Authenticated page HTML and API responses are not cached by the worker. | Use browser site-data controls; uninstalling an app and clearing data are separate operations in some browsers. |
| Authentication cookies | A secure session cookie lasts up to seven days. A sign-in flow cookie expires after ten minutes. | Sign out from your account to revoke the session, or clear cookies through browser settings. |
BotSims does not currently add marketing analytics, advertising cookies or tracking pixels in application code. Hosting services may use essential cookies or operational mechanisms under their own policies. This page is not a claim that the complete hosting infrastructure sets no cookies.
What is not saved in local storage
The dedicated AI API key field remains in the current tab's memory. It is cleared by reloading or changing provider and is excluded from application project/module exports and action traces. Do not place a key in ordinary source, objectives or names; those fields are ordinary saved project content.
Contact drafts remain in page memory until submission. Submitting stores the message and verified sender identity in the application's database. Profile, support and optional Google-link records are server records; clearing browser storage does not remove them.
Google sign-in stores random, HttpOnly cookies for the session and short-lived login flow. Only session token hashes are stored on the server. Sign-out revokes the current session. Profile and support records remain until separately deleted.
Clearing data safely
- Export every project and module you need to retain. Download any experiment reports or action traces you want to keep.
- Open your browser's settings for this website's stored data, permissions and cookies.
- Clear the data you intend to remove. Local projects, modules and preferences may be lost together.
- Reload the website and import the exports you want to restore.
Browser names and menu locations vary. Private browsing, limited storage or blocked cookies/storage can prevent automatic restoration. BotSims cannot recover files you never exported after local data has been removed.
More information
Read the Privacy policy for optional AI requests and provider data flows, or the saving guide for practical import/export steps. Use Contact to send a question about a specific storage behavior.
Turn an idea into a working model.
Start from a robot preset or bring your own design to the workbench.