Verified identity
Client Explorer signs you in through OAuth with PKCE. The service verifies tokens and checks current group access before returning workspace data.
BUILT AROUND CLEAR BOUNDARIESYour workspace.
Your workspace.
Considered access.
Practical controls for shared designs and connected agents. Here is what the current service implements.
Your group is the boundary
Projects and their referenced parts, assemblies, reports, and exports are scoped to the authorized group. Sign-in alone does not grant access to every workspace.
Scoped agent credentials
Personal MCP tokens have expiry, revocation, and read-only or read/write permissions. Their secrets are stored hashed, and access is checked against current group entitlement.
Protected OAuth credentials
Stored OAuth tokens are encrypted. Authentication cookies are HttpOnly and use Secure on HTTPS. Refresh rotation is coordinated to protect concurrent sessions.
History you can inspect
Saved design changes append immutable revisions. Assembly instances pin exact revisions, and reports retain their input versions. Reversible deletion keeps this evidence intact.
Bounded design inputs
Geometry uses validated declarative data. The server does not execute submitted model code or download arbitrary model URLs. Reference and size checks apply to MCP operations.
Know the scope
This is an implementation overview, not a claim of independent certification, an audit, a penetration test, or a service-level agreement. Your external AI provider has its own data practices. Keep tokens out of prompts, grant the access you need, and revoke unused credentials.
Contact & supportFor data handling and retention, read the privacy policy.