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:
Product model and description
Warranty status (active, expired or expiring)
Warranty start and end dates, used to work out expiry timelines and trigger alerts
Warranty entitlement type, for example next business day on-site
Purchase date and service region, where the manufacturer returns them
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:
Device names and hostnames
Device serial numbers, used to look up manufacturer warranty data
Operating system and hardware details, used to build the asset record
Customer or site groupings, used to attribute devices to the right customer
Last-seen dates, used to spot devices that have gone quiet
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:
Customer or site names, used to group devices under the right customer
Device records belonging to those customers, including hostnames, serial numbers and hardware details
Customer groupings, as set up in the MSP's RMM
Contacts the MSP adds (name, email address, phone number) for people at its customers, who may receive alert and digest emails sent on the MSP's behalf. If one of those people opens their personal link and replies, we record the reply.
MSP responsibilities
By connecting its RMM to Orbend, the MSP confirms that it:
Has the right, or the permission of its customers, to share device and asset data with a service like Orbend for lifecycle and warranty management
Has told its customers where the law requires it that their asset data may be handled by service providers the MSP uses
Is responsible for the accuracy of the data it makes available, and for the contacts it asks us to email
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:
Showing warranty status and asset details to the MSP that owns the device records
Working out warranty expiry, end-of-life and refresh timelines
Raising alerts when a warranty or lifecycle date is reached or changes
Sending alert and digest emails to the contacts the MSP chose, and recording their replies on the MSP's Pipeline
Producing the MSP's lifecycle and warranty reports
Keeping the service working: checking that syncs and emails succeed, and keeping a record of activity for the MSP's audit trail
We do not use this data for:
Training machine learning or AI models
Market research, analytics or benchmarking that is sold or shared outside Orbend
Any commercial purpose beyond running Orbend for the MSP that owns the data
Advertising or marketing of any kind
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:
They are encrypted (AES-256) before they are saved, and the encryption key is kept separate from the database and the source code
Once saved, a credential cannot be read back through Orbend. Screens only show that one is set.
They are never sent to the browser, and they are removed from technical error reports
They are decrypted only at the moment the application needs to use them
Personal customer links are stored in a form that cannot be read back as a link, expire after 90 days, and stop working when the person is removed from a digest
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.
Documented APIs only: we use the services' published, authorised APIs. We do not scrape websites, portals or undocumented endpoints.
Limits: we work within each service's rate limits and terms of use. Warranty lookups to a manufacturer are queued and run one at a time, in small batches.
Failures are recorded: when a service is slow, refuses a request or is down, Orbend records the type of problem so we can see when a limit needs raising. It does not store the service's raw error text in the MSP's account.
9. Data Retention and Deletion
Active records: kept and refreshed while the MSP's account is open.
Removing a customer or device: hides it rather than erasing it, so alert history stays intact and the record can be restored. The same happens when a device is removed from the RMM. A device that reappears in the RMM comes back automatically.
Closing an account: when an MSP asks us to close its account, we switch it off and then permanently delete everything in it from the live system: customers, devices, manufacturer data, alerts and history, reports, integrations and the audit trail. We aim to do this within 30 days of the request.
Backups: our hosting provider keeps daily backups that can be restored for up to 7 days. Deleted data drops out of backups when that window passes.
Audit trail: kept for 12 months, then removed automatically.
Technical health records (sync results, email delivery results, traffic counts): kept for 90 days, then removed automatically. They do not hold recipient email addresses.
Customer links: expire after 90 days.
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:
Sold or licensed to other businesses
Shared with data aggregators, brokers or analytics providers
Shown to anyone other than the MSP that owns it, except where the law requires it
Used to build or improve any product, dataset or service outside Orbend
Passed between MSPs
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
DigitalOcean hosts the application and its database, including backups, in Sydney, Australia. This is where customer data is stored.
Cloudflare delivers the application's pages and sits in front of the application's servers. Web traffic, including requests to the application and IP addresses, passes through its global network. It does not store the database.
Kinde handles sign-in. It holds sign-in details, names and email addresses of the people who use Orbend. It does not receive device or customer data.
Resend delivers the emails Orbend sends for MSPs (alerts and customer digests). Those emails contain the recipient's email address and the customer and device details in the message.
Sentry receives technical error reports. We remove request contents and personal link codes before they are sent.
Run this website
Cloudflare also hosts orbend.io and runs the early access form. This does not involve MSP data.
Look up warranties
Dell and Lenovo receive device serial numbers, and nothing else, so they can return warranty details. They are not our service providers; each handles the serial number under its own terms.
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:
Contain the incident and replace any credentials that may be compromised
Tell affected MSPs as soon as we can, and notify the Office of the Australian Information Commissioner where the Notifiable Data Breaches scheme requires it
Tell the manufacturer or platform provider if their credentials or data are involved
Find the root cause and fix it
Give affected parties a written incident report on request
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: