Terms of Service

SmartQS is a multi-tenant queue management platform: token generation, a live call and queue engine, kiosk display boards, reporting, staff roles, and visitor notifications. An organization ("tenant") gets its own isolated account — the isolation posture (Standard, Enterprise, or Sovereign) is set when the account is created.

Staff accounts are created and managed by an organization's own admins. Each account has a role (admin or counter operator) that determines what it can see and do. You're responsible for keeping staff credentials confidential and for what happens under an account your organization controls.

Don't use SmartQS to collect more visitor data than a queue actually needs, don't try to enumerate or guess another visitor's status-page link, and don't attempt to access another tenant's data. Don't use the platform for anything unlawful or for a purpose it wasn't built for (it's a queue system, not a general data warehouse).

Every row in the system is scoped to a tenant, and public endpoints resolve a tenant only through an opaque identifier — never a sequential or guessable one. Which specific isolation model applies (shared database with row-level security, a dedicated database, or a fully separate cloud account) depends on the deployment tier your organization is on; see the Deployment tiers section on our homepage.

Counter and Kiosk apps are designed to keep working through a dropped connection and sync once it's restored — that's a design goal of the product, not a guaranteed uptime commitment. Formal SLAs, if any, are set out in an organization's order form, not in these general terms.

How we handle personal data — including the roles an organization and SmartQS each play as controller and processor, legal basis for processing, and data subject rights under GDPR and India's DPDP Act — is set out in our Privacy Policy, which forms part of these terms. An organization we onboard gets a signed data processing agreement in addition to it.

These general terms don't themselves specify a governing law or jurisdiction — that's set out in the master agreement / order form each organization signs at onboarding, since it can reasonably vary by tenant (for example, a government deployment's contract terms). We'll publish a default governing law here before onboarding any organization without a bespoke agreement.

We may update these terms as the product develops before general availability. Material changes affecting an onboarded organization will be communicated directly, not just posted here.

Questions about these terms: contact@smartqs.app