Privacy

QirimWa handles workspace data with tenant isolation, role-based access, and operational traceability in mind.

This privacy page explains the practical categories of data processed by QirimWa and how that data is used to run WhatsApp commerce, shared inbox workflows, billing, and platform administration.

What data QirimWa processes

QirimWa processes workspace profile data, user account data, connected WhatsApp account metadata, conversation history, contact records, merchant catalog data, order or booking records, campaign records, billing state, and operational notifications.

Depending on how a workspace is configured, QirimWa may also process AI settings, knowledge base entries, message logs, audit activity, and limited integration metadata returned by Meta or payment providers.

How data is used

Workspace data is used to authenticate users, run inbox workflows, deliver outbound messages, process inbound webhooks, manage merchant catalog and order or booking workflows, manage templates and campaigns, and show billing or usage context inside the product.

Operational records such as audit logs, notification events, and message history are also used to support traceability, troubleshooting, and day-to-day platform administration.

Access control and tenant isolation

QirimWa applies tenant scoping at the application layer so workspace users operate only within the tenant assigned to their account, while superadmin access is separated for platform governance and support tasks.

Administrative or support access should be limited to authorized personnel and is intended only for platform management, support intervention, or security review.

Credentials and integrations

Integration credentials such as WhatsApp access tokens and provider-level secrets are handled through controlled backend services and are not intended to be openly exposed across normal workspace surfaces.

When Meta, payment providers, or other operational integrations send data into QirimWa, that data is used only to support the configured workflow such as onboarding, billing, webhook handling, or delivery monitoring.

Retention and operational records

QirimWa may retain conversation history, billing records, audit logs, notification records, and related metadata for product operation, support review, and platform accountability.

Retention windows may vary depending on workspace activity, subscription status, support needs, or legal and security obligations that apply to the platform.

Contact and questions

If you need clarification about workspace data handling, platform access, or privacy-related operational behavior, contact the QirimWa team through the published support channels.

For tenant-specific issues, include the workspace name, affected user email, and a clear description of the workflow involved so the team can review the request accurately.

Need anything else?
QirimWa
QirimWa keeps official WhatsApp operations, AI automation, and campaign workflows in one structured product.