What the browser saves

The preview stores setup drafts and demo state in the current browser profile. Saved information includes workspace preferences, deployment plans, integration drafts, policies and recent local history. Demo enterprises additionally retain fictional simulations, review statuses and notes.

The setup workspace and the two demo enterprises have separate state. Enter demo mode and Exit demo change which state you are viewing; they do not move records between contexts. There is no shared account or backend synchronization of these drafts.

If storage is unavailable

The message Storage unavailable. Changes remain for this visit only. means the app could not persist an edit. You may continue exploring the current page, but reloading or closing it can lose those changes. Private browsing, storage restrictions or browser policies can affect persistence.

Use the browser's normal site-storage settings if you need to investigate the restriction. Do not disable organization-wide browser protections just to keep demo data. Use fictional content and export a planning artifact where that workflow provides an export.

Tabs and other devices behave differently

Tabs using the same app origin and browser storage can refresh saved changes from one another. The notification Workspace refreshed from another tab indicates that such a refresh occurred; open editors and drawers close. Finish an edit before changing the same workspace in another tab.

A different browser profile, device or private session has its own state. Share demo includes the selected enterprise and view, not the saved contents of your workspace. CSV and JSON downloads are separate files, not a complete restorable backup.

Before clearing site data

Clearing app site storage can remove setup and demo changes together. Prefer Reset this demo when you only want to restore one fictional enterprise. Local change history is not an immutable audit log, and requested retention does not automatically clear browser records.