Shop Command Privacy Policy

Account and workspace details such as user names, business contact information, roles, and shop membership.

Operational shop records entered into the product, including customers, units, service orders, parts, inventory, invoices, reports, settings, notes, and attachments.

Usage and reliability information such as page views, clicks, feature usage, timestamps, device/browser details, errors, and performance signals.

Support, pilot, and onboarding notes shared with Shop Command during setup, testing, troubleshooting, or workflow review.

Operate the product, provide support, secure accounts, troubleshoot reliability issues, and improve workflow quality.

Analyze masked or aggregated product usage so we can understand which workflows are working, where users get stuck, and what should be improved.

Develop internal product benchmarks, demonstrations, tests, and case-study material using masked or anonymized data whenever practical.

Protect customer workspaces from unauthorized access, abuse, data loss, and cross-customer exposure.

Customer data is separated by workspace and should not be visible to other customers.

Shop Command administrators may access workspace data when needed for support, testing, security, reliability, onboarding, analytics, or product improvement.

We do not publish identifiable customer names, customer records, invoices, service orders, or private operational details in public marketing without a separate approval.

We use role-based access, authentication, database policies, audit evidence, and operational review to reduce unauthorized access risk.

Sensitive credentials should not be entered into general notes, service descriptions, report requests, or assistant prompts unless a feature explicitly asks for them.

Pilot and test accounts may be monitored closely so we can identify broken workflows, training gaps, errors, and product improvements before wider rollout.