Information we handle
Account and access information such as name, email address, authentication state, organization membership, Business scope, and role.
Business workspace information such as business names, configuration, connection state, channel identifiers, and operational settings.
When a business authorizes Meta or WhatsApp, the business assets and identifiers that Meta returns for the assets the business selected. Smart Visions does not ask customers for their Facebook password and does not require customers to paste a Meta access token into the product.
Communication data needed to provide the service, which can include WhatsApp message content, media references, sender and destination identifiers, timestamps, delivery or read status, conversation state, and support actions.
Security, audit, diagnostics, and technical logs used to protect accounts, investigate failures, reconcile provider events, and operate the service.
How we use information
To authenticate users, enforce organization and Business-scoped access, provide inbox and CRM functionality, connect authorized communication channels, send authorized replies, and run customer-enabled automation.
To maintain service reliability, detect abuse, troubleshoot integrations, reconcile provider state, keep audit records, and support customers.
We do not treat a pre-authorization setup record as proof that a communication channel is connected. Provider-connected status is based on provider and credential evidence.
Meta and WhatsApp integrations
Meta authorization is performed through Meta-hosted authorization and Embedded Signup flows. Smart Visions requests access only to business assets the customer authorizes.
For a phone number already active in the WhatsApp Business App, Smart Visions supports only an official Meta Business App Coexistence path when the account and number are eligible. We do not require deleting the WhatsApp account or removing the WhatsApp Business App as a fallback.
Disconnecting an integration stops or limits future access according to the provider flow. It does not automatically erase information already stored by Smart Visions; deletion requests are handled separately.
Service providers and systems
Smart Visions uses infrastructure and service providers to operate the product. Depending on the feature, these can include Meta / WhatsApp for authorized messaging, Supabase for application data and authentication, Cloudflare for application delivery and runtime infrastructure, and Chatwoot as the communication plane for supported inbox workflows.
Additional providers may be used for specific enabled features such as email delivery or AI processing. Access is limited to what is needed to provide the enabled function and is governed by the product configuration and access controls.
Retention and deletion
We retain information only for as long as reasonably needed to operate the service, protect security and audit integrity, meet contractual or legal obligations, resolve disputes, and maintain required financial or compliance records.
An authorized account or business contact can request deletion or de-identification of data controlled by Smart Visions. We verify the requester before acting. Some limited records may need to be retained where required for security, fraud prevention, legal obligations, financial records, or audit integrity.
Security and access
Access to customer workspaces is scoped by organization membership and explicit Business access. Sensitive provider credentials are handled on the server and are not intended to be exposed in the browser.
Smart Visions uses role and scope controls, audit records, secret-management boundaries, and provider verification checks to reduce unauthorized access and cross-Business data exposure.
Your choices and requests
You can request access, correction, or deletion of information controlled by Smart Visions, or ask about how a business integration is being used. Requests involving a Business workspace must come from an authorized contact so that we can protect other users and business data.
Policy changes
We may update this policy when the product, providers, or legal requirements change. The effective date on this page identifies the current published version.