Understand access and data handling in V7

A customer conversation, a business workspace and a management integration have different access needs. This overview explains the implemented boundaries and the questions your business should resolve before launch. It complements the privacy notice and does not replace your business’s own policies.

For business owners reviewing how customer information and management access are used.

Business accounts and tenant boundaries

Workspace access requires authentication and an assigned business role. Business data and permitted operations are scoped to the company associated with that access. Owners and authorised staff use the management workspace; visitors use the public customer chat experience.

Review team membership and permissions when people join, change responsibilities or leave. Administrative API and MCP access follows its own authorisation checks. Public chat does not inherit an owner’s management privileges.

Conversation context and stored records are different

Active conversation memory is scoped to the business and session. Its configurable history and duration limits control which earlier messages can be supplied for a follow-up. They do not establish a verified returning-customer identity.

Conversation history, enquiries, usage information and security records may be retained separately for authorised review. Expiring active memory does not automatically erase those records or provider-held data. Confirm the retention process and the applicable privacy information before collecting customer details.

AI providers and connected services

When paid AI is enabled, the configured provider receives the input needed for that model request, which can include instructions, relevant business information and conversation context. Connected channel or payment providers process information needed for their respective services.

Review the privacy notice for provider categories and check the actual configuration and processing arrangements with the operator. This page does not assert a specific processing location, certification, contractual guarantee or zero-retention setting.

Customer requests and private booking links

Enabled enquiry forms collect the details needed for the stated request. Opening a form does not submit it. Give customers a clear explanation of the purpose, the information required and how your team follows up.

A private management link can authorise access to an eligible V7-native booking when that feature is enabled. Customers should not share that link publicly. Private account operations in other systems require their own implemented integration, verification and permission checks.

Before you publish

Check who can access the workspace, what the agent is allowed to do, which providers are enabled and what personal information your forms request. Confirm the controller and privacy contact, the purposes for processing and the retention process with the operator.

Use the Privacy and Cookies links for the platform notices. Each business remains responsible for its own customer-facing information and processing decisions. Contact the business handling the conversation for a request about its customer records; contact Vertex Seven about platform account questions.

What to check before launch

This is a product overview, not a security certification or a guarantee of regulatory compliance. Ask for verified contractual and operational details where your business requires them.

Read the privacy information → · Read the cookie information →

Make an informed decision.