SMS / DATA HANDLING
Where SMS data is processed.
This statement describes the v2 diagnostic architecture. It is a product data-flow description; your customer agreement and the operator’s applicable privacy notice provide the legal terms and contact details for the deployed service.
| Information | Where it is handled | Purpose |
|---|---|---|
| Sign-in identity, organization membership and role | Ambarix identity provider and control service | Authenticate accounts and enforce organization access. |
| Licence limits, expiry, status and enrolled device identity | Ambarix control database | Allocate purchased endpoint capacity and authorize permitted sessions. |
| Device public keys, certificate fingerprints and opaque device IDs | Ambarix control database and customer devices | Bind enrollment and direct sessions to the intended endpoint. |
| Access, enrollment and licence events | Ambarix control database | Security and account administration. Default application audit retention: 90 days; deployment policy may configure it. |
| Endpoint route, diagnostic destination, adapter details and command parameters | Technician laptop and target endpoint only | Perform the requested diagnostic across the customer’s network route. |
| Diagnostic response reports and packet captures | Technician laptop; temporary generation files on the endpoint | Store investigation evidence under the customer’s control. |
Direct diagnostic transport
Commands, responses and capture bytes travel over a direct TLS connection between the technician companion and the enrolled endpoint. The Ambarix service has no diagnostic relay, capture-upload API or diagnostic-file store. The endpoint verifies a short-lived authorization and proof of possession of the technician session key.
Local workspace and files
The diagnostic interface is served by the companion on the technician laptop. Its scripts and styles are bundled locally. It does not load analytics, external fonts, remote error reporting or other remote page assets. Capture downloads are written as partial files and committed after size, format-marker and SHA-256 verification. Final reports remain in the selected folder until the customer deletes them.
Customer-selected backup, synchronization, antivirus, screen sharing and endpoint management tools may process those local files independently. Select an output folder consistent with your organization’s policy. Interrupted endpoint captures can leave temporary artifacts; the client attempts cleanup on restart and reports cleanup problems locally.
Account and transport metadata
Not storing diagnostic files does not mean the service processes no customer information. Authentication, licensing, rate limiting, network transport and operational security may process identifiers and source-address metadata. Infrastructure and identity-provider logs have their own retention settings. These settings and the customer agreement must be reviewed for the actual deployment.
Customer administration
Organization owners approve account membership. Licence administrators enroll or deactivate endpoints. Removing access or suspending a licence prevents new authorizations; an authorization already issued can remain valid for up to five minutes, and a bounded diagnostic already started may finish.
Contact
Use your contracted Ambarix support contact or the Ambarix contact page for account, licence and data-handling questions. Please do not attach confidential diagnostic files to an account request unless a separate, authorized support process requires them.