These terms outline the practical conditions for using QirimWa, including workspace access, subscription behavior, billing, platform restrictions, and acceptable operational use.
Each QirimWa workspace is tenant-scoped and must be used only by authorized users acting on behalf of the relevant business or organization.
Users are responsible for maintaining the confidentiality of their credentials and for ensuring that access is limited to approved owners, admins, agents, or platform administrators as applicable.
Feature availability in QirimWa depends on the active subscription plan. Starter is intended for product evaluation, while paid plans unlock operational modules such as WhatsApp onboarding, catalog-driven commerce workflows, AI settings, templates, campaigns, and team workflows.
If a subscription expires, remains unpaid, or is otherwise restricted, QirimWa may limit or suspend access to affected paid features until the subscription state is restored.
Customers are responsible for compliant use of WhatsApp messaging, merchant catalog data, bookings or orders, contact data, templates, campaigns, and internal operator access within their workspace.
QirimWa must not be used for abusive messaging, unlawful activity, unauthorized account access, evasion of provider rules, or any attempt to misuse platform infrastructure or tenant boundaries.
QirimWa relies on third-party services such as Meta WhatsApp Business Platform, AI providers, and payment providers to support specific product workflows.
Availability, approval, or delivery outcomes related to those providers may affect the customer experience, and QirimWa cannot guarantee uninterrupted behavior when upstream providers impose limits, delays, or policy restrictions.
QirimWa may suspend, restrict, or review workspace access when there is a security concern, payment failure, suspicious activity, provider compliance issue, or misuse of the platform.
Where reasonable, the platform should provide notice, but immediate action may be required in situations that threaten service stability, security, or policy compliance.
QirimWa is intended to support structured merchant operations, but customers remain responsible for how they configure automation, order or booking workflows, human handover, contact handling, and outbound communication policies.
Teams should review their own catalog rules, templates, payment flow, approval processes, escalation rules, and campaign audiences before using the platform in production.
QirimWa may update product behavior, plans, quotas, integrations, or administrative controls as the platform evolves.
When changes materially affect billing, access, or operational behavior, the platform should communicate those updates through the product or the relevant support and notification channels.
