Plain-language summary: Your data is only ever used to run Orbend for you. Orbend reads device and customer records from your RMM and never changes anything there. It sends device serial numbers to the manufacturer (Dell or Lenovo today) to look up warranty details. It does not sell or share your data, and each MSP's data is kept separate from every other MSP's. Data is stored on servers in Australia and is encrypted in transit and at rest. A small number of service providers help us run Orbend, and they are listed in section 11.

1. About This Policy

This Data Use Policy ("Policy") describes how Orbend ("we", "us", "our") accesses, stores and uses data that comes from the systems an MSP connects to Orbend: its RMM and the manufacturers' warranty services.

Today, Orbend connects to one RMM, Atera, and looks up warranty details with two manufacturers, Dell and Lenovo. Other RMMs and manufacturers are on our roadmap but are not live. We do not retrieve any data from them, and we will update this Policy before any of them is connected.

This Policy is written for MSPs, and for manufacturers, API providers and RMM vendors who want a clear account of what we do with their APIs. Read it alongside our Privacy Policy, which covers personal information about our users and website visitors.

2. Data We Retrieve

When an MSP connects Orbend to its RMM and turns on a manufacturer, we retrieve a limited set of data to give warranty and asset lifecycle management.

From manufacturers (Dell and Lenovo today)

Orbend sends a device's serial number to the manufacturer's warranty service as the lookup key. This is the only information we send. We receive back:

We do not retrieve pricing, reseller information or end-customer account data.

From the RMM (Atera today)

Orbend reads from the MSP's RMM using the credentials the MSP provides. We retrieve:

Orbend only reads from the RMM. It never changes anything there. We do not ask for passwords, patch data, script history or remote session logs.

From public sources

Orbend also pulls operating system end-of-life dates daily from a public catalogue (endoflife.date). No customer data is sent to it.

3. Data From MSP-Connected Platforms

When an MSP connects its RMM to Orbend, Orbend handles that data on the MSP's behalf. The MSP decides what to connect and stays responsible for its own customers' data.

What this can include

The data an MSP brings into Orbend is mostly about the MSP's customers, not the MSP itself. It can include:

MSP responsibilities

By connecting its RMM to Orbend, the MSP confirms that it:

Orbend does not check the arrangements between an MSP and its customers. The MSP is responsible for making sure its sharing with Orbend is lawful.

Customer data stays with the MSP

An MSP's customers do not have access to the Orbend platform beyond their own personal links. Their data is never visible to or shared with any other MSP or Orbend customer. When an MSP's account is closed, its data is deleted as described in section 9.

4. Purpose and Use Limitations

Data retrieved from the RMM and the manufacturers is used only for these purposes:

We do not use this data for:

5. Data Storage and Security

Hosting
Data stored on servers in Australia
Encryption in Transit
TLS 1.2 or higher
Encryption at Rest
AES-256, including RMM and API credentials
Audit Trail
12 months of sign-ins, Pipeline moves and customer emails, searchable by admins and exportable as CSV

Access to production systems is limited to authorised staff and requires multi-factor authentication. Inside Orbend, users have roles (admin or user), and some areas, such as integrations and the audit trail, are for admins only.

Web traffic to the Orbend application passes through Cloudflare's network on its way to our servers. The database and its backups stay in Australia.

6. Separation Between MSPs

Orbend serves many MSPs, and keeping their data apart is a core design requirement. Every record belongs to one MSP, and every request the application makes to the database is limited to the signed-in MSP's records. Automated tests check that this rule is followed throughout the code.

Data from one MSP is never visible to, combined with or shared with another MSP.

A small number of authorised Orbend staff can see an MSP's account through a restricted operator console, for support and to run the platform. Credentials are shown there only as "set" or "not set", never their values. Their actions inside an MSP's account appear in that MSP's audit trail as "Orbend support".

7. Credential Management

API keys, tokens and other credentials for the RMM and the manufacturers are treated as secrets:

Manufacturer lookups use API credentials, either Orbend's own or ones the MSP provides. Either way they are protected as described above.

8. How We Query Other Systems

Orbend queries the RMM and the manufacturers automatically on a schedule, not every time someone opens a page. The MSP sets how often its RMM is read. Warranty lookups run on Orbend's schedule.

9. Data Retention and Deletion

After an account is deleted, we keep a short internal record that it happened (company name, who asked, when, and counts of customers, devices and people). It holds no device or customer data.

An MSP can ask for earlier deletion of any of its data at any time by contacting us at the address in section 15.

10. No Resale or Onward Transfer

Orbend does not sell, license or broker data retrieved from the RMM, the manufacturers or an MSP's systems, including its customers' device records and contacts. This data is not:

The only parties that receive any of it are the service providers and manufacturers listed in section 11, and only as that section describes.

If Orbend is acquired by or merged with another business, the buyer will be required to honour this Policy, or customers will be told and given the chance to delete their data before it is transferred.

11. Service Providers and Third Parties

We use a small number of providers to run Orbend. They may handle data as part of their service, and we use them only to run Orbend for you. Here is who they are and what each one does:

Run the application

Run this website

Look up warranties

Some of these providers may handle data outside Australia, in particular Cloudflare, Kinde, Resend and Sentry, and the manufacturers. The database and backups stay in Australia. We update this list when it changes. For more detail, contact hello@orbend.io.

12. Security Incident Response

If we confirm or suspect a security incident that affects data covered by this Policy, we will:

To report a security concern, email hello@orbend.io with the subject "Security Incident".

13. Compliance and Governing Law

This Policy is governed by the laws of the State of New South Wales, Australia. Orbend handles personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).

Data is stored in Australia. Some data leaves Australia only in the ways described in section 11: through providers whose networks or servers may be overseas, and in the lookups sent to manufacturers.

14. Changes to This Policy

We may update this Policy to reflect changes in what we do, the systems Orbend connects to, or the law. When we make significant changes, we will update the date at the top and email active customers.

Manufacturer and platform partners who want to hear about changes can ask us at the address below.

15. Contact

For questions about this Policy, API partnership enquiries or data handling concerns:

Orbend

Subject Data Use Policy: [Your Organisation Name]
Business Being registered (Pty Ltd). Until then, run by founder Dick Rijnsburger
Response We aim to respond to policy enquiries within 2 business days