About this notice
This notice supplements the 4rho Privacy Policy for the restricted native 4rho Desk operator apps. 4rho LTD operates the service and is the controller identified in that policy. The policy's contact details and information about your privacy rights also apply to Desk. The details below describe Desk's native sign-in, device credentials, and operational snapshots.
Google sign-in and device sessions
When an authorized operator signs into Desk with Google, we process the Google account identifier and verified email address to check access. Google provides the browser sign-in page; its handling of information is described in the Google Privacy Policy.
We associate the Desk session with a randomly assigned device identifier and an identifier derived from the app's public device key. We process session identifiers, credential hashes, authentication timestamps, and request-proof metadata to authenticate requests, rotate credentials, detect replay, and revoke access. The device identifier is assigned for authentication; it is not a hardware serial number or advertising identifier. The private device key stays on the device.
Information shown in the app
The native Desk app displays the signed-in operator identity and a limited, read-only snapshot of operational status. This includes engine and guardian status, aggregate published quote counts and notional, and observation times.
The last snapshot stays in app memory while observation is paused or a connection is temporarily unavailable. The app displays its observation time so you can distinguish that retained snapshot from a fresh read.
Storage and retention
The Desk service keeps native sign-in and session records in process memory, without persisting them to an application database or session file. Short-lived login records and credential hashes support authentication and replay detection. Session authority ends at expiry, revocation, or server restart. Expired records are cleaned up when the service next processes the relevant session state; expiration is not a promise of deletion at an exact time. The exchange account and financial record retention periods in the general Privacy Policy do not describe these transient Desk session records.
The native Desk apps keep refresh credentials and device-key material in device-only secure storage. Access credentials and operational snapshots are held in memory. Successful logout or session cleanup removes the stored credentials. If cleanup fails, the app reports that failure and blocks authenticated use in the current app session until cleanup succeeds.
The snapshot is cleared on logout, a new sign-in, observed session loss, or app termination. Server revocation is detected on the next authenticated request. These session and snapshot rules describe the native Desk application; infrastructure logs remain separate from its in-memory session store.
Privacy requests
Contact compliance@4rho.com about Desk privacy, access to your information, or a deletion request. The general Privacy Policy describes the rights available to you and how requests are handled.