Separate customer and admin access
Customer sessions open tenant-scoped portal data. Platform-admin routes require a separate authorization check and do not rely on customer browser state.
Security & reliability
Practical safeguards across the customer, billing, and assistant lifecycle.
Nuvareq combines account boundaries, tenant-scoped data, reviewed configuration publishing, and authenticated provider workflows. This page describes current product controls and does not claim a third-party certification.
Account and data boundaries
Access follows the role and workspace.
Tenant-scoped records
Configuration, usage, billing, calls, leads, and provider mappings are associated with the correct business workspace before they are returned or changed.
Provider secrets stay server-side
Credential values are masked in browser-facing admin responses. A blank edit preserves an existing encrypted value rather than exposing or erasing it.
Billing and provider events
External state is accepted through controlled paths.
Stripe-hosted checkout
Nuvareq selects the server-approved plan mapping and sends customers to Stripe-hosted checkout. Browser-supplied price identifiers are not the source of truth.
Authenticated webhooks
Billing and messaging callbacks are validated before they update subscription or delivery state. Duplicate provider events are handled with idempotency controls.
Fail-closed readiness
Publishing and runtime actions require the credentials and provider configuration they depend on. Missing setup remains visible instead of silently weakening authorization.
Reviewed assistant changes
Draft changes do not automatically become live behavior.
Customers save and submit structured business information. Nuvareq reviews a revision before publishing it to the mapped assistant, and the lifecycle keeps an audit trail of approval, publishing, failure, retry, and rollback.
Deterministic configurationApproved onboarding fields compile into a reproducible assistant configuration.
One mapped assistantProvider identifiers are stored with the correct tenant instead of being accepted from the browser.
Last working versionA publish failure does not erase the previously published configuration.
Visible action requiredCustomers and admins can see when review, credentials, or a retry is needed.
Voice, SMS, and AI boundaries
Automation still needs clear human rules.
Approved knowledge
The customer defines what the assistant may answer and what it must never invent.
Consent-based SMS
SMS is excluded from PAYG and included with Starter, Growth, and Scale. Entitled sending still requires consent, phone setup, registration, and provider readiness.
Recording disclosure
Customers configure applicable call-recording and data-collection language for their business and jurisdiction.
Not emergency service
Nuvareq must not be relied on as emergency dispatch or as a substitute for legal, medical, financial, or other licensed professional advice.
Privacy and support
Understand the data path and know where to ask for help.
Our Privacy Policy explains the categories of information used to operate the service. If a security, privacy, billing, or provider-readiness issue needs attention, contact Nuvareq directly.