Dataset operations stay in the browser
Imports, queries, record changes, and exports are processed by local JavaScript. The demo does not send dataset contents to a server, language model, analytics endpoint, or live data connector. The online website still requires ordinary requests to the host to load its files.
Browser storage is not a backup
The full demo uses best-effort localStorage for workspace state and saved query preferences. Storage policies, quota limits, private browsing, or clearing browser data may remove it. Export a complete JSON workspace to retain your data and history.
The small homepage preview is independent and memory-only. Its edits are discarded when you leave or reload the page; it does not modify your full demo workspace.
Application views are previews
Support and Billing views filter record types and properties in the interface. A relationship is hidden when any of its participants is hidden, and raw source payloads are suppressed in those views.
These controls are not authentication, authorization, or tenant isolation. The browser user can inspect the complete local dataset using developer tools. Use only synthetic or non-sensitive test data.
History and sources have a defined scope
Accepted changes create new local snapshots. Existing source snapshots are not rewritten by later edits. The demo checks model constraints and prevents a failed import from partially committing.
Those behaviors do not imply distributed durability, independent truth verification, cryptographic provenance, or compliance certification. The query engine is a reference implementation, not a production service benchmark.
No background tracking is installed
This website build includes no advertising pixels, third-party analytics scripts, remote fonts, or automatic lead-collection forms. Hosting-layer request logs are separate from application behavior and depend on the deployment configuration.
Read the local data notice for storage and deletion details, or the demo guide for practical limits.