Trust & access
Know what stays
in your browser.
Here is how the current website handles setup choices, workspace examples, downloaded plans, and contact drafts—and how to clear or keep each one.
This is a public website with local demonstrations. Accounts, private saved workspaces, live agents, and app connections are not available.
Current data behavior
What happens when you use a feature.
| Feature | Where the information goes |
|---|---|
| Company setup | Company, mission, roles, model strategy, and budget choices stay in the open page’s memory. Refreshing starts a new plan. |
| Download plan | Your browser creates a JSON file with the plan and sample estimate. The download does not create an account or activate the plan. |
| Explore workspace | Only the company name and mission move through a session-storage draft. The home page reads and removes that draft, then applies the values to its example. |
| Sample workboard | Task changes, approval decisions, and budget adjustments update the local example. Reloading restores the sample state. |
| Contact draft | The page prepares text locally. Copy uses your clipboard; the email link passes the draft to your email app. You decide whether to send it. |
| Sign in | The destination explains account availability. It has no password field and does not authenticate a user. |
Your practical controls
Keep a plan, or start fresh.
To keep your work
Download the plan before refreshing setup. Review the JSON before sharing it: it includes the company, mission, roles, budget, and deployment choices you entered.
A downloaded file remains in your chosen download location until you remove it.
To clear the example
Use Reset example on the product workboard, or reload the page. A transferred mission is removed from session storage as the home page reads it.
If a transfer did not complete, clearing this site’s browser session storage removes the remaining draft.
Use fictional company information to explore the flow. API keys, passwords, and customer records do not belong in the mission field.
Before connected work
Define access around an action.
For a customer-reply workflow, a useful boundary is: the support role reads selected request text, prepares a draft, and sends it to the support lead for review. Sending the message is a separate permission. Record the reviewer, final text, recipient, and decision together.