Botkeep is currently a local frontend prototype. This document separates current behaviour from production commitments so it does not claim processing or safeguards that are not active yet.
1. Scope and default
This policy covers cookies, localStorage and similar access to information on a user’s device. The current Botkeep frontend does not set advertising, analytics or profiling cookies; does not fingerprint devices; and does not automatically load third-party embeds. Instrument Sans and IBM Plex Mono are served locally.
Only storage used to provide a feature requested by the user, preserve the local prototype or remember the privacy notice is active. These necessary tools do not require consent under the applicable cookie rules, but they remain disclosed here.
2. Current inventory
The prototype password and any secret value typed into the wizard are not stored in these records. A secret is replaced by a fixed mask before the workspace is saved.
| Name | Technology | Purpose | Duration | Consent |
|---|---|---|---|---|
| botkeep_cookie_preferences_v1 | First-party localStorage | Records notice version, necessary-only status and expiry so the notice is not repeated improperly | Up to 180 days | Not required; technical preference record |
| botkeep_prototype_user | First-party localStorage | Keeps the local demo session and non-sensitive demo profile available between pages | Until sign-out or browser deletion | Not required; requested account feature |
| botkeep_prototype_store_v1 | First-party localStorage | Stores simulated bots, files, deploys and interface settings in this browser | Until prototype reset or browser deletion | Not required; requested prototype workspace |
| botkeep_legal_acceptance_v1 | First-party localStorage | Records the legal-document versions acknowledged during local demo registration | Until browser deletion | Not required; requested account-registration step |
3. Categories not currently used
- Preferences beyond the privacy notice: not used.
- Audience measurement or analytics: not used.
- Advertising, cross-site tracking or profiling: not used.
- Automatically loaded social-media, video, map or scheduling embeds: not used.
4. Notice and choices
The first-visit notice explains that only necessary local storage is active. “Continue with necessary only” records that fact; it is not consent to analytics or marketing. The settings panel remains available from every public footer and identifies inactive categories.
If Botkeep introduces a non-technical tool, it will remain blocked until a valid choice is made. Accept and reject controls will have equal prominence, optional purposes will be separate, no box will be preselected and withdrawal will be as easy as acceptance.
5. Delete or change browser data
Use “Cookie settings” to reopen the notice. Sign out to remove the prototype session and use “Reset demo” in Account to restore the local workspace. Browser settings can remove all Botkeep site data. Blocking all storage prevents the prototype from remembering sessions, bots and choices but public legal information remains available.
6. External links and server logs
External services receive no request from the frontend until the user selects an external link. After leaving Botkeep, the destination provider applies its own storage and privacy rules. Ordinary web delivery may generate IP-based server logs, but that processing does not itself authorise storage on the user’s device.
7. Updates and contact
The inventory must be checked before every release that changes scripts, embeds, authentication or hosting. Questions may be sent to info@movara.it; formal communications to mosrls@pec.cgn.it.