Item
Bot base data (name/status/metadata)
Canvas (nodes/edges/variables)
Telegram token / service secrets
Runtime test logs
Audit events (save/start/stop)
Runtime variables / waiting states
UI preferences (panel sizes, toggles)
Data and security
Data and security
Where data is stored
Data and security
Where data is stored
Data Storage and Security
Where and how your data is stored: what is permanent, what gets deleted after execution, how to find things in Supabase, and important security limits.
Where
Internal project storage
Bot configuration storage
Protected secret storage (encrypted)
Logs panel + service log storage
Service event storage
Runtime process memory (partially temporary)
Browser localStorage
Persistence
Persistent
Persistent
Persistent
Persistent when log write succeeds
Persistent
Temporary
Local per browser
Visibility
Visible in Bots and editor header
Visible in Canvas/System after Save
Only secret presence is visible in UI
Visible in UI logs panel
Used by system/admin tooling
Usually not directly visible in UI
Local in current browser only
Notes
General bot state and metadata.
Stored as a config payload, not separate rows per node.
Protected server-side storage for sensitive values.
Useful for troubleshooting and support workflow.
Useful for troubleshooting and support.
Can reset on process restart until persistent runtime storage is added.
Safe for non-secret UI preferences.
Documentation navigation
Move through pages step by step as a guided learning path.