NeoUEM / Trust center

Trust center

The facts a security or procurement review needs: where NeoUEM runs, who handles data, how it is protected, and what we have not done yet.

Last updated 18 November 2026.

Where NeoUEM runs

NeoUEM is a cloud service operated by Cybzilla Systems Private Limited. The application and the database both run in Singapore. You sign in from a browser and install only the agent on your computers.

Providers that handle data

ProviderWhat it doesWhereData it handles
Google CloudRuns the NeoUEM application and serves this website and the console (Cloud Run)SingaporeAll workspace data in transit and while being processed
NeonManaged PostgreSQL databaseSingapore (AWS region)All stored workspace data
CloudflareDNS and edge protectionGlobal edge networkWeb and API requests in transit
ResendSends service emailProvider’s infrastructureRecipient email address and message content for invitations, verification codes, password resets and alerts

We will update this list when a provider changes. Customers with an agreement are told in the way that agreement sets out.

Data we hold

  • Device data. Hardware, operating system, installed software, health, encryption status, network details such as IP addresses and the Wi-Fi network name, and the accounts logged in to each managed computer. Device location only if you turn it on.
  • Recovery keys. BitLocker and FileVault recovery keys for devices that report them.
  • People. Administrator accounts and, if you use it, your employee directory and who holds which device.
  • Activity. Policies, commands and their results, and the audit log.

Sensitive-data discovery runs on the device and reports only the kind of data found; the files it scans are not uploaded. An administrator using the terminal or remote desktop can see what is on a computer; neither session is recorded. NeoUEM does not inspect browsing or network traffic.

How data is protected

  • In transit. Browser and agent connections use TLS 1.2 or later. After enrollment each device also presents its own certificate.
  • At rest. Recovery keys, authenticator secrets, identity-provider credentials and the certificate authority key are encrypted by the application with AES-256-GCM before they are stored. The hosting providers also encrypt their storage.
  • Between organizations. PostgreSQL row-level security keeps each organization’s rows apart, as a second barrier behind the application.
  • Commands. Every command is signed and verified on the device before it runs.
  • Passwords. Cybzilla staff never set or see a customer password. Owners join through a single-use emailed invitation.
  • Audit. The audit log is hash-chained so changes to it can be detected, and can be archived to write-once storage.

The security page describes each control and its limits.

Export and leaving

  • Export your device list, asset register and compliance report as CSV from the console at any time.
  • Export your configuration as a file.
  • Retiring a device closes its connection and cancels anything queued for it. Uninstalling the agent removes NeoUEM from the computer.
  • To close a workspace, write to support@neouem.online from an owner account. We delete the workspace and its data, except records the law requires us to keep.

Assurance: what exists and what does not

ItemStatus
SOC 2 reportNone today
ISO 27001 certificationNone today
Automated code and dependency scanningRuns on every change before release
Uptime commitmentNone on the free plan; set in the commercial agreement for larger fleets
Public status pageNone yet; report a suspected outage through Support

For a security questionnaire or a call with our engineers, talk to sales.

Report a vulnerability

Email info@cybzilla.com with “Security report” in the subject. Cybzilla’s responsible disclosure policy applies and states the acknowledgment time. Please do not test against other customers’ workspaces or run tests that degrade the service. Contact details are also published at /.well-known/security.txt.

Documents