Prism
Trust

Trust and privacy for Prism.

Prism is currently offered as Prism at $50/month or $500/year for 3 seats. Most operator workflow content can stay local unless you enable telemetry, use hosted account services, or intentionally share material with Prism for support.

Public positioning, support guidance, and legal surfaces follow the same authorized-use and operator-oversight boundary.

Trust posture

Operational transparency without security theater.

Prism keeps local workflow material local by default, exposes telemetry preferences, and scopes support requests to the minimum necessary diagnostic set.

DefaultCustomer content can stay local

Workflow data, logs, screenshots, and profiles are not forced into a hosted path.

TelemetryVisible operator preference

Minimal, full, or off are explicit choices rather than hidden defaults.

SupportMinimum necessary sharing

Support requests should include only the artifacts needed to diagnose the issue.

BoundaryAuthorized workflows only

Public copy does not position Prism as a bypass or stealth tool.

Data handlingLocal-first by default

Profiles, macros, datasets, screenshots, and logs can remain on the customer machine. Prism only receives that material when hosted features are enabled or when a customer deliberately shares it for billing, support, or troubleshooting.

TelemetryOperator-controlled preference

Choose minimal, full, or off at onboarding. Telemetry settings are visible and adjustable with no hidden collection.

Authorized useNo bypass or anti-detect positioning

Prism is for systems and workflows the customer owns, administers, or is expressly authorized to automate. Public copy and support expectations follow that same line.

Support bundles

What Prism may receive when customers ask for help.

Support should request the minimum diagnostic set needed to understand the issue and route it correctly.

Likely artifactsTypical support inputs
  • App version and build channel
  • Device identifiers and activation state
  • Screenshots, logs, and reproducible failure steps
  • Billing or entitlement context when relevant
Operating ruleAsk for the minimum necessary material.

Customers should share only the data needed for troubleshooting. Support guidance should state clearly when screenshots, run logs, or exported data are being requested.

Policy setLegal documents stay aligned with the Prism product.

The EULA, Acceptable Use Policy, and Privacy Policy cover desktop access, authorized use, and privacy expectations for the current Prism rollout.

Need help?Activation, billing, and runtime issues still route through one support path.

Not sure whether the issue is policy, billing, activation, or runtime? Start with support and Prism can route from there.