Policy of Use

MeshRuby provides infrastructure to bring physical objects online: a control plane, vendor accounts, customer and device management, telemetry, image capture, and command delivery across an expandable mesh.

MR.Optic is a camera endpoint for remote capture, secure image upload, and fleet visibility. MR.Temp is a temperature telemetry endpoint for authenticated measurements and presence on the network. Features may change as MeshRuby evolves.

You must be able to form a binding contract and must provide accurate registration details. Vendor accounts are for organizations and their authorized operators. Admin consoles are restricted to people MeshRuby designates.

You are responsible for credentials, device keys, and activity under your account. Notify MeshRuby promptly if you suspect unauthorized access. We may refuse, suspend, or reclaim accounts that violate this policy or that we reasonably believe are compromised.

You may use MeshRuby only for lawful purposes and in line with this policy. You must not:

• Probe, scan, or attack MeshRuby, other customers, or connected devices without authorization.
• Circumvent authentication, rate limits, encryption, or access controls, including device keys and message-broker credentials.
• Upload malware, interfere with the mesh, or overload APIs, brokers, or storage.
• Use MR.Optic to capture images unlawfully, without required notices or consent, or in a way that exploits minors.
• Misrepresent measurements, device identity, or account ownership.
• Resell, scrape, or harvest the platform except as a written MeshRuby agreement allows.
• Use the services for life-safety, medical diagnosis, fire protection, or other safety-critical control unless a separate written contract says otherwise.

Vendors decide which customers and devices they enroll and what they capture. You must have a lawful basis to collect, store, and process personal data, images, locations, and telemetry that pass through MeshRuby.

You must not submit data you are not entitled to process. MeshRuby processes that data to operate the platform (hosting, delivery, security, support, and improvement of the services). Retention follows operational need, legal duty, and your deletion of records in the dashboard where that function exists.

Images, customer records, and device metadata remain your responsibility as between you and the people those records concern. MeshRuby does not police every upload in real time and may remove or restrict content that appears unlawful or harmful.

You are responsible for installing, powering, placing, and maintaining hardware, and for the environments you monitor. MeshRuby does not guarantee coverage, battery life, radio conditions, or that a device will capture every event.

MR.Temp readings are operational telemetry, not certified laboratory or medical measurements, unless MeshRuby states otherwise in writing. Do not rely on MeshRuby alone where failure could cause injury, death, or severe property damage.

Commands sent to devices can change behavior in the field. Only authorized operators should issue captures, reads, settings, key resets, or other commands.

Protect access tokens, refresh tokens, device keys, and broker topics. Rotate credentials when staff leave or a device is lost. Do not embed secrets in public repositories or untrusted firmware images.

MeshRuby applies technical and organizational measures appropriate to a connected-device platform, but no system is perfectly secure. You must also secure your own networks, browsers, and operator devices.

MeshRuby, MR.Optic, MR.Temp, the site design, software, documentation, and marks are owned by MeshRuby or its licensors. Except for the limited license in the End User Policy, no rights are granted.

Feedback you send may be used to improve the services without obligation to you. Your customer names, images, and telemetry stay yours, subject to the license needed to host and display them in the product.

Authentication forms may use Cloudflare Turnstile to reduce automated abuse. Connectivity, hosting, messaging, and similar providers may process data as subprocessors. Their terms apply to their components. MeshRuby is not responsible for third-party sites linked from the service.

Services are provided as available. Maintenance, outages, radio conditions, or force majeure may interrupt access. Unless a separate paid agreement states a service level, MeshRuby does not promise uninterrupted or error-free operation.

We may modify features, APIs, or this policy. Material changes will be posted on this page with an updated date. Continued use after the effective date is acceptance of the revised policy.

To the fullest extent permitted by law, MeshRuby provides the services “as is” and “as available,” without warranties of merchantability, fitness for a particular purpose, title, quiet enjoyment, or non-infringement, and without any warranty that telemetry or images are complete, accurate, or timely.

To the fullest extent permitted by law, MeshRuby and its directors, employees, and suppliers are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, data, goodwill, or business interruption, even if advised of the possibility.

MeshRuby’s total liability for claims relating to the services is limited to the greater of (a) the amounts you paid MeshRuby for the services in the twelve months before the claim, or (b) fifty US dollars (or equivalent), except where liability cannot be limited (for example fraud or liability that the law does not allow to be excluded).

You will defend and indemnify MeshRuby against claims, damages, and reasonable costs arising from your content, your devices, your customers, your violation of law or this policy, or your infringement of another person’s rights, except to the extent caused by MeshRuby’s willful misconduct.

You may stop using the services and close an eligible account through the product or by requesting closure through your MeshRuby contact. MeshRuby may suspend or terminate access immediately for breach, legal risk, non-payment where fees apply, or to protect the platform and other users.

On termination, licenses end and we may delete or de-identify data after any required retention period. Provisions that should survive (including intellectual property, disclaimers, liability limits, and indemnity) remain in effect.

These terms are governed by the laws applicable to MeshRuby’s place of establishment, without regard to conflict-of-law rules, except where mandatory consumer or local law says otherwise. Courts with jurisdiction over that place may hear disputes, unless a written MeshRuby agreement specifies arbitration or another forum.

Questions about this Policy of Use can be raised through the vendor portal for account holders, or through the support channel MeshRuby provides to your organization. Keep a copy of this policy for your records.