Skip to main content
Scope Mesh is built around one idea: your assistant knows you, and the mesh doesn’t need to. This page explains how that works, and what applies to the preview today.

Answers, not data

When a mesh needs to know something about you, it asks your assistant a narrow question and gets back only the answer: Your calendar, email, budget, and accounts stay with your assistant. The mesh keeps the questions it asked and the answers it got, and nothing else.
Short answers can still say something about you. Enough yes-or-no questions about prices can narrow down a budget. That’s why a mesh limits which questions it can ask, and why you can always see every answer it received.

See what the mesh learned

Every answer your assistant gives is recorded, so you can see exactly what the mesh learned about you. In the demo, turn on Show what Scope Mesh learned to see each traveler’s questions and answers. See Try the demo.

Approvals belong to people

Your assistant can recommend a plan, but it can’t commit you to one. Every person approves the exact proposal themselves. If anything about the plan changes, such as the time, the hotel, or the price, earlier approvals no longer count, and everyone approves again.

What the preview keeps

  • The website demo runs with made-up travelers. It doesn’t ask for or collect anything about you.
  • The demo connector for Claude and ChatGPT needs no sign-in and keeps nothing between messages. When your assistant joins the trip for you, it sends only yes or no answers and your first choice, and the connector refuses anything else.
  • Beta signups go by email. Scope keeps your email to tell you when there’s something to try.
For how Scope handles your information across its apps, see Privacy and the Scope privacy policy.