A setup inquiry is not an order.

Moxby is the product name used on this destination. These website terms concern your use of the information, inquiry facilities and support conversation offered here by the operator. The difference between Moxby and moxbey.com is intentional; it does not identify a separate reseller or an unrelated product provider.

The operator's full postal address is 26 Mill Street, Werkstatt 2, Austin, Texas 12918, Austin, Texas, United States. Questions can be sent to office@moxbey.com or raised by phone at +1 (656) 555-6275. The contact information identifies the operator; it does not promise walk-in access or opening hours.

If you inquire on behalf of a team or another organisation, describe your role accurately. Sending a message does not establish that you have authority to license software, permit access to a website or commit that organisation to commercial conditions. Any authority needed for a later agreement must be confirmed separately.

Moxby concerns a shared work environment for chat, tasks and documents, with a separate browser-side assistant for local scenarios and bounded actions on websites. The pages give those areas room to be discussed. They do not establish a release date, a supported-browser list or a promise that every described example is an available feature.

Illustrative workflow photographs and walkthroughs explain relationships between work items and actions. They are not customer evidence, verified product screenshots or performance demonstrations. A proposed review point on a website form is an example of a boundary to discuss, not a representation that the site can be controlled automatically.

The setup builder assembles a request from named areas. Its dependencies explain the request: choosing local workflows or website actions also includes the browser assistant. The resulting count is a count of selected areas. It is not a licence quantity, compatibility score, delivery estimate or price calculation.

There is no cart, checkout or payment facility. An inquiry asks the operator to discuss a requested setup. Selecting an area, sending a message or receiving a submission reference does not place an order and does not reserve availability. Do not send payment-card data or account credentials through the form or chat.

A request becomes an order only through a separate express agreement that identifies the parties and the scope, with the applicable commercial conditions accepted by both sides. An automated receipt only confirms that the request was stored. An informal acknowledgment, a scoping question or a support reply is not acceptance of a commercial order by itself.

The site publishes no numeric price. Any indicative figure discussed during an initial inquiry is an estimate, not a binding quote, unless expressly offered as a firm proposal on stated terms. Do not read a configurator selection as a commitment to supply those selected areas as a ready-made bundle.

Use accurate contact details and provide at least one way to reply. The inquiry form requires a name and consent to process the request; phone and email are each optional, but at least one is needed. A delivery error is not evidence that the operator accepted the work. Avoid repeatedly sending the same request while a connection failure leaves the result uncertain.

The inquiry basis is individual scope, not a published rate or an online subscription tier. For a workspace request, the relevant scope starts with the shared routine and context to connect. A browser-assistant request also depends on the requested environment and behaviour. Local workflows and website actions require review of the particular workflow or target, including permissions and feasibility.

A change to the requested work can change a proposal. Adding another website, changing an action from review-only to submission, or introducing an external service is not automatically covered by an earlier discussion. The impact on commercial conditions must be agreed before that change becomes part of the supplied scope.

No minimum term, billing period or discount is published here. Payment timing and any cancellation or refund conditions belong in an actual agreement, as do any tax treatment or third-party charges that apply. Submitting an inquiry creates no non-refundable fee and gives no permission to invoice.

You remain responsible for deciding whether a proposal matches the work you need. Ask for an unclear assumption to be written down, especially when a workflow crosses from a local document into a third-party website. Silence about a dependency is not a promise that its cost or access is included.

Do not use inquiry forms or support chat to send malicious code, spam or threats. Do not impersonate another person, submit information you have no right to share, try to bypass access controls or interfere with the website's operation. A public contact route is not permission to test private systems or probe another person's conversation.

For a browser workflow, your ability to view a page does not establish permission to automate it. The website owner's rules and applicable law still apply. Confirm your own authority to use the account and perform the intended action. A requested assistant does not bypass authentication, remove site restrictions or supply rights you do not already hold.

Do not submit passwords, authentication tokens, private account links or copies of confidential records as an example. A useful inquiry names the action and explains the boundary without exposing the underlying account. Where another person's data is involved, use a non-identifying description and discuss the lawful handling before any real information is shared.

An ambiguous result needs a stop, not another blind attempt. If the requested workflow involves a potentially irreversible change, the review point and stopping condition must be explicit. An illustrative example here does not authorise repeated submissions, purchases, deletion or communication to a third party without a confirmed scope and permission.

Website text, photographs, design and marks are owned by the operator or used subject to the rights of their owners. You may view the site and keep reasonable extracts to evaluate a Moxby inquiry. This does not give you a licence to republish the site, sell its material or use its marks in a way that suggests an association or endorsement.

Photographs marked as illustrative workflows explain a working context. They are not an open asset library and must not be reused as evidence of your own product or customer results. References to third-party names identify those parties; their marks remain subject to the relevant owner's rights.

You retain the rights you hold in the material you submit. By sending an inquiry, you permit the operator to use that material to assess and handle the request, subject to the privacy notice. Do not submit material if you cannot give that limited permission. Sending a message does not assign ownership of your work or grant a broad right to publish it.

Any licence to use software, or allocation of rights in work supplied under an agreement, must be stated in that agreement. An example on this marketing website is not source-code access, a software licence or an assignment of intellectual property.

The website and its explanatory material are provided as is and as available, to the extent permitted by law. They help frame a discussion; they are not a commitment that a specific workflow will run on every device, browser or website. An illustration of a review state is not a claim that an action has been implemented or tested in your environment.

No result or productivity saving is guaranteed. No uptime percentage is promised. No universal browser or website compatibility is stated. Local operation must not be read as an assurance of offline use, absence of telemetry or protection from every security risk. Those are distinct technical questions, not consequences of choosing a product-area name.

Any express warranty belongs in the actual agreement for the supplied scope. A promise about a supported environment, a delivery obligation or a remedy must be identified there. General website language does not enlarge that agreement, and these website disclaimers do not remove an express obligation the operator actually accepts.

Third-party websites and services can interrupt or change a workflow independently. A page can move a field, expire a session or return an unclear state. Before relying on an action, its permissions and review boundary need confirmation. Keep the source material needed to check an output rather than treating an illustrative process as an assurance that no review is required.

The support widget is a contact facility, not a promise of a live agent or an emergency-response service. A stored conversation does not establish when an answer will arrive or whether a requested action will be accepted. For the records and choices associated with chat, consult the privacy notice.

To the extent permitted by applicable law, the operator is not liable for indirect or consequential loss arising solely from use of this informational website, including lost business opportunities or anticipated savings based on a workflow example. The site is not a substitute for confirming an actual product scope before relying on it for work.

The operator does not accept responsibility for the content or independent conduct of third-party websites merely because they are linked or discussed here. That limit does not remove responsibility for the operator's own duties under applicable law. A browser task can depend on systems outside the operator's control, and the website does not turn those dependencies into guaranteed services.

Nothing excludes liability that cannot lawfully be excluded, or limits a mandatory consumer remedy. These website terms set no monetary liability cap. Any enforceable commercial allocation of risk for a supplied product belongs in its actual agreement, subject to those same legal limits.

If you believe a website error has affected you, contact the operator with the public page address and an explanation. Keep private information out of the initial report. Describing the problem helps distinguish a missing page or a failed submission from a dispute over an agreed service.

The operator may refuse abusive inquiries, restrict automated misuse or suspend access to a website facility when reasonably necessary to protect the service or comply with law. Repeated unsolicited messages and attempts to access another visitor's support session are not permitted uses of the contact route.

A restriction on a public website facility does not automatically terminate a separate product agreement. That agreement governs its own suspension or termination conditions, subject to applicable law. Nor does a website restriction remove your ability to raise a privacy request or a legal complaint through the operator's email or postal address.

The website can also be unavailable during a technical fault or maintenance. Do not assume that a failed page load means an inquiry has been refused or an agreed service cancelled. If the status of a message is uncertain, contact the operator rather than trying to force repeated submissions.

This governing-law and court provision applies subject to any mandatory law that protects you and cannot be displaced by agreement. It does not require a visitor to give up a non-excludable consumer right, a statutory complaint route or a privacy right that applies to the processing of their data.

No mandatory arbitration procedure is imposed by this page. If a later product agreement contains terms addressing disputes about that agreed service, read them as part of that agreement, with the same reservation for rights that cannot lawfully be waived.

The operator can be contacted before a dispute is brought so an unclear scope or disputed record can be examined. That contact route is not a condition on exercising a right where the law does not permit such a condition. Privacy complaints are addressed separately in the privacy notice.

The effective and last-updated line at the top identifies the current website terms. Revisions can clarify how an inquiry is handled or reflect a change to a website facility. Read the current terms when using the site rather than relying on a saved extract without its date.

A later website revision does not silently change the scope or express warranty of an agreement already made. Changes to an agreed service need the process required by that agreement and applicable law. These terms also do not turn a previous inquiry into an order because wording has changed.

Privacy and storage changes have their own notices. The cookie statement explains how an allowance is changed or withdrawn, and the privacy revision section explains changes to data-use information. Accepting website terms is not an allowance for optional advertising storage.

Email office@moxbey.com or call +1 (656) 555-6275. For post, use 26 Mill Street, Werkstatt 2, Austin, Texas 12918, Austin, Texas, United States. Identify the section you are asking about and distinguish a website question from a proposed change to a product scope.

If your question concerns an existing discussion, refer to that correspondence without sending credentials or payment details. Ask for confirmation of a material condition before relying on it. A request for clarification is not acceptance of a new fee or a wider action permission.

Use data requests for access to or deletion of information, and accessibility and getting help if a control prevents you from using the contact route. For a new product discussion, the inquiry page accepts the requested scope without taking payment.