Clear operating rules for a controlled support workflow.

These product terms apply to access to Tactrail's web application, Shopify connection, support-email workspace, automation tools, and related public request or tracking flows. A signed Order Form, data-processing agreement, or negotiated service agreement can add or replace provisions and should state which document controls if terms conflict.

A pilot or preview may be limited, changed, or discontinued. Production commitments should only be relied on when they are written in an executed agreement with the identified Provider.

You must be legally able and authorized to act for the organization whose workspace you create or join. Keep credentials confidential, assign roles according to job need, maintain accurate account information, and promptly remove access that is no longer required. Workspace owners are responsible for invitations and member access.

You may connect only stores, domains, mailboxes, and customer data you are authorized to administer. You retain responsibility for the legality, accuracy, and quality of your content, policies, store data, and customer communications, and for providing required notices and instructions to the Provider.

You grant the Provider only the rights needed to host, process, transmit, and display that data to operate the service under the applicable agreement. Ownership, confidentiality, deletion, export, and retention details must be completed in that agreement before production use.

Tactrail can classify messages and draft responses using store, conversation, and order context. AI output can be incomplete, inaccurate, or unsuitable. Model confidence labels are operational signals, not calibrated guarantees of correctness.

You decide which supported categories use draft, human-only, or any separately enabled auto-send mode. You must test the product with your policies and representative cases, review consequential decisions, and keep a human escalation path. Refunds, chargebacks, legal rights, safety issues, and other sensitive cases should not rely solely on model output.

You must not use Tactrail to do, assist, or encourage any of the following:

• Accessing a store, mailbox, workspace, or customer record without authorization.
• Using Tactrail for unlawful, deceptive, abusive, discriminatory, or unsolicited communications.
• Attempting to bypass access controls, rate limits, delivery safeguards, or human-review policies.
• Uploading malware or using the service to probe, disrupt, or degrade another system.
• Presenting model output as verified fact when required store or order context is missing.
• Using the service for high-impact decisions about a person without appropriate human judgment and a lawful basis.

Tactrail depends on separately operated services, including Shopify, email delivery, database and authentication, AI model, billing, and hosting providers. Their terms, availability, APIs, scopes, and processing locations can affect the service. You must maintain any accounts and permissions required on your side.

A reference to an integration does not promise that the third party endorses Tactrail or that every feature, region, or plan is supported.

Any price, billing period, usage allowance, tax treatment, trial, renewal rule, and refund term must be shown in the checkout or Order Form accepted by the customer. The application may enforce plan and usage limits. This page does not create a price or paid subscription by itself.

Material reductions to an agreed production service, price changes, and termination rights require the notice and procedure stated in the controlling commercial agreement.

The Provider and customer share responsibility for protecting the service. Customers must manage members, connected systems, policies, and response review. The Provider must operate the safeguards and incident process promised in the final agreement. The public security page describes the current release-candidate posture without making a certification claim.

Access may need to be restricted to prevent abuse, protect users or connected systems, comply with law, or respond to a material breach. The final agreement must define notice, cure periods, termination, workspace export, deletion, and any continued access after cancellation. No retention or export window is promised by this pre-release page.

A monitored legal contact has not yet been configured. The Provider must publish one and define formal-notice mechanics before accepting production customers.