Each workspace is tenant-scoped, with authenticated requests and role-aware access. QaiS operates in the active workspace, and supported activity is recorded so administrators can review what happened.
TENANT-SCOPED · ROLE-AWARE · AUDITABLE
Workspace identity is resolved before tenant data is opened. Requests are authenticated and scoped to the active organization throughout the application.
Workspace · identity · scopeSupported QaiS actions and important user activity are recorded with useful context such as the actor and time. Administrators can review this history.
Recorded · attributable · reviewableHQE does not use or license Customer Data to train general-purpose models unless the customer explicitly opts in. AI requests are limited to the context needed to provide the requested feature.
No training without opt-inWe use access controls, logging, backups, service monitoring, and release verification as operational safeguards. Enterprise buyers can request a current security questionnaire.
Controls · backups · monitoringTraffic between supported clients and the service is encrypted in transit. Access to production systems and stored customer information is restricted to authorized operational needs.
TLS · controlled accessEvery request is authenticated and tenant-scoped. Role-based access runs across the workspace, and administrators control membership and roles.
Authentication · rolesCustomers retain ownership of Customer Data. HQE receives only the limited rights needed to operate, secure, support, and improve the service as described in the Terms and Privacy Policy.
Customer-owned dataWorkspace administrators can request an export and account owners can request deletion. We remove or de-identify information subject to operational, contractual, and legal retention requirements.
Export · deletion requestQaiS works under your team's rules: who can call which tool, and on whose behalf. Tenant data stays scoped to its workspace. When an administrator explicitly enables a shared channel or integration, only the authorized shared content is exchanged through that feature.
Supported calls are attributed to a person and time. Some tools also provide a before/after record or a recovery action; availability depends on the operation.
The example activity below illustrates the kind of operational context an administrator can review. Exact fields vary by module and action.
No certification claim: we do not currently claim SOC 2, ISO 27001, or TX-RAMP certification. If a procurement process requires a specific control, data location, subprocessor list, or contract term, ask us to confirm it in writing before purchase.
A workspace is a tenant with its own yourteam.qais.app address. The service resolves that workspace before opening tenant data, authenticates the request, and applies the user's organization role and capabilities.
HQE does not use or license your Customer Data to train a general-purpose model unless you explicitly opt in. When an AI feature needs a third-party model, relevant context may be sent to that provider to fulfill the request under our provider terms and privacy practices.
Not currently. We do not claim SOC 2 certification. Enterprise buyers can request a current security questionnaire so the available controls can be evaluated without relying on a roadmap promise.
Ask your workspace administrator about export options, then use the documented deletion request path when you are ready. We remove or de-identify information subject to operational, contractual, and legal retention requirements.
Our standard public service does not promise customer-selected data residency. If location is a procurement requirement, contact us before purchase so we can confirm whether a suitable Enterprise arrangement is available.
One tenant, one audit trail, one owner: you. Open a workspace and see it live.
FREE PLAN · NO CREDIT CARD · START ONLINE
QRM