Privacy Policy

MeshRuby operates the platform. For vendor and admin account data (such as email, mobile number, and authentication records), MeshRuby decides how that data is processed to provide the service.

For customer records, device telemetry, images, and similar content that a vendor enrolls or captures, the vendor is responsible for having a lawful basis. MeshRuby processes that content to host, deliver, secure, and display the service the vendor requested. If you are a person photographed or monitored by a vendor’s devices, contact that vendor first about your rights in that content.

Depending on how you use MeshRuby, we may process:

• Account data: email address, mobile number (optional), password (stored in hashed form by the service), and role (vendor or admin).
• Session data: access and refresh tokens kept in your browser so you stay signed in, as described in the Cookie Policy.
• Customer and organization records that vendors enter (names, contact details, and assignments to devices).
• Device data: identifiers, names, settings, units, timers, online status, command history, and related metadata for MR.Optic and MR.Temp.
• Telemetry: temperature readings and timestamps from MR.Temp.
• Images and capture metadata from MR.Optic (file size, time, device). Images may include people, places, or other personal data if a camera is aimed that way.
• Security and abuse-prevention data: Cloudflare Turnstile tokens on sign-in and sign-up, and technical logs reasonably needed to operate and protect the service.
• Preferences: interface language and light or dark theme stored in your browser.

We use this information to:

• Create and authenticate accounts, and keep you signed in.
• Operate dashboards, device fleets, commands, galleries, and notifications.
• Store and show telemetry and images to authorized operators of the relevant vendor account.
• Protect the service against abuse, fraud, and unauthorized access.
• Remember language and appearance preferences.
• Meet legal obligations and enforce the Policy of Use.
• Improve reliability and features of the platform, using aggregated or de-identified data where practical.

Where data-protection law requires a legal basis, we rely on: performance of a contract (providing the account and platform you requested); legitimate interests in running a secure IoT service (balanced against your rights); consent where we ask for it (for example certain non-essential storage, if introduced later); and legal obligation when we must retain or disclose information.

Vendors must not submit personal data they are not entitled to process, including images of people without a lawful basis in the place of capture.

We do not sell personal data. We share information only as needed to run MeshRuby:

• Infrastructure and subprocessors that host, store, transmit, or protect the service (for example connectivity, storage, and messaging).
• Cloudflare, which provides Turnstile bot protection on authentication forms. Cloudflare processes the data needed for that challenge under its own terms.
• People in your organization who you authorize on the same vendor or admin account.
• Authorities when law requires disclosure, or when we must protect MeshRuby, users, or the public from serious harm.
• A successor if MeshRuby is transferred as part of a merger, acquisition, or similar transaction, under equivalent protections.

MeshRuby may process and store information on servers in more than one country. If you access the service from another region, your data may be transferred to where the platform is hosted. We take steps appropriate to the nature of the service to protect information in transit and at rest.

Account data is kept while the account is active and for a further period needed for security, billing disputes where fees apply, and legal claims. You may request closure of an eligible account through the product or your MeshRuby contact.

Device telemetry, images, and customer records remain until the authorized vendor deletes them in the dashboard (where that function exists) or until the account is closed and any required retention period ends. Browser storage lasts as described in the Cookie Policy.

Backups and security logs may persist for a limited time after deletion, then are overwritten or de-identified.

We use access controls, encrypted transport, hashed passwords, and session tokens to protect accounts. Device keys and broker credentials must be kept confidential by operators, as set out in the End User Policy. No method of transmission or storage is perfectly secure. Notify MeshRuby promptly if you suspect a breach of your account or devices.

You can update profile details available in the dashboard, change language and theme, sign out, and clear site data in your browser. Vendors can manage or delete customer and device records they control, including gallery images where the product allows it.

Depending on where you live, you may have rights to access, correct, delete, restrict, or port personal data, to object to certain processing, and to withdraw consent. Account holders should use the vendor portal or the support channel MeshRuby provides to their organization. If we process content only on a vendor’s instructions, we will direct individual requests about that content to the vendor when appropriate.

You may also lodge a complaint with a data-protection authority in your country if that right applies to you.

MeshRuby is a business IoT platform. It is not directed at children, and we do not knowingly collect account data from children. Vendors must not use MR.Optic in a way that exploits minors or captures children’s images unlawfully. If you believe we have account data about a child, contact us through the channels in section 13 so we can delete it.

MeshRuby does not use automated decision-making that produces legal or similarly significant effects about you without human involvement. Turnstile only distinguishes likely humans from automated abuse on authentication forms.

The Cookie Policy lists the browser technologies we use (session storage, theme, language, Turnstile, and the optional web-app cache). That policy is part of how we process information on your device.

We may update this Privacy Policy when our practices or the law change. The date at the top is the latest revision. Material changes will be posted on this page. Continued use after the effective date means you have read the updated policy.

Privacy questions 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.