Shop Command Terms of Use

Users are responsible for keeping account credentials secure and for using roles that match the work each user should perform.

Owners and managers are responsible for adding, removing, and reviewing users in their workspace.

Technician accounts should only be used by the technician assigned to that account.

Pilot, demo, or free access may be provided for workflow testing, onboarding, feedback, and product validation.

Pilot access may be reviewed more closely than paid production usage so Shop Command can identify training needs, product defects, and workflow gaps.

Shop Command may change or end pilot terms before paid rollout if the workspace is inactive, misused, or no longer aligned with the pilot purpose.

Published pricing is $50 per user per month for monthly billing and $550 per user per year for annual billing unless a written agreement says otherwise.

Payments are processed through Stripe-hosted checkout links. Shop Command does not collect card numbers directly in the app.

Seat counts, billing cadence, renewals, and cancellation handling should be confirmed before starting paid service.

Do not use Shop Command to store passwords, private keys, payment card data, or regulated secrets in ordinary notes, service orders, attachments, or assistant prompts.

Do not attempt to access another customer workspace, bypass permissions, scrape private data, overload the service, or use the product for unlawful activity.

Report suspected account compromise, data leakage, or unsafe access immediately through the current support channel.

Shop Command may use workspace activity, operational records, support notes, and product usage data for support, analytics, testing, security, reliability, product improvement, and masked case-study development.

Customer workspaces should remain hidden from other customers, but Shop Command administrators may access data when needed for legitimate operating, support, security, or improvement purposes.

Public customer-identifiable claims, logos, or private operational details should not be published without separate approval.