Terms: Product Description, Not a Binding Contract
The text below explains how volbor is designed to be used. This is not a formal public offer, legal contract, or substitute for legal counsel. Legal entity, registered address, and governing jurisdiction are not published on this public marketing site: do not infer applicable law or jurisdiction from the page language. Any binding agreement accepted during checkout or account onboarding in the application dashboard supersedes this informational page. If discrepancies arise, the in-app dashboard agreement governs.
Do not cite this website page in your own customer contracts as vendor company details.
Relying on Website Copy
- Treating website copy as a binding contract: disputes regarding payments and customer data are conducted based on marketing paragraphs rather than in-dashboard agreements.
- Treating shared credentials as normal practice: makes it impossible to audit who accepted terms or who responded to a customer.
- Sending unauthorized broadcasts "on behalf of the tool": connecting a messaging channel does not grant automatic consent to message recipients.
- Inferring uptime guarantees from marketing collateral: this informational page does not provide guaranteed availability SLA percentages.
Responsibilities
The workspace belongs to the team members you invite
Access is granted to specific individual users and roles, as detailed on the security page. Sharing passwords bypasses these audit trails. Replies sent to customers from the workspace are executed by your team, not an anonymous software service.
Channels and bot copy are your commitment domain
Operating hours, pricing, stock levels, and fulfillment times communicated by your chatbot must be configured and maintained by you. The platform does not verify inventory accuracy against your warehouse until you configure external data synchronizations and confirm they are actively responding.
A contact list does not confer the legal right to message
Connecting a communication channel does not grant recipient consent for promotional messaging. The broadcasts and reactivation workflow does not override applicable compliance standards. You determine recipient eligibility and legal grounds for messaging.
Billing is governed by the dashboard checkout screen
Plan inclusions and prices are detailed on the pricing page and the in-app payment interface. This terms page does not serve as an invoice: in case of any discrepancy, the amount displayed in your dashboard checkout applies.
What This Overview Does Not Guarantee
This overview does not guarantee specific uptime SLA percentages, isolated dedicated infrastructure, or formal enterprise compliance certifications on this tier. It does not promise that historical messages from legacy systems migrate automatically: see platform migration for details. It does not designate penalty clauses or judicial venue: those require an executed corporate agreement with a named legal entity, which is not established on this page.
Questions & Clarifications
Can this web page be cited in legal proceedings?
As a product description only, strictly in conjunction with what was displayed during login and checkout. Not as a standalone binding contract.
Who owns the customer conversation transcripts?
Conversations take place between your staff and your customers. The dashboard stores history so threads can be maintained. This language does not grant or revoke intellectual property rights: those are governed by your formal customer agreement, not a website paragraph.
What happens in case of a terms violation?
This page does not impose arbitrary legal penalties. Dashboard access may depend on active subscription payments and compliance with terms presented on screen. Do not assume account locks not specified in the dashboard interface.
Is a formal clickwrap checkbox required on this site?
There is no separate checkbox required on this public page. Browsing this marketing page does not constitute binding contract execution.
Where can I find the data policy?
Refer to privacy policy and data deletion. They are also informational overviews rather than entity-specific legal agreements.
Related Pages
- Privacy Policy
Why it matters: Review explicitly what conversation data is handled.
The risk without it: Conflating login credentials with data retention rules. - Data Deletion
Why it matters: Avoid mistaking channel disconnection for data purging.
The risk without it: Requesting conversation deletion via an unmonitored generic address. - Security
Why it matters: Configure team roles before disputes arise over who accessed what.
The risk without it: "Individual user accounts" remains an unenforced policy. - Pricing
Why it matters: Do not look for contractual fees on a legal overview page.
The risk without it: Quoting a website article as a binding rate sheet. - Contact
Why it matters: Understand how official company inquiries are submitted.
The risk without it: Expecting corporate registration details in a website footer. - For Developers
Why it matters: Ensure integration requirements are reviewed by whoever holds API credentials.
The risk without it: Enabling APIs without designated secret token ownership.