SignalOps Terms of Service

01

Acceptance

By using SignalOps, you agree to these Terms and any applicable written order or pilot agreement between you and SignalOps. If you do not agree, do not use the Service. If you are using the Service on behalf of a company, you represent that you have authority to bind that company to these Terms.

02

The Service

SignalOps is the accountability layer between frontline reps and the spreadsheets, rollups, and reconciliations that follow them. Today the Service is designed for wireless retail teams and is positioned as carrier-agnostic, meaning it is meant to fit alongside existing operating systems instead of forcing a POS replacement.

SignalOps is currently in private beta. Features, workflows, reports, exports, and admin controls may change, move, or disappear as we learn from live use.

03

Beta Limitations

Private beta means the product is usable, but still evolving. During beta, you should expect rough edges, missing controls, and operational changes that would not be acceptable in a fully mature general-availability product.

• The Service may experience downtime, bugs, data loss risk, or breaking changes.
• During beta, SignalOps is not your system of record for legal filings, accounting records, payroll decisions, tax reporting, or other financial filings.
• Customers should keep their existing systems and controls running in parallel until SignalOps reaches general availability and both sides agree on production terms.
• Production-ready commercial terms such as SLAs, uptime guarantees, and similar commitments will be addressed, if at all, in later GA documents rather than during this beta.

04

Account & Access

Each person should use their own account. You are responsible for keeping credentials secure, preventing unauthorized use, and making sure only the right people have access to your stores, districts, teams, and reports.

Do not share credentials. Shared credentials can make audit history unreliable, blur who actually performed a sensitive action, and interfere with access controls, investigations, and support.

05

Acceptable Use

Use the Service lawfully, responsibly, and only for your own authorized business purposes. You may not:

• access the Service without authorization, scrape it at scale, probe it, or abuse rate limits or shared infrastructure;
• reverse engineer, decompile, or try to extract source code, trade secrets, or underlying models from the Service;
• use the Service in a way that violates law, regulation, contractual obligations, or the terms of any third-party systems you rely on; or
• upload malware, illegal content, or personal information you are not authorized to collect, use, or disclose.

06

Customer Data Ownership

As between you and SignalOps, your business data remains yours. SignalOps acts as a processor and custodian of that data so we can host the Service, provide support, secure the environment, and deliver the reports and workflows you ask us to run.

We will make reasonable data export options available for the records you put into the Service. We do not sell your customer data, and we do not use your customer data to train general-use models.

07

Our IP

SignalOps owns the Service itself, including the software, site copy, product design, design system, documentation, branding, and the SignalOps name and marks. These Terms do not transfer any ownership rights to you.

While your account is active and in good standing, we give you a limited, non-exclusive, non-transferable right to use the Service for your internal business operations in line with these Terms.

08

Fees & Billing (during beta)

Most beta accounts are currently no-charge or covered by a pilot arrangement. If we agree to a paid pilot, pricing, invoicing, and payment timing will be governed by a separate written order or pilot agreement, not by surprise language hidden in this page.

We will not start billing you unexpectedly. Any future self-serve or subscription billing model will be presented clearly before it takes effect.

09

Term & Termination

During beta, either side may end access by giving notice by email. If SignalOps later reaches general availability and we enter a standard commercial relationship, the default term will be month-to-month unless a written order says otherwise.

On request, we will make a reasonable export of your operational data available. After termination, we will delete operational data within a reasonable window, but we may retain audit logs, security records, billing records, backup copies, and any data we are required to keep for legal hold, fraud prevention, or operational integrity reasons.

10

Disclaimers

During beta, the Service is provided "as is" and "as available." To the fullest extent allowed by law, SignalOps disclaims implied warranties, including implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

SignalOps is a tool to help organize activity, reporting, and reconciliation. You remain responsible for reviewing your own records, and we do not guarantee that bonus calculations, compensation figures, reconciliations, or management decisions produced with the Service are complete or correct.

11

Limitation of Liability

To the fullest extent allowed by law, SignalOps will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, or business interruption arising out of or related to the Service.

To the fullest extent allowed by law, SignalOps's total liability for all claims arising out of or relating to these Terms or the Service will not exceed the greater of the fees you paid us in the 12 months before the claim or $100, whichever is greater.

12

Indemnification

If your actions, data, or use of the Service violate these Terms, violate law, or infringe someone else's rights and that causes a third-party claim against SignalOps, you will defend and indemnify SignalOps for that claim.

If SignalOps violates law, breaches these Terms, or infringes a third party's rights and that causes a third-party claim against you, SignalOps will defend and indemnify you for that claim. Each side must promptly notify the other and give reasonable cooperation in the defense.

13

Confidentiality

Both sides will protect the other side's non-public information and use it only as needed to evaluate, receive, or provide the Service. That includes business information, account data, pricing, security details, support materials, and unpublished product information.

Because SignalOps is in private beta, beta features, roadmaps, screenshots, product behavior, and unpublished implementation details should be treated as confidential unless we clearly say otherwise in writing.

14

Governing Law & Dispute Resolution

These Terms will be governed by the laws of the State of Delaware, without regard to conflict-of-laws rules.

Unless a written order between you and SignalOps says otherwise, disputes will be resolved in the state or federal courts located in Delaware.

15

Changes to These Terms

We may update these Terms as the product and business mature. For material changes, we will give notice by email or another reasonable account notice method before the updated terms take effect.

For minor edits, clarifications, or non-material updates, we may simply post the revised version and update the "Last updated" date below.

16

Contact

Legal questions, notices, and requests about these Terms should be sent to [email protected].

Formal notices may also be directed to SignalOps via the email addresses above.