Terms of Service

General terms for SABSUS usage, subscriptions, white-label, buyout, integrations and customer data.

Service purpose

SABSUS provides business operating tools for sales, orders, CRM, delivery, inventory, documents, payments, marketing and automation. The exact scope depends on the selected plan, implementation and commercial agreement.

Accounts and roles

The company owner is responsible for users, roles, permissions, data accuracy, internal policies and permissions from employees or customers whose data is processed.

Payments and subscriptions

Subscription, white-label and buyout models have different commercial terms. Payment, billing period, cancellation, refunds, module setup and external costs may be confirmed by a separate invoice, contract or agreement.

Integrations and third-party services

SABSUS may connect to external services. Availability and cost of those services depend on third-party providers, their terms, APIs, limits and pricing.

Acceptable use

The system may not be used for illegal activity, violation of third-party rights, unauthorized access, spam, abuse of limits or malicious content.

Limitation of liability

SABSUS aims to provide stable operation, but cannot guarantee the absence of errors, third-party API failures, connectivity issues, incorrect data, user mistakes or external service downtime.

Contact

For terms questions, contact support@sabsus.com.

Implementation scope

SABSUS can be used as a subscription, white-label solution, custom implementation or full buyout. These models are different. A standard subscription provides access to the platform under the agreed plan. A white-label setup may include branded customer-facing screens and custom configuration. A buyout or private deployment requires a separate scope, handoff plan, support agreement and legal confirmation.

Client responsibilities

The client is responsible for accurate business data, correct tax settings, payment method configuration, employee permissions, product information, prices, customer communications, content uploaded to the system and compliance with laws that apply to its business. SABSUS can provide tools and workflows, but it does not replace the client’s legal, accounting or operational responsibility.

Service changes

The platform may change over time as modules are improved, integrations are updated, security requirements change or third-party APIs modify their behavior. Some features may depend on external providers such as payment processors, email services, SMS providers, maps, hosting, app stores, AI providers or other APIs. If a third-party service changes, related SABSUS workflows may require adjustment.

Data and termination

If an account is terminated, access to the platform may be limited or removed according to the commercial agreement. The client should export required operational records before cancellation or deletion. Some records may remain when needed for security, accounting, dispute resolution or legal compliance.

White-label and branding

When SABSUS is configured under a client brand, the client remains responsible for the brand materials it provides, customer-facing claims, public descriptions, prices, policies and content shown to its customers. White-label configuration does not transfer responsibility for the client’s business operations to SABSUS.

AI-generated content and automation

Sabi AI and Flow automation can help generate content, map data, suggest actions and automate processes. The client is responsible for reviewing AI-generated outputs, checking business logic, confirming messages before use when required and ensuring that automated workflows do not create incorrect, unlawful or harmful outcomes.

Taxes, receipts and financial data

SABSUS can help display taxes, payment methods, receipts, order totals, deposits and business accounts, but the client is responsible for verifying tax rules, accounting records, fiscal requirements and legal reporting obligations in the jurisdictions where it operates.

Legal notice

This page is provided for transparency and does not replace a signed service agreement, order form, data processing agreement or implementation statement of work when one is used.