Who we are
This policy explains how the Rubus Hub Android app handles information. Rubus Hub is provided by RubusNode Technologies (Private) Limited ("RubusNode", "we", "us").
Rubus Hub is a companion app for Android devices that an organization, such as your employer, manages with RubusNode through Android Device Policy. The organization decides to manage the device and decides how it is managed. RubusNode processes the information described here on behalf of that organization, under its agreement with us.
Devices the app works on
Rubus Hub works only on devices enrolled by an organization through Android Device Policy. Your organization installs it and delivers its configuration automatically.
On a device that is not managed by an organization, Rubus Hub shows a message saying so. It does not create an account, collect information or send anything to RubusNode.
Information the app sends
On a managed device, Rubus Hub sends the following to the RubusNode service used by your organization:
- Identifiers: a device ID assigned by RubusNode, and a Firebase Cloud Messaging registration token used to deliver wake-up messages. The app does not read your IMEI, serial number, phone number or Android ID.
- Capability report: Android version, API level, Rubus Hub version, and the type of secure key storage on the device.
- Results of administrative tasks your organization requests, such as installing organization apps or files. These include the package names and versions of organization-managed apps, and the names and locations of files the organization delivers.
- Diagnostic summaries, only when an administrator requests them: Android version, device manufacturer and model, time since restart, processor count and the app’s memory use. Rubus Hub does not collect system logs, logcat output or bug reports.
- Kiosk events, on dedicated kiosk devices only: failed and locked-out exit-PIN attempts and changes in kiosk lock state, with the organization’s list of permitted apps.
During setup, the app exchanges a single-use setup code from your organization for device credentials. It keeps these credentials in app-private storage protected by the Android Keystore. The app also keeps a local copy of the status and command history it displays.
Some information shown in Rubus Hub, such as compliance status and the organization’s restrictions, comes from your organization’s RubusNode service rather than being collected by the app.
What the app does not do
Rubus Hub does not collect your location, contacts, messages, photos, files, browsing history, or name or email address. It does not record or share your screen, does not let anyone control your device remotely, and does not use your camera or microphone. It does not request phone, storage, location, accessibility or usage-access permissions.
Rubus Hub contains no advertising and no analytics, and RubusNode does not sell information.
Android Device Policy, a separate app from Google, applies your organization’s management policies and reports device information to your organization. That processing is covered by your organization’s policies and Google’s terms, not by this policy.
How the information is used
We use this information only to provide the service to your organization. That means enrolling and authenticating the app, showing management status on the device, delivering and confirming tasks your organization authorizes, providing diagnostics on request, and protecting the service, for example by detecting tampered or replayed messages.
Who receives it
- Your organization: its authorized administrators can see device status, task results and diagnostics in the RubusNode console.
- Service providers that host and operate the RubusNode service for us, under confidentiality and security obligations.
- Google Firebase Cloud Messaging, which delivers wake-up messages to the app. Wake-up messages contain no commands or device information; the app then fetches its tasks directly over an authenticated connection.
- Authorities, where we are required to disclose information by law.
Security
All network traffic uses HTTPS. Release builds refuse unencrypted connections. Credentials are protected by the Android Keystore; hardware-backed protection depends on the device. Messages that report results or device state are signed with a per-device key, so the service can reject altered or replayed messages. No system is perfectly secure, but we work to protect the information we process.
How long information is kept
Your organization controls how long information is kept. RubusNode keeps device information while the device is enrolled and the organization’s RubusNode account is active. We delete it when the organization asks us to or after its account ends, as set out in our agreement with the organization, unless the law requires us to keep it longer.
When your organization retires the device or removes Rubus Hub, the app’s data on the device is deleted with the app.
Your choices and requests
Because your organization manages the device, contact your IT administrator first about access to, correction of or deletion of your information, or about how the device is managed. You can also contact us at support@rubusnode.com. We will help, or pass your request to your organization, which decides on requests about its managed devices.
Children
Rubus Hub is a workplace app. It is not directed at children.
Changes to this policy
If we change how Rubus Hub handles information, we will update this page and its effective date before the change takes effect.
Contact
RubusNode Technologies (Private) Limited. For privacy questions or requests, email support@rubusnode.com.