Start with the real working day.
Projects cross departments. Customer enquiries need internal follow-up. People processes affect daily operations. We build the VAV One story around those practical connections.
Bring projects, conversations, people operations and customer follow-up into focus. With VAV One, teams can see the next step, the person responsible and the information behind the decision. VAV AI helps make that work easier to understand.
Projects / Riverside Office Fit-out
Riverside Office Fit-out
✦ VAV AI
Ask about a project. Review the important points from a discussion. Consider a suggested follow-up. VAV AI helps you work through relevant context before deciding what happens next.
Explore VAV AI →✦ VAV AI · Project review
Illustrative exampleSOURCE CONTEXT
The layout review is awaiting Maya’s review. Omar’s site brief is in progress and depends on the completed layout review.
ANSWER
The layout review needs attention before the site brief can be updated. Review Maya’s task and confirm the next step with the team.
SUGGESTED FOLLOW-UP
Ask Maya for an update on the layout review.
CONNECTED WORK
VAV One helps teams organise these parts of the working day around the work they concern.
Conversation
A conversation raises a question.
Task
A task gives it an owner.
Files
Supporting files explain the detail.
Review
A review brings the next decision into view.
THE PLATFORM
SOLUTIONS
Explore project delivery, HR operations, sales follow-up or leadership reviews. See how the relevant modules support a workflow your team already recognises.
Explore SolutionsStart with your processes, teams and existing systems. Define the modules, connections and implementation scope that fit the work you want to improve.
FAQ
Yes. Bring your current system landscape into the discussion so the team can assess the required information and available connections.
One real workflow, the people involved and the decision or handoff you want to improve.
Show us how your team works today. Explore a clearer way to organise responsibility, review the context and prepare the next step.
Book a Demo →VAV One brings projects, conversations, people operations and customer follow-up into a clearer working picture. Our focus is the relationship between the work being done and the decisions that move it forward.
Official brand art
One
Platform.
Every
Decision.
The work
The decision that moves it forward
VAV AI · context for the discussion
The idea is simple: people should be able to understand the next step, the responsibility behind it and the information available for review. VAV AI adds a way to explore relevant context and prepare for that discussion.
THE WORK
THE DECISIONS THAT MOVE IT FORWARD
THE WORK
THE DECISIONS THAT MOVE IT FORWARD
They shape the platform experience, the VAV One story and the way we discuss implementation with each organisation.
Projects cross departments. Customer enquiries need internal follow-up. People processes affect daily operations. We build the VAV One story around those practical connections.
Clear ownership, useful context and an accessible source record make work easier to review. These principles guide the platform experience and the way we discuss implementation.
Every business has its own processes, systems and responsibilities. Our starting point is a conversation about the work you need to support and the scope required to do it.
Tell us about the teams, processes and decisions you want to support. We’ll talk through the platform and the scope required to do it.
Choose the topic that best describes your enquiry so it can reach the appropriate team.
Illustrative routing
Design template — populate from the implemented website’s actual technologies and complete jurisdiction-specific review before publication.
The cookies and similar technologies used on the VAV One marketing website, why they are used, and the choices available to you.
Manage preferences
Required
Needed for the website to work
Optional category
Name and purpose to be confirmed
Optional category
Name and purpose to be confirmed
Illustrative — shown only if the implemented consent system provides it
SECTION 1
A plain explanation of cookies and similar technologies, such as local storage or pixels, as they apply to this website.
SECTION 2
Each technology actually deployed, with its provider, purpose, duration and category.
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
| Required | ||||
| Optional | ||||
| Optional |
Populate from the implemented website. Only list technologies the site actually uses.
SECTION 3
Technologies needed for the website to work, and why they cannot be switched off.
SECTION 4
Any optional categories, where applicable, and what each is used for.
SECTION 5
How to accept, refuse or change your choices at any time, and the effect of those choices.
Change your choices at any time
Opens the website’s preference controls, where provided.
SECTION 6
How this Cookie Policy relates to the Privacy Policy.
Read the Privacy Policy→SECTION 7
The effective date of this policy and how updates are made.
See the Privacy Policy for the privacy contact, or use the contact form and choose “General enquiry”.
Bring a project, people process, customer follow-up or management review. We will explore the relevant modules and discuss how the available experience fits your organisation.
Demo · Your workflow in VAV One
Riverside Office Fit-out
Layout review
Maya
In ReviewSite brief
Omar
Due 26 SepFurniture schedule
Lina
Due 30 SepClient walkthrough
Sara
Due 2 OctFive areas we can walk through, using the workflow you bring rather than a generic tour.
Layout review
ChatFilesMeetingLayout review
In ReviewSite brief
Due 26 SepWalkthrough
Due 2 OctConfiguration
Data preparation
Training
We confirm your request has been delivered before showing a success message. There is no silent marketing subscription, and no pre-filled calendar slots.
Sending your request…
Your demo request has been received.
Our team will contact you to arrange a demonstration around your priorities.
We could not send your request. Please try again.
A useful implementation begins with the work your team needs to do. Bring your processes, responsibilities and existing systems into the discussion, then agree the VAV One scope that fits your priorities.
THE PATH
Each step produces something your team can review — not a promise of instant onboarding.
Identify the people involved, the information they use and the decisions or handoffs that need improvement. Choose a priority workflow for the initial evaluation.
Review the relevant modules, user roles, data and system connections. Distinguish standard capability, configuration and any separately assessed integration or development work.
Discuss the structures, fields, statuses and responsibilities needed for the proposed process. Confirm what information will be brought in and who will own it.
Agree representative journeys and expected results. Check the workflow with the people who will use and manage it before deciding on rollout.
Clarify the training, rollout responsibilities and support arrangements required by your organisation. Put agreed services and milestones into the implementation proposal.
CLEAR SCOPE
The proposal distinguishes standard capability, configuration, and any separately assessed integration or development work — so everyone knows what the agreed scope includes.
Modules as they work today
Projects and TasksTeam ChatMeetingsSet up for your process
Fields and statusesUser rolesNotification rulesAssessed and agreed on its own
System connectionsData migrationCustom developmentBEFORE YOU START
FAQ
Timing depends on the modules, configuration, data and connections involved. The proposal should set out the agreed scope and delivery milestones.
Discuss the priority workflow and the dependencies around it. The team can help define a practical starting scope.
Bring one process, the people involved and the outcome you want — we’ll agree a practical starting scope together.
Plan Your First WorkflowYour organisation may already rely on ERP, customer, calendar or other business systems. Explore where VAV One fits and which information needs to connect to the work.
START HERE
These questions define a useful connection — before anyone discusses a connector.
e.g. customer account, item, order
The system that owns it today
Roles and access in VAV One
The follow-up or review it enables
CONNECTION TYPES
A file import, a configured connector, a live read and a write back to another system serve different purposes. Review the connection type and supported operations for your requirements.
Bring in records from a file, on an agreed schedule.
A set-up link to a supported system for agreed records.
Show information from another system when it is needed.
Update the other system from an agreed workflow step.
Destination: CRM enquiries use customer name, reference and division for follow-up.
DATA
Identify records, fields, ownership and how often the information needs to change. Make sure the destination workflow has the context needed to use it correctly.
VALIDATION
Check that records match, values are understandable and the intended workflow behaves as agreed. Include permissions and error handling in the implementation discussion.
AVAILABLE CONNECTIONS
Share the product and version you use, the information required and whether your workflow needs to read or update it. The VAV One team can confirm the relevant available scope.
Named connectors are published only after their data scope and availability are confirmed.
FAQ
An integration connects an agreed flow of information. Your proposal should distinguish the systems that remain in use from the work performed in VAV One.
Every requirement needs assessment against the available interfaces, access, data and supported connector scope.
Tell us which record you need, where it lives and what it should support — we’ll confirm the relevant available scope.
Review Your Connection RequirementsStart with the work you want to improve. Discuss the VAV One modules, users, connections and implementation services needed for your organisation, then request a proposal with a clear scope.
Choose capabilities
5 of 8PROPOSAL DRAFT
Scope for your organisation
Illustrative — no preset tiers or prices
Start with the work you want to improve, then shape the setup and services around it — before any proposal is written.
Identify the teams and workflows you want to support, from project delivery and people operations to customer follow-up and management reviews.
Review organisational structure, access, data and any existing-system connections. Include the VAV AI workflows you want to evaluate.
Discuss configuration, data preparation, training and support requirements. Ask the proposal to distinguish software scope from any implementation or additional service work.
Use this list with your finance, procurement and IT owners. A clear proposal answers each one in writing, so the scope you agree is the scope you receive.
Request a Tailored ProposalProposal review checklist
VAV One · scope for your organisation
FAQ
Share your requirements through the proposal enquiry. The team can confirm the commercial scope and applicable pricing.
Ask the team about the evaluation options available for your proposed setup.
Discuss how future modules, users or integrations would be handled in the commercial agreement.
Tell us the teams, workflows, users and connections you want to cover. The team will come back with a proposal that shows a clear scope.
Projects, people, conversations and customers all contribute to the same business outcomes. VAV One gives those areas a clearer structure, with practical tools for daily coordination and VAV AI for understanding relevant work context.
VAV One
Work
Projects · Chat · Meetings
People
People and HRMS
Customers
CRM
Decisions
Approvals · Insights
Briefings · Summaries · Suggestions
Illustrative overview
ONE STRUCTURE
Each area gets practical tools for daily coordination, with links to the module pages that go deeper.
Furniture schedule
Layout review
Client walkthrough
WORK
Organise projects and tasks, assign owners, set dates and track the status of the work. Keep discussions, attachments and related records available when someone needs the detail.
PEOPLE
Bring employee information, organisational structure, schedules and attendance into the people-operations picture.
Last conversation: call with facilities manager
CUSTOMERS
Give enquiries, customer conversations and next actions a structured place in the sales workflow.
Layout review — Riverside
DECISIONS
Use linked tasks, review requests, meetings and configured notifications to prepare the next step. Managers can move from a working overview to supporting information.
Use project briefings, discussion summaries and suggested follow-ups to make relevant work easier to review. Explore the sources and actions supported in your proposed setup.
Explore VAV AI →Project briefing
The layout review needs attention before the site brief can be updated.
Discussion summary
Key points: layout options agreed; lighting still open for review.
Suggested follow-up
Ask Maya for an update on the layout review.
IMPLEMENTATION
Start with the modules that address your priority workflow. Review your existing systems, data and access requirements with the VAV One team before agreeing implementation scope.
FAQ
Discuss the modules, users, connections and services you need with our team. The proposal should make the agreed product and implementation scope clear.
Bring one real workflow — we’ll show the modules that support it.
Organise enquiries, customer conversations and the next action. Give your sales team a clearer view of the relationship, the opportunity and the person responsible for following up.
OPPORTUNITY
Follow-upClinic reception fit-out
Adam & Eve Medical Centre
Can we see an option with a larger waiting area?
Layla Rahman
Facilities manager
Interaction history
CUSTOMER CONTEXT
Keep contact and enquiry information organised so the team can find the record relevant to a conversation. Review notes and the available interaction history before deciding the next step.
PIPELINE
Use meaningful stages to organise sales work and review where opportunities stand. A useful pipeline makes the next action easier to identify, not just the number of records easier to count.
Fit-out enquiries · Sales pipeline
FOLLOW-UP
Bring customer interaction context into the follow-up process. Help colleagues see what has already been discussed, who is responding and what needs attention.
Can we see an option with a larger waiting area?
@Maya can we rework the layout? Clinic stays open during works.
Yes — revised option ready by Wednesday.
STRUCTURE
Discuss your divisions, teams, fields and reporting needs. Configure the relevant structure around the customer journey you want to support.
Explore Sales Follow-upCONNECTIONS
Where customer or transaction information sits in another system, review the required data and available connections with the VAV One team. Agree the information flow before including it in your sales process.
Explore IntegrationsTHE DEMO
Follow a fictional enquiry through its customer context, conversation, pipeline stage and assigned follow-up. See which details your team needs at each step.
01 Customer context
Layla · Adam & Eve Medical Centre02 Conversation
Larger waiting area requested03 Pipeline stage
Follow-up04 Assigned follow-up
Sara · Send revised layoutFAQ
Share the channels and systems you use. We will review the available connections, setup requirements and scope relevant to your proposal.
The demo can review your stages and required fields, then identify the configuration needed for a clear customer journey.
Bring one real enquiry — we’ll trace its context, conversation, stage and next action with your team.
Show Us Your Customer Follow-up ProcessA useful management view helps you understand what needs attention and where to look next. Bring projects, responsibilities and review items into focus, then open the supporting work.
FOCUS
Organise your working overview around the conversations managers need to have.
Surface review items and the choices waiting on a manager.
See the person responsible before the conversation starts.
Know which tasks, discussions and files support the answer.
DRILL DOWN
Open linked tasks, related discussions and supporting files. Keep the source available when a summary needs explanation.
MEASURES
Review status, dates and configured progress information alongside their definitions. Distinguish completed work items from reported project progress so the team discusses the right measure.
Use a VAV AI project briefing to prepare for a review. Check the relevant tasks and use suggested follow-ups as a starting point for the management conversation.
Explore VAV AIThe layout review needs attention before the site brief can be updated. Review Maya’s task and confirm the next step with the team.
YOUR VIEW
Discuss the projects, departments and branches you need to review. Agree the records, fields and relationships required for a useful management view.
FAQ
The strongest review starts with a concise overview and keeps a route to the detail. The demo will show how the working view relates to source tasks.
Review the required systems, definitions and data flow with the team. The available scope depends on the agreed connection and implementation.
Bring the reviews you run each week — we’ll shape an overview that keeps a route to the source work.
Show Us the Decisions You Need to PrepareGive meetings a clear purpose. Schedule the discussion, include the relevant people and link the tasks that need attention before the conversation begins.
PREPARATION
Prepare a title, agenda, date and time. Identify the meeting lead and invite the participants who need to contribute.
LINKED TASKS
Connect relevant tasks to the meeting so participants can review responsibility, status and supporting information. Keep the discussion grounded in the work.
CALENDAR
Use calendar views to browse planned meetings and reopen their details. Review the agenda, attendees and linked work when preparing for the next conversation.
IN PRACTICE
A project review can start with three linked tasks, the questions that need an answer and the people responsible. The team can return to those work items after the discussion.
FAQ
Task links are part of the meeting-coordination story and can be shown in the demo.
Bring these requirements into the scope discussion so the team can confirm the available connections and capabilities for your setup.
Bring one recurring meeting — we’ll show how its agenda, attendees and linked tasks come together.
Explore a Work-Linked MeetingGive employees, managers and HR teams a clearer place to find people information and organise everyday processes. Start with employee records, organisational context, schedules and attendance, then discuss the wider HR workflows your business needs.
ONE PLACE, TWO VIEWS
FOR EMPLOYEES
Explore the employee experience for personal information, schedules, attendance and available HR request entry points. Make the next step in an everyday HR process easier to understand.
RECORDS
Use the employee directory and profile information to find people and understand their place in the organisation. Review the structure of departments, teams and reporting responsibilities.
TIME
Bring shift calendars, schedules and recorded attendance into the operational discussion. Review history and the relevant working context when an attendance question needs attention.
HR SCOPE
Leave, payroll, expenses, employee documents, hiring and lifecycle processes have different policy and implementation requirements. Bring those needs to the demo so the team can explain the available scope and agree the journeys that require configuration and validation.
Records
Employee directory, profiles, departments, teams and reporting lines.
Time and Leave
Schedules, attendance, leave policies, requests and balances.
Payroll and Expenses
Required inputs, review stages and outputs for your markets.
Employee Lifecycle
Hiring, joining, onboarding and offboarding journeys.
IMPLEMENTATION
Identify the people, policies, historical records and responsibilities involved. Agree what needs to be configured, what information will be brought in and how your team will check the result.
Explore Implementation →IDENTIFY
AGREE
FAQ
Tell us the policies, locations and outputs you need. The team can confirm the relevant capability and propose a demonstration and validation scope.
Share your policies, locations and people processes — we’ll explore the scope that fits your organisation.
Bring Your HR Workflow to the DemoTurn a plan into work your team can follow. Organise projects, break work into tasks and subtasks, and keep responsibility, dates and supporting context visible.
Workspace / Fit-outs / Riverside
Riverside Office Fit-out
Furniture schedule
+ Add task
Site brief
+ Add task
Site brief
Waiting on @Maya’s layout review before I finalise the brief.
STRUCTURE
Use workspaces, spaces and lists to reflect the way your teams organise projects. Give tasks and subtasks their own descriptions, owners, priorities and dates so the next action is clear.
VIEWS
Scan detailed records in Table or List, review stages on a Board and see dated work in Calendar or Timeline. Different views help different conversations while keeping attention on the underlying tasks.
Table & List
Scan detailed records and sort by owner, status or date.
Board
Review stages at a glance and move work between them.
Calendar
See dated work across the week or month.
Timeline
Follow dated work across the project period.
Site brief
+ Add field
CUSTOM FIELDS
Use custom fields for task codes, categories, responsibilities and other useful context. Add relationships and dependencies where work needs to refer to another record or prerequisite.
@Maya can you confirm the lighting option before Thursday?
Yes — I’ll bring it to the review meeting.
DISCUSSION
Discuss an issue, mention a participant and attach a relevant file beside the work. Link a meeting or review item so colleagues can find the background before responding.
PROGRESS
Review task and subtask status alongside your chosen progress measures. A completed checklist and a reported project milestone can describe different things; make the distinction clear in the way you manage the project.
Ask for a briefing on relevant project work and review the tasks behind the answer. Use the briefing to prepare questions and follow-ups for your team.
Explore VAV AI →✦ Project briefing · Riverside
Illustrative exampleWhat needs attention in this project?
BRIEFING
The layout review needs attention before the site brief can be updated. Review Maya’s task and confirm the next step with the team.
TASKS BEHIND THE ANSWER
SUGGESTED FOLLOW-UP
Ask Maya for an update on the layout review.
FAQ
Projects, lists, tasks and subtasks provide structure for different levels of work. The demo can show how your responsibilities and reporting needs fit that structure.
Bring one real project — we’ll show how projects, tasks, owners and dates fit the way your team already works.
Show Us Your Project WorkflowAn update is easier to use when the team can find what it refers to. Bring conversations, questions and shared files into the working context of your projects and tasks.
# riverside-fitout
Project channel · Riverside Office Fit-out
Omar10:12
Can someone confirm the ceiling height for the meeting room? @Maya
Maya10:15
2.7 m — it’s in the layout review notes. Linking the task here.
Lina10:21
Adding the supplier’s ceiling detail for reference.
MENTION SOMEONE
CONVERSATIONS
Use team and project conversations to coordinate shared work. Mention the intended participant and use a quoted reply to make the question or response clear.
TASK DISCUSSION
Keep task-specific updates beside the description, ownership and supporting files. Colleagues can review the work before joining the discussion.
Explore Projects and Tasks →Layout review
MayaYesterday
Updated layout attached — meeting room moved to the north side.
OmarYesterday
Thanks. I’ll update the site brief once this is approved.
Maya# riverside-fitout
2.7 m — it’s in the layout review notes. Ceiling height confirmed.
Omar# riverside-fitout
Can someone confirm the ceiling height for the meeting room?
Lina# procurement
Supplier needs the final ceiling height before ordering.
SEARCH
Search conversations and messages, return to relevant context and keep important discussions accessible. Shared media gives teams another route to supporting material.
Use discussion summaries to review key points and suggested follow-ups. Keep decisions, unanswered questions and proposed tasks distinguishable so the team can decide what to do next.
Explore VAV AI →✦ Discussion summary
# riverside-fitout · 14 messages today
• Meeting room ceiling height confirmed at 2.7 m.
• Which lighting option will the client choose?
• Update the site brief with the confirmed ceiling height.
IN PRACTICE
The value is a conversation people can act on with the context in view.
01Raise an issue
A team member raises an issue.
02Clarify
A colleague clarifies the requirement.
03Review the task
The team reviews the relevant task.
04Agree the next step
The team agrees the next step.
FAQ
Shared files and selected previews support team conversations. Confirm the file types and review experience your team needs during the walkthrough.
Bring one real conversation — we’ll show how discussion, tasks and files stay connected for your team.
Explore Your Team’s Collaboration WorkflowUse VAV AI to review relevant project context, understand discussion summaries and consider suggested follow-ups. Bring a clearer starting point to the questions your team needs to answer.
The layout review needs attention before the site brief can be updated. Review Maya’s task and confirm the next step with the team.
SOURCE CONTEXT
WHAT VAV AI HELPS WITH
PROJECT BRIEFING
Ask what needs attention in a project. Review a briefing that brings the relevant task context into view, then return to the work when you need the detail.
DISCUSSION SUMMARY
Use summaries to revisit key points, decisions and follow-up suggestions. Separate what was said from what still needs to be agreed.
SUGGESTED FOLLOW-UP
A useful suggestion gives the team something to consider. Review the proposed follow-up and confirm the responsibility and timing before treating it as a commitment.
The layout review is awaiting Maya’s review. Omar’s site brief is in progress and depends on the completed layout review.
The layout review needs attention before the site brief can be updated. Review Maya’s task and confirm the next step with the team.
Ask Maya for an update on the layout review.
SEE IT IN CONTEXT
IN YOUR WORKFLOW
Use a project briefing to prepare for a review, a discussion summary to catch up on the context, or a suggested follow-up to clarify what the team should consider next. Start with a defined task rather than an open-ended promise about everything in the business.
CONTEXT AND CONTROLS
Ask which sources are available, how access is handled and which actions require user review in your proposed setup. These questions belong in the demonstration and implementation discussion.
Read about Security →FAQ
This page focuses on briefings, summaries and suggestions that help people review work. Ask the team to demonstrate the exact actions supported in your intended workflow.
Source availability depends on the capability and connections involved. Tell us the information you want to use so the team can confirm the supported scope.
A clear question, relevant current records and a way to check the supporting context. Use the briefing to prepare a decision, then verify the details that matter.
Choose a workflow your team understands. We will explore how the available context can support a clearer briefing and next step.
Book a VAV AI DemoGive a review request its supporting context and bring it to the person responsible. Use task-based requests and configured notifications to organise the handoff.
REVIEW REQUEST
Bring the task, discussion and relevant files together before asking for a review. Give the reviewer a clear question and a route to the detail.
NOTIFICATIONS
A supported status-based rule can bring a task to the attention of a specified person. Explore the trigger, recipient and linked result in a practical demonstration.
CONTEXT
Use relationships and task links so a manager can understand what the review concerns. Clear context helps the person reviewing the work ask the right questions.
YOUR PROCESS
Review stages, responsibilities and outcomes with the implementation team. Agree how each step should behave before extending the workflow to additional teams or connected systems.
A project task moves to In Review. Its configured reviewer receives a notification and opens the corresponding task to inspect the supporting information.
FAQ
Downstream changes depend on the supported workflow and integration. Include the intended result in the scope discussion and validate it before rollout.
Share your routing rules so the team can confirm the appropriate configuration and supported recipient behaviour.
Bring one review step — we’ll walk through the trigger, the reviewer and the task they need to see.
Map Your Review WorkflowHow VAVOne collects, uses, shares and protects information across the website, applications, APIs and related services.
Privacy Policy
ON THIS PAGE
SECTION 1
What this Privacy Policy covers and who operates VAVOne.
VAVOne is a cloud-based business management platform operated by VAV ONE TECHNOLOGY SOLUTIONS - L.L.C - S.P.C (referred to in this Privacy Policy as “VAVOne”, “we”, “our” or “us”). Our services include customer relationship management, communications, team collaboration, work management, human resources, sales and marketing tools, automation, artificial intelligence, analytics and integrations with third-party applications.
This Privacy Policy explains the information we collect or receive, the purposes for which we process it, the parties with whom it may be shared and the rights available to individuals. It applies to the VAVOne website, applications, APIs and related services (together, the “Services”). Please read it carefully before using the Services. Additional terms may apply to particular integrations and features.
SECTION 2
Key terms used in this Privacy Policy.
SECTION 3
When VAVOne acts as a processor and when it acts as a controller.
For personal information supplied by Customers through their workspaces, VAVOne generally acts as a service provider or data processor, and the Customer determines why that information is collected and how it is used. This may include CRM records, employee information, files, leads, messages and communication histories. Customers are responsible for lawful collection, appropriate notices, consent where required, access permissions and use of the information in their workspaces.
For information relating to our own website, account administration, subscriptions, support, security and business operations, VAVOne may act as a data controller. The applicable responsibilities depend on the particular processing activity and relevant law.
SECTION 4
Account, support and workspace information collected through the Services.
When a Customer registers, requests a demonstration, subscribes or contacts us, we may collect names, business email addresses, telephone numbers, organization details, billing contacts, account settings and support correspondence.
Depending on the features a Customer enables, Customer Data may include CRM contacts, sales leads, opportunities, campaign information, tasks, documents, HR and employment-related information, meetings, recordings, transcripts, messages, attachments and other records uploaded or created by authorized Users. Customers determine which information to upload and who may access it.
SECTION 5
Technical and activity data, cookies and similar technologies.
We may collect IP addresses, browser or device information, login times, feature usage, error reports, diagnostic records and similar Usage Data. Cookies and comparable technologies may help with sign-in, session continuity, security, preferences and measurement of service performance. The availability of optional analytics cookies and consent controls depends on the website or application concerned and applicable law.
See the Cookie Policy→SECTION 6
Data received when Customers connect third-party services.
Where an authorized Customer connects a third-party service, VAVOne may receive the account identifiers, access tokens, business assets, content and records necessary to perform the enabled functions. The information received depends on the service, the permissions approved by its provider and the Customer’s choices. We do not require customers to provide their social media passwords to connect through supported authorization flows.
SECTION 7
How Meta platform data is processed for Customer-enabled features.
VAVOne may allow Customers to connect Facebook Pages, Instagram professional accounts, Meta advertising accounts, Messenger conversations and WhatsApp Business accounts. Subject to the Customer’s authorization and approved Meta APIs, information processed may include account and Page identifiers, ad campaigns and performance metrics, lead form submissions, posts, comments, messages, telephone numbers, media, message status and related business insights.
We use such information to provide the features a Customer enables, including advertising management and reporting, lead synchronization into the CRM, social publishing, comment management, authorized customer messaging, inbox workflows and operational analytics. Meta data is not accessed for unrelated purposes or sold to data brokers. The connection and permitted actions remain subject to Meta’s platform terms, policies and permissions.
A Customer may disconnect an integration or revoke authorization through the relevant platform settings. Disconnection stops future authorized access once completed; copies previously imported into the Customer workspace remain subject to the Customer’s data management instructions, retention requirements and deletion requests. Customers remain responsible for appropriate message opt-ins and lawful communication practices.
SECTION 8
Google API Limited Use commitments and other connected platforms.
Customers may choose to connect services such as Google Workspace, Google Calendar, Gmail, Google Drive, Google Ads, YouTube, Microsoft 365, LinkedIn, TikTok, Snapchat, X, Plaud, GitHub and other supported business systems. The data accessed depends on the selected integration and permissions granted. We use information from these integrations to deliver requested functions such as calendar synchronization, email and meeting support, advertising reports, content publishing and connected business workflows.
Where VAVOne uses data received from Google APIs, that use is subject to the Google API Services User Data Policy, including its Limited Use requirements. We use Google user data to provide user-facing features authorized by the Customer and do not use Google Workspace user data to develop, improve or train generalized AI or machine-learning models. Human access to Google user data is limited to circumstances permitted by the Google policy, such as an authorized support request, security purposes or legal requirements.
SECTION 9
Purposes for operating the Services, support, security and communications.
VAVOne may process information to operate and maintain the Services; authenticate Users; deliver CRM, messaging, marketing, HR, project and collaboration functions; provide connected integrations and automation; respond to support requests; communicate service notices; monitor performance; investigate faults and security incidents; administer subscriptions; and comply with legal obligations. We may use aggregated or appropriately de-identified information to understand and improve the Services.
We may send product information or marketing communications where permitted by law. Recipients can opt out using the instructions provided in the communication or by contacting us. Customers using VAVOne for their own campaigns are responsible for obtaining any required recipient consent and honoring applicable unsubscribe or opt-out requests.
SECTION 10
How AI features process information and our related commitments.
VAVOne provides AI-assisted features that may process prompts, workspace records, documents, call or meeting content, conversations and other information relevant to the action requested by a User or Customer. Information may be transmitted to an AI service provider to deliver that function. Customers should use appropriate access controls and avoid processing information through optional features without a lawful basis.
The AI-related providers identified in our service documentation include OpenAI, xAI, OpenRouter and Google Cloud Document AI. The involvement of a particular provider depends on the enabled feature and configuration. Customers should review material AI outputs before relying on them for important decisions. Any representation concerning model training or provider retention practices must follow the applicable product configuration and provider agreements.
SECTION 11
Third parties that support hosting, AI, messaging, analytics, maps and payments.
We may engage Service Providers to support hosting, communications, analytics, artificial intelligence, payments, mapping and technical operations. The providers and technologies identified in VAVOne’s current service documentation include:
Oracle Cloud Infrastructure provides cloud hosting, database management, and file and object storage services for VAVOne. Our application infrastructure uses Oracle Cloud regions in Abu Dhabi, United Arab Emirates, and Mumbai, India. For more information about Oracle's privacy practices, please visit: Oracle Services Privacy Policy.
OpenAI provides artificial intelligence models that support VAVOne's AI-powered assistance, content generation, data analysis, and intelligent business workflows. Information submitted through AI-enabled features may be processed by OpenAI to generate responses and perform requested tasks. For more information about OpenAI's privacy practices, please visit: OpenAI Privacy Policy.
xAI provides artificial intelligence language models used to support AI-powered assistance and automated business processes within VAVOne. Information processed through these models is used to generate responses and provide the AI functionality requested by users. For more information about xAI's privacy practices, please visit: xAI Privacy Policy.
OpenRouter provides access to multiple artificial intelligence models through a unified API platform. VAVOne uses OpenRouter for AI model routing and access to additional AI service providers, allowing supported AI features to process user requests through the selected models. For more information about OpenRouter's privacy practices, please visit: OpenRouter Privacy Policy.
Google Cloud Document AI provides document processing and information extraction services. VAVOne uses this technology to extract text and structured information from uploaded documents, supporting document intelligence and related business workflows. For more information about Google's privacy practices, please visit: Google Privacy Policy.
Firebase Cloud Messaging is a cross-platform messaging service provided by Google that enables applications to deliver push notifications to users. VAVOne uses this service to send application notifications, alerts, reminders, and other relevant updates to supported web and mobile devices. For more information about Google's privacy practices, please visit: Google Privacy Policy.
LiveKit provides real-time communication infrastructure for voice and video interactions. VAVOne uses LiveKit to support real-time audio and video communication features, enabling users to participate in calls and other supported communication activities within the platform. For more information about LiveKit's privacy practices, please visit: LiveKit Privacy Policy.
VAVOne uses email delivery services based on the Simple Mail Transfer Protocol (SMTP) to send transactional and service-related communications, including account invitations, password reset instructions, system notifications, and other important account updates. Information required for email delivery may be processed by the configured email service provider. The applicable privacy policy depends on the SMTP provider used by VAVOne.
Google Analytics is a web analytics service offered by Google that tracks and reports website traffic and application usage. VAVOne uses Google Analytics to understand how visitors and users interact with our website and services, evaluate engagement, identify areas for improvement, and enhance the overall user experience. For more information about Google's privacy practices, please visit: Google Privacy Policy.
Firebase provides application analytics and performance monitoring services developed by Google. VAVOne uses Firebase to monitor mobile application activity, understand user interactions, identify application crashes, and improve the reliability and performance of our services. For more information about Google's privacy practices, please visit: Google Privacy Policy.
Google Maps is a mapping and location-based service provided by Google. VAVOne uses Google Maps to support address searches, geographical information, location identification, and mapping features within the platform. For more information about Google's privacy practices, please visit: Google Privacy Policy.
OpenStreetMap is an open geographic data project that provides map information, while Nominatim offers geocoding services for searching and identifying geographical locations. VAVOne uses these services to support address lookup and conversion of location information into geographical coordinates. For more information about OpenStreetMap's privacy practices, please visit: OpenStreetMap Privacy Policy.
Facebook and Instagram advertising and remarketing services are provided by Meta Platforms, Inc. and its applicable affiliates. VAVOne enables businesses to connect their Facebook and Instagram accounts to manage advertising campaigns, monitor performance, generate leads, and access advertising reports through supported Meta integrations. Where remarketing technologies are used on our website, Meta may collect and process information about website interactions to support advertising measurement and personalized advertisements, subject to applicable permissions and consent requirements. Users can learn more about Meta's advertising practices and manage their advertising preferences through Meta Accounts Center.
Apple provides payment processing services for eligible subscriptions and purchases made through applications distributed on the Apple App Store. For more information about Apple's privacy practices, please visit: Apple Privacy Policy.
Google Play provides payment processing services for eligible subscriptions and purchases made through Android applications distributed on the Google Play Store. For more information about Google's privacy practices, please visit: Google Privacy Policy.
Network International provides electronic payment processing and merchant payment solutions. VAVOne uses Network International to support payment transactions for applicable subscriptions and services. Payment-related information may be processed by Network International to authorize transactions, facilitate payments, prevent fraud, and meet applicable financial and regulatory requirements. For more information about Network International's privacy practices, please visit: Network International Privacy Notice.
These providers may process information according to the services they supply. Not every provider receives every Customer’s data. The set of providers used may change as features and integrations evolve. Further information about relevant providers may be requested at privacy@vavone.com.
SECTION 12
When information may be shared and what we do not sell.
We may share information with a Customer’s authorized Users; Service Providers working on our behalf; third-party platforms that the Customer chooses to connect; professional advisers where necessary; and public authorities where disclosure is legally required. Information may also be transferred in connection with a business restructuring, merger or acquisition, subject to applicable legal protections.
We do not sell Customer Data or Meta Platform Data. We do not give third-party advertisers independent access to Customer workspace content for their own advertising purposes.
SECTION 13
Contract, legal obligation, legitimate interests and consent where required.
Where applicable data protection laws require a legal basis, processing may be based on performance of a contract, compliance with a legal obligation, legitimate interests that are not overridden by applicable individual rights, or consent where legally required. The appropriate basis depends on the service, information involved and jurisdiction. Customers are responsible for identifying appropriate grounds for processing personal information for their own business purposes.
SECTION 14
How long information is kept and how deletion requests are handled.
We retain personal information for as long as necessary to provide the Services, fulfil the purposes described in this Policy, comply with applicable laws, resolve disputes and protect our legal rights. Retention depends on the nature of the information, Customer instructions and agreements, operational requirements and legal obligations. Customers may request deletion of eligible information, subject to applicable legal and technical limitations. Information contained in backups may be removed through applicable backup retention and rotation procedures.
SECTION 15
Cross-border processing and transfer safeguards.
VAVOne uses cloud infrastructure for its Services. Some Service Providers and connected third-party platforms may process information in countries other than the country where a Customer or individual is located. Where required by applicable law, we use appropriate contractual, technical or organizational measures for international data transfers.
SECTION 16
Technical and organizational measures used to protect personal information.
We use technical and organizational measures intended to protect personal information from unauthorized access, loss, misuse, alteration or disclosure. These may include access management, security monitoring and protections appropriate to the Services. Customers are responsible for safeguarding their account credentials and managing authorized Users. Although we work to protect personal information, no internet-based system can be guaranteed completely secure.
SECTION 17
Access, correction, deletion and related rights under applicable law.
Subject to applicable law, individuals may be entitled to request access to, correction or deletion of personal information, to object to or restrict certain processing, to withdraw consent where applicable, or to request data portability. We may need to verify the identity and authority of a requester before responding.
If VAVOne processes your information on behalf of your employer or another Customer, please contact that organization first. We will assist the Customer in handling valid requests where appropriate. For requests relating to information that VAVOne controls, email privacy@vavone.com.
SECTION 18
How to request deletion and what happens when integrations are disconnected.
To request deletion of information held by VAVOne, contact privacy@vavone.com with the subject VAVOne Data Deletion Request. Include the relevant account or business name and a description of the information concerned, but do not include passwords or API secrets. We may seek verification and coordinate with the relevant Customer before taking action.
Disconnecting Facebook, Instagram, Messenger, WhatsApp, Google or another integration stops further access through the disconnected integration once processed. It does not automatically delete previously synchronized CRM records, and data held by the third-party platform must be managed under that platform’s own processes. Deletion requests will be handled according to applicable law, contractual responsibilities and valid retention requirements.
SECTION 19
Third-party sites linked from the Services.
The Services may contain links to websites or applications operated by third parties. We do not control their privacy practices. Users should review the privacy policies and terms of those services before providing personal information.
SECTION 20
VAVOne is intended for business use by adults.
VAVOne is designed primarily for business use and is not intended for independent registration by children under 18. If you believe a child’s information has been processed improperly, please contact privacy@vavone.com so the matter can be reviewed.
SECTION 21
Subscription cancellation and refund terms.
Customers may cancel their subscriptions at any time in accordance with the applicable subscription terms. However, no refunds, credits, or prorated reimbursements will be provided for any unused portion of a monthly or annual subscription period.
SECTION 22
How updates to this Privacy Policy are published.
We may revise this Privacy Policy from time to time to reflect changes in our Services, legal requirements or data handling practices. The updated policy will be published on our website with a revised date. Where required, we will provide additional notice of material changes.
SECTION 23
How to reach VAVOne about privacy and data deletion.
VAV ONE TECHNOLOGY SOLUTIONS - L.L.C - S.P.C
Musaffah MW4, Abu Dhabi, United Arab Emirates
Website: https://vavone.com
Privacy and data deletion enquiries: privacy@vavone.com
Last updated: 16 October 2026
Email privacy@vavone.com for privacy and data deletion enquiries, or use the contact form.
Explore guides to organising project reviews, using AI briefings and keeping responsibility connected to the work. Start with a practical method, then see how it can inform your VAV One workflow.
“Confirm whether the layout is ready for the site brief to be updated.”
From Guide 01 · Project reviews
Each guide walks through a method step by step, then shows where it can connect to your workflow in VAV One.
Prepare the review question, identify the owner and organise the information needed for a useful discussion.
INSIDE THIS GUIDE
Ask a focused question, review the supporting context and check the next step before making a commitment.
INSIDE THIS GUIDE
Learn more about Projects, Team Chat, Workflows and Approvals, Management Insights and VAV AI.
Have a workflow you want to explore? Book a demonstration around the people, information and decisions that matter to your team.
An AI briefing can help a team orient itself, but the value depends on the question, available records and review that follows. Treat the answer as a way into the work.
What needs attention before this project’s review?
Illustrative example
Educational guidance. Examples are illustrative, use a fictional project and do not imply general AI accuracy or data access.
Choose a project and a useful purpose. “What needs attention before this project’s review?” is easier to assess than “Tell me everything about the business.” Include the time period or scope when it matters.
“Tell me everything about the business.”
“What needs attention before this project’s review?”
Review the task context and available sources. Confirm the dates, status and ownership of the records that influence the answer. Missing information should lead to a question, not an assumption.
Records behind the answer
IllustrativeMissing information → a question, not an assumption.
A task awaiting review is a recorded state. Asking its owner for an update is a suggested action. Keep those concepts separate so a proposed follow-up does not look like an agreed commitment.
The person who wrote a message is not always the person responsible for the next task. Check the intended owner and ask for confirmation where a deadline or commitment is inferred.
“The site brief should be updated once the layout is signed off — ideally by Friday.”
When a briefing mentions cost, progress or performance, verify the underlying definition and data. A language summary does not replace a reconciled calculation.
“Fit-out progress is at 60%.”
Language summaryUse the briefing to identify questions, prepare the review and reduce the effort of finding context. The final decision should reflect the source records and the people responsible for the work.
AI briefing
Orientation and context
Questions
3 items for the review
Team review
Thu 24 Sep · source records open
Decision
Made by the people responsible
A QUICK BRIEFING CHECK
See a project-context example, review a discussion summary and examine suggested follow-ups in a focused demonstration.
A status meeting becomes more useful when everyone understands the question being discussed. Prepare a small set of review items with a clear owner, relevant context and a defined next step.
REVIEW ITEM · RIVERSIDE OFFICE FIT-OUT
In ReviewConfirm whether the layout is ready for the site brief to be updated.
Illustrative example
Educational guidance. Examples are illustrative and use a fictional project.
Write what the team needs to resolve. “Review the layout” is less useful than “Confirm whether the layout is ready for the site brief to be updated.” A specific question helps participants bring the right information.
“Review the layout”
“Confirm whether the layout is ready for the site brief to be updated.”
Record the person responsible for the work and the person being asked to review it. These may be different people. Keep the distinction visible so a request does not disappear into a general discussion.
Prepares the layout and answers questions about it.
Confirms whether the layout is ready for the next step.
Link the task, current description, dates, discussion and supporting files. A review should make it easy to inspect the detail behind a status rather than treating the summary as the whole record.
STATUS SUMMARY
Layout review
The summary is the doorway — not the whole record.
A percentage may describe checklist completion, a manual estimate or physical delivery. State what the measure means. Do not assume two percentages are comparable because they appear on the same dashboard.
Same number, three different meanings
IllustrativeKeep the agenda tied to the review items. Identify what has been agreed, what needs more information and who will follow up. Confirm dates with the people responsible.
Layout ready for the site brief update
RecordedFurniture schedule lead times
Lina to checkUpdate the site brief
Omar · date to confirmRecord the agreed update in the relevant working context. If an automation is meant to notify someone or change a record, check that the intended result actually occurred.
Meeting outcome
Site brief to be updated
Recorded in the task
Update added to the working context
Automation
Notify Omar of the change
Check it happened
Omar received the notification
A SIMPLE PREPARATION CHECKLIST
Projects, task discussions, linked meetings and review requests can support a more structured review. Bring a representative process to a demo and examine the workflow with your team.
Access, hosting and data handling are part of evaluating a business platform. Bring your requirements to the VAV One team so the proposed setup can be reviewed against your organisation’s needs.
Bring your requirements into the conversation early. Each area is reviewed against the proposed setup and your organisation’s needs.
Review the roles, users and organisational boundaries involved in the workflow. Ask how the proposed setup handles access to records, connected systems and AI context.
Discuss the required deployment location, retention, backup, export and recovery arrangements. Confirm which commitments apply to application data and which apply to connected services.
Review the sources used in your intended AI workflows, the processing involved and the actions available to users. Clarify how those requirements fit the agreed deployment.
Tell us which documentation and questions your IT, security or procurement team needs to review. The team can identify the material relevant to the proposed scope.
“Where is our information held?” can have a different answer for application storage, backups, logs and AI processing. Ask for each one to be confirmed on its own, for the scope you are proposing.
A clear sequence your IT, security, procurement and legal owners can follow — so nothing is assumed before it is confirmed.
STEP 01
Roles, required locations, data categories and the AI workflows you intend to use.
STEP 02
Walk through the proposed setup with the VAV One team against your organisation’s needs.
STEP 03
The team identifies the documentation that applies to the proposed scope.
STEP 04
Check published and contractual commitments against the proposed service.
FAQ
Yes. Include the required locations and data categories in the assessment so the team can confirm the available deployment and processing scope.
Request a technical discussion and provide your assessment requirements. Published and contractual commitments should be checked against the proposed service.
Tell us your roles, required locations, data categories and the questions your IT, security or procurement team needs answered.
Questions?Contact the VAV One team
Choose the workspace your organisation uses.
Open your organisation’s work and collaboration environment.
Open your customer relationship and follow-up workspace.
Need help finding your workspace?
Check with your organisation’s administrator or contact the VAV One team.
New to VAV One? Explore the platform or book a demo.
© 2026 VAV One
Different teams ask different questions. VAV One helps you explore the combination of work, people, customer and review tools that fits your operational priorities.
FOR PROJECT TEAMS
Keep responsibility visible from plan to review.
Organise tasks, discussions and supporting information around the work being delivered. Prepare the next review with the relevant context in view.
MODULES INVOLVED
FOR HR AND OPERATIONS TEAMS
Give everyday people processes a clearer structure.
Bring employee information, schedules and attendance into the working picture. Discuss the policies and HR journeys your organisation needs.
MODULES INVOLVED
Can we see an option with a larger waiting area?
FOR SALES TEAMS
Know what happens after the enquiry.
Organise customer context, conversations and next actions so the sales team can follow up with purpose.
Explore Sales Follow-up →FOR MANAGERS AND LEADERS
Move from the status to the source.
Review the projects and items that need attention, then open the tasks and information behind them.
MODULES INVOLVED
Bring the people involved, the steps they follow and the information they need. The VAV One team can help you explore the relevant modules and agree a practical demonstration scope.
HR and operations teams work across employee information, schedules, requests and internal follow-up. VAV One helps bring structure to that work so the relevant people and records are easier to find.
Review employee records, departments, positions and team context. Give the operational discussion a clear reference for who works where and who is responsible.
Review the working calendar and recorded attendance when discussing day-to-day staffing questions. Use the relevant history and context rather than relying on an isolated number.
Identify the next action, the person responsible and the supporting information. Use the relevant work and review tools to organise coordination around HR requirements.
Leave, payroll, expenses and employee lifecycle processes need rules and data that fit your organisation. Discuss the intended outcome, available capability and validation approach before rollout.
Fictional employee data · follow-up created by a person
Used as applicable to your process
FAQ
Yes. Bring a priority such as employee records, schedules or attendance visibility and the team can focus the walkthrough accordingly.
Your locations, teams, policies, existing records and the roles that need access provide a useful starting point.
Bring one HR priority — records, schedules or attendance — and we’ll focus the walkthrough on it.
Discuss Your People Operations WorkflowManagers need to understand what requires attention, who is responsible and what information supports the next decision. VAV One helps organise that review around the underlying work.
Review relevant projects, dates and pending questions in a configured management view. Keep the overview focused enough to guide the conversation.
Make responsibility visible alongside the work. When a review needs an update, the team should know which person and task to return to.
Move into linked tasks, discussions and files when a status needs explanation. Make the review about the information available and the decision required.
Review a briefing on relevant project context before the discussion. Check the sources, clarify assumptions and consider the suggested follow-up with the team.
Illustrative data · due dates and named owners first
Open the project overview
Riverside Office Fit-out
Inspect the item
Layout review awaiting decision
Read the supporting task
Files and latest discussion
Prepare the question
For Maya, the responsible person
FAQ
Discuss the decisions, source records and measures you need. A useful management view starts with agreed definitions and a tested route to the underlying work.
The scope depends on the available records, calculations and connections. Review the intended measures and data sources during implementation planning.
Bring the decisions you prepare each week — we’ll shape a calm overview with a clear route to the source work.
Build a Demo Around Your Management ReviewProject teams need more than a list of open tasks. They need clear responsibilities, useful updates and the context to resolve the next issue. Bring those parts of delivery into one structured workflow with VAV One.
@Maya is the meeting room staying on the north side?
Is the revised layout ready for the client?
Break the project into lists, tasks and subtasks. Assign the people responsible and record the dates, priorities and detail needed to start the work.
Discuss questions inside the task, mention the relevant participant and attach supporting material. Make it easier for someone joining the conversation to understand the issue.
Updated layout attached — meeting room moved to the north side.
Thanks. I’ll update the site brief once this is approved.
Link the tasks that need attention, identify the review question and bring the supporting information into view. Use a meeting agenda to focus the discussion.
Open related work and responsibilities before agreeing a follow-up. Use VAV AI project context as preparation, then check the detail with the team.
Configured example · not a prebuilt construction engine
Each links to its module page
FAQ
Bring a sample project structure and review process. The demo can explore the relevant statuses, fields and relationships.
Include it in the system discussion. Confirm the required information flow and available integration before relying on it in the project workflow.
Bring one real project — we’ll map its tasks, discussions, reviews and decisions into a configured example.
Show Us a Project That Needs Clearer CoordinationAn enquiry becomes useful when someone knows what to do with it. Give sales teams a structured view of the customer context, the conversation and the follow-up that needs attention.
Needs space for two desks and good natural light.
Can the office be ready before January?
@Maya can we propose two layout options?
Find the relevant customer-facing record and review the information available. Capture the context your team needs to understand the request.
Review what has been discussed and identify what still needs an answer. Give the person following up a clear starting point.
Can the office be ready before January?
@Maya can we propose two layout options for the villa office?
Yes — two options ready by Friday.
Keep the follow-up owner and pipeline context visible. Review where the opportunity stands and what the team needs to do next.
Discuss how your divisions, teams and existing systems should contribute to the sales workflow. Confirm any connected customer or transaction information before relying on it.
Fictional customer · one assigned follow-up
Enquiry
Villa office conversion
Customer context
Yusuf Ali · homeowner
Conversation
January finish asked
Assigned follow-up
Sara · Mon 28 Sep
Pipeline review
Enquiry → Follow-up
BEFORE THE DEMO
One typical enquiry
A real request your team handles
Your stages
How opportunities move today
Channels involved
Where conversations happen
Managers’ questions
What they ask about follow-up
Each links to its module page
FAQ
Discuss the division and team structure you need, including access and reporting expectations, so the proposed setup can be reviewed.
Include any AI-assisted communication requirements in the demonstration discussion. Automatic outreach should be evaluated as a specific capability and authorised workflow.
Bring one typical enquiry — we’ll follow it from customer context to an assigned next step.
Explore a Clearer Customer Follow-up JourneyThese Terms of Service govern access to and use of VAVOne websites, applications, software, APIs, and business management services.
Terms of Service
Customer Agreement
ON THIS PAGE (26 SECTIONS)
SECTION 1
Binding agreement between you and VAVOne governing access and use of the Services.
These Terms of Service (the “Terms”) form a legally binding agreement between VAV ONE TECHNOLOGY SOLUTIONS - L.L.C - S.P.C (“VAVOne,” “we,” “us,” or “our”) and the individual or legal entity accessing, subscribing to, or using VAVOne (“Customer,” “you,” or “your”). They govern access to our websites, applications, software, application programming interfaces (APIs), and related services (collectively, the “Services”).
By creating an account, accepting these Terms electronically, subscribing to a plan, or using the Services, you agree to be bound by these Terms and our Privacy Policy. If you use the Services on behalf of an organization, you represent that you have the authority to enter into this agreement on its behalf. In that case, “Customer” refers to the organization. If you do not accept these Terms, do not access or use the Services.
You must be at least 18 years old, or the legal age of majority in your jurisdiction if higher, and legally capable of entering into an agreement. An organization is responsible for the activities of its employees, administrators, agents, and other authorized users who access its VAVOne workspace.
SECTION 2
Cloud-based business management platform features, capabilities, and availability.
VAVOne is a cloud-based business management platform. Depending on the subscription plan and activated modules, the Services may include customer relationship management (CRM), sales and lead management, work and project management, human resources and recruitment workflows, collaboration and communication, business reporting and insights, artificial intelligence assistance and automation, advertising and social media management, and connections to external services.
Features, usage limits, storage allowances, access levels, integrations, and availability vary by plan and may change as the Services develop. Unless expressly stated in the applicable subscription order, no particular feature, integration, or third-party capability is guaranteed to remain available indefinitely.
SECTION 3
Responsibilities for account credentials, workspace roles, and security compliance.
You agree to provide accurate registration, billing, and account information and keep it current. You are responsible for protecting account credentials, assigning appropriate access permissions, managing authorized users, and promptly informing us if you suspect unauthorized use or a security incident involving your account.
Customer administrators control user invitations, roles, access privileges, and workspace settings. You are responsible for ensuring that each authorized user complies with these Terms. We may require verification of identity or account authority before responding to sensitive account requests.
You must not share credentials in a manner that circumvents plan restrictions or attempt to obtain access to another customer's organization or data.
SECTION 4
Monthly billing, automatic renewal terms, applicable taxes, and price adjustments.
VAVOne offers paid subscription plans on a monthly billing basis. The applicable fees, included features, limits, and any separately purchased add-ons are described at checkout, on our published pricing pages, or in an accepted written order. Subscription fees are payable in the currency and on the payment terms presented at purchase.
Subscriptions automatically renew for successive monthly billing periods unless cancelled before the next renewal. By selecting an automatically renewing subscription and providing a payment method, you authorize the applicable recurring charges as disclosed at purchase, subject to payment provider requirements and applicable law.
Subscription fees do not include applicable value-added tax or other government charges unless expressly indicated. Customers are responsible for legally applicable taxes, which may appear separately on an invoice. Fees for optional add-ons or usage in excess of included limits may be charged separately where disclosed and accepted.
We may change published prices or plan offerings. Changes to the recurring price of an existing subscription will be communicated in advance where required by law and generally apply from a subsequent billing cycle, not retroactively to periods already paid for.
SECTION 5
Immediate prorated upgrades and end-of-billing-cycle downgrade policies.
Customers may upgrade to a higher subscription plan at any time, subject to available account controls and successful payment. An upgrade takes effect when processed. The additional subscription charge for the remaining portion of the current monthly billing cycle will be calculated on a prorated basis, accounting for any applicable unused-plan credit. The full price of the upgraded plan will apply to subsequent monthly renewals.
Customers may request a downgrade to a lower subscription plan. Unless otherwise agreed, the downgrade takes effect at the beginning of the next billing cycle. The current plan remains available until the paid period ends. Following the downgrade, access to features, users, storage, integrations, or other capacities beyond the limits of the new plan may be restricted. Customers should review plan limits and export or manage relevant data before the change takes effect.
SECTION 6
Cancellation procedures, non-refundable subscription payments, and access duration.
Customers may cancel automatic renewal at any time through available account settings or by contacting VAVOne through the support channel identified in their account or subscription correspondence. A cancellation requested before the next renewal takes effect at the end of the current paid billing period. Paid features ordinarily remain accessible until that date, subject to these Terms and any suspension for serious violations.
All subscription payments are non-refundable except where required by applicable law or expressly agreed in writing by VAVOne. We do not provide refunds, credits, or prorated reimbursements for unused portions of monthly subscriptions after cancellation. Cancellation does not eliminate charges already incurred or amounts due for Services provided before the effective cancellation date.
SECTION 7
Third-party payment gateways, payment authorization, and overdue invoice handling.
Payments may be handled by authorized third-party payment service providers, including Network International and, where available, Apple App Store or Google Play in-app billing. The selected provider's payment terms and privacy policies may also apply. Payment options differ by purchase channel and jurisdiction.
You authorize processing of charges for your selected plan and applicable add-ons. If payment fails or an invoice remains overdue, we may notify you and, after reasonable notice where practicable, suspend or restrict paid Services until outstanding amounts are settled. Any billing dispute should be reported promptly with the relevant invoice and transaction details.
SECTION 8
Customer retention of data ownership and limited operational rights granted to VAVOne.
As between VAVOne and the Customer, the Customer retains ownership of the business records, contacts, messages, documents, files, and other content uploaded to or generated within the Customer's workspace (“Customer Data”), excluding VAVOne's software and underlying intellectual property.
The Customer grants VAVOne a limited right to host, store, transmit, process, display, and otherwise use Customer Data as necessary to provide, maintain, secure, support, and improve the Services in accordance with these Terms, our Privacy Policy, and applicable data processing agreements. The Customer is responsible for ensuring it has a lawful basis and all necessary rights, notices, and permissions to submit and process Customer Data, including third-party personal information and confidential business material.
The Customer controls which authorized users may access its workspace and is responsible for the legality, accuracy, and appropriateness of its content, including communications sent using VAVOne.
SECTION 9
Controller and processor roles in accordance with the VAVOne Privacy Policy.
Our handling of personal data is described in the VAVOne Privacy Policy, published at https://vavone.com/privacy-policy. Depending on the data and context, VAVOne may act as a controller for its own account and commercial information or as a processor/service provider for information managed by a Customer in its workspace.
The Customer remains responsible for its own privacy notices, consent management, marketing permissions, retention choices, and compliance obligations when using the Services. Requests about personal data controlled by a Customer should generally be directed to that Customer first. Requests concerning VAVOne's own processing can be sent to privacy@vavone.com.
SECTION 10
Connecting Meta, Google, Microsoft and other external platforms and API dependencies.
VAVOne may allow Customers to connect optional third-party accounts and services, such as Meta platforms (Facebook, Instagram, Messenger and WhatsApp), Google services, Microsoft services, advertising channels, communications systems, maps, and other supported applications. A Customer must have the authority to connect each account and permit the associated data exchange.
Connected third-party services are governed by their own policies, terms, permissions, technical limitations, availability, and approval requirements. Third parties may modify, limit, interrupt, or discontinue their APIs or integrations, which may affect VAVOne functionality. We are not responsible for independently controlled third-party outages or policy decisions, except to the extent required by applicable law or our express written commitments.
Disconnecting an integration ordinarily stops further authorized synchronization through that connection; handling of previously synchronized data is subject to workspace controls, the Privacy Policy, and applicable law.
SECTION 11
Compliance with marketing laws, telecommunications regulations, and platform rules.
When using messaging, broadcasting, customer communication, lead management, advertising, or social publication tools, the Customer is responsible for the content it sends or publishes, the audiences it selects, and its compliance with applicable marketing, telecommunications, consumer protection, privacy, and platform rules.
Customers must obtain required opt-ins or other lawful permissions, honor opt-out requests, and avoid unsolicited messages, misleading claims, prohibited goods or services, deceptive advertisements, and misuse of personal information. Third-party platforms may review, reject, remove, or restrict content or connected accounts under their own rules.
SECTION 12
Human oversight requirement, output verification, and AI add-on conditions.
Some VAVOne features use artificial intelligence, machine learning, document extraction, or automated workflows. AI-generated text, classifications, recommendations, summaries, and other outputs may be incomplete, inaccurate, or unsuitable for a particular decision. The Customer is responsible for reviewing outputs and maintaining appropriate human oversight, especially in employment, financial, legal, healthcare, or other consequential contexts.
The Customer must not use AI features to violate law, third-party rights, platform policies, or applicable provider restrictions. AI functionality may rely on external AI or infrastructure providers as described in the Privacy Policy. Access to AI features, any AI credits, and paid AI add-ons are subject to the applicable plan and purchase terms.
SECTION 13
Restrictions against security violations, scraping, spam, reverse engineering, and misuse.
You must use the Services only for lawful, authorized business purposes. You may not misuse VAVOne, including by attempting unauthorized access; disrupting networks or security controls; distributing malware; conducting abusive scraping; infringing intellectual property or privacy rights; uploading illegal or malicious material; sending spam; impersonating others; engaging in fraud or harassment; or using the Services to bypass third-party platform restrictions.
You may not reverse engineer, resell, sublicense, reproduce, or create competing derivative products from the Services except where expressly permitted by law or authorized in writing. We may investigate suspected violations and take proportionate action, including warning, feature restriction, account suspension, or termination, subject to applicable law.
SECTION 14
VAVOne platform ownership and limited customer internal operational license.
VAVOne and its licensors retain all rights, title, and interest in the Services, software, interfaces, documentation, branding, trademarks, and related technology. Subject to payment of applicable fees and compliance with these Terms, we grant the Customer a limited, non-exclusive, non-transferable right to access and use the Services for its internal business operations during the subscription term.
No ownership of the VAVOne platform is transferred to the Customer. The Customer retains its rights in Customer Data. References to third-party products and trademarks identify their respective owners and do not imply endorsement.
SECTION 15
Unrestricted permission to incorporate product improvement ideas without compensation.
If you voluntarily provide suggestions or feedback concerning the Services, you grant VAVOne permission to use that feedback to develop and improve our products without an obligation to compensate you. This provision does not transfer ownership of confidential Customer Data or override our confidentiality and privacy obligations.
SECTION 16
Scheduled maintenance, service modifications, and availability disclaimers.
We aim to provide a reliable service but may conduct scheduled maintenance, emergency repairs, security updates, or other changes. We may introduce, modify, or discontinue features as business and technical needs evolve. When a material change significantly reduces paid functionality, we will provide notice where reasonably practicable or legally required and address applicable contractual remedies.
We do not guarantee uninterrupted access or that all software defects, third-party interruptions, or connectivity problems can be eliminated.
SECTION 17
Grounds for account suspension, termination effects, and surviving legal obligations.
We may suspend or restrict access where reasonably necessary to address suspected misuse, material breach, nonpayment, security threats, legal obligations, or third-party restrictions. Where appropriate and practicable, we will provide notice and an opportunity to remedy the issue.
Customers may terminate their subscription in accordance with Section 6. After the paid term ends or the account is terminated, access to paid features may cease. Data access, export, retention, and deletion after termination are governed by the applicable plan arrangements, Privacy Policy, and any agreed data processing terms. We do not promise a specific post-termination data availability or deletion period in these Terms unless separately agreed.
Provisions that by their nature should survive termination, including accrued payment obligations, intellectual property protections, confidentiality and data protection obligations where applicable, liability limitations, and dispute provisions, will continue to apply.
SECTION 18
Disclaimer of responsibility for third-party websites, tools, and external content.
The Services may contain links to external websites, documentation, tools, or content that we do not operate. Their terms, policies, security, and content are controlled by their respective operators. You should review those policies before using an external service.
SECTION 19
Services provided on an 'as available' basis without implied warranties.
Except as expressly stated in a written agreement and to the maximum extent permitted by applicable law, the Services are provided on an “as available” basis. We do not warrant that the Services will be uninterrupted, error-free, or suitable for every Customer's specific requirements, or that outputs and third-party information will always be accurate. Nothing in these Terms excludes any warranty or consumer or statutory right that cannot lawfully be excluded.
SECTION 20
Exclusion of consequential damages and aggregate liability cap equal to 12 months' fees.
To the maximum extent permitted by applicable law, neither party will be liable to the other for indirect, incidental, special, punitive, or consequential losses, including loss of profits, business opportunities, or anticipated savings, arising from these Terms or use of the Services, regardless of the legal theory asserted, where such exclusions are legally permitted.
VAVOne's total aggregate liability arising out of or relating to the Services will not exceed the subscription fees actually paid by the Customer to VAVOne during the 12 months immediately preceding the event giving rise to the claim, unless a different limit is agreed in writing or applicable law requires otherwise. This cap is a proposed commercial term and must be approved by VAVOne's legal and commercial team before publication.
Nothing in these Terms limits liability where limitation is prohibited by law, including for fraud or willful misconduct where applicable.
SECTION 21
Customer defense and indemnification obligations regarding unlawful content and breaches.
To the extent permitted by applicable law, the Customer agrees to defend and indemnify VAVOne against third-party claims, losses, and reasonable costs arising from the Customer's unlawful content, infringement of third-party rights, or material breach of these Terms, except to the extent caused by VAVOne's own breach or wrongful conduct. VAVOne will provide reasonable notice of such claims and an opportunity for the Customer to participate in their defense, subject to the circumstances.
SECTION 22
Relief from liability for uncontrollable events and infrastructure outages.
Neither party will be responsible for delay or failure to perform obligations, other than payment obligations already accrued, caused by circumstances beyond its reasonable control, including natural disasters, severe network failures, governmental measures, war, labor disruptions, or widespread third-party infrastructure incidents. The affected party will take reasonable steps to reduce the impact and resume performance.
SECTION 23
Notification of revisions and acceptance through continued usage.
We may update these Terms to reflect changes in the Services, legal requirements, or business practices. The revised version will be published on our website with an updated effective date. For material changes, we will provide reasonable prior notice through the Service or by email where practicable or legally required. Continued use after updated Terms take effect constitutes acceptance where permitted by law; otherwise, we will obtain any required additional consent.
SECTION 24
Laws of the United Arab Emirates and exclusive jurisdiction of Abu Dhabi courts.
These Terms are governed by the applicable laws of the United Arab Emirates, as applied in the Emirate of Abu Dhabi, without prejudice to mandatory rights under applicable law. Subject to any legally mandatory alternative forum, disputes arising from these Terms will be submitted to the competent courts of Abu Dhabi, United Arab Emirates. Parties should first attempt to resolve disputes through good-faith discussions.
SECTION 25
Severability, non-waiver, assignment terms, and entire agreement integration.
If any provision of these Terms is held unenforceable, the remaining provisions remain in effect. Our failure to enforce a provision does not waive the right to enforce it later. Neither party may transfer this agreement in a manner prohibited by applicable law; the Customer may not assign its rights without prior written consent, except as agreed in writing. These Terms, the Privacy Policy, any applicable order, and any mutually executed data processing or service agreement constitute the parties' agreement regarding the Services, subject to the agreed order of precedence in those documents.
Electronic notices may be sent to the contact email associated with the Customer account. Customers should maintain valid and monitored account contact details. Section headings are for convenience and do not change the meaning of the Terms.
SECTION 26
Official corporate identity, registered address, and privacy contact details.
Musaffah MW4, Abu Dhabi, United Arab Emirates