Technical information

Data Handling Practices

Technical context can make support faster, but it should be collected intentionally. This page explains the types of system information ObserX may use during requested work.

Draft updated July 17, 2026

Technical information may include

  • Network diagrams and connection paths
  • IP addresses and network ranges
  • Device names, model numbers, serial numbers, and MAC addresses
  • Camera, recorder, and remote-viewing details
  • Photographs and screenshots
  • Configuration notes, logs, and observed error messages
  • Vendor, service, and account ownership notes

How it is used

Technical information is used to understand the requested environment, diagnose symptoms, coordinate approved work, document major findings, and avoid repeating discovery during future support. ObserX should collect only the information reasonably useful to the approved service.

Credentials

Passwords, recovery codes, private keys, and security tokens should not be submitted through normal website forms, email descriptions, topology fields, or uploaded screenshots. When credentials are necessary, they should be exchanged only through an approved secure method identified for that service and limited to the access required.

Customer choices

Tell ObserX when a device, image, note, or configuration contains information that should not be copied into the service record. You may redact unrelated information before sharing it. Withholding required access or context may limit what can be diagnosed.

Third-party coordination

When a request requires coordination with a provider or manufacturer, only the relevant technical context should be shared, and the customer should authorize that coordination. Third parties apply their own data and account practices.

Corrections and questions

To correct technical details you submitted or ask that they be removed from the active service record when appropriate, contact hello@obserx.com. Do not include credentials in the request.

A clear next step

Need help with a business technology issue?

Tell ObserX what is happening and start with a clear diagnostic scope.