Privacy at Infser
Infser is designed to keep the control plane focused on identity, authorization, device state and security metadata rather than becoming a store for machine content.
Account, authentication and workspace information is processed so Infser can identify users, enforce access and operate the service.
Device identity, capability, lifecycle and presence metadata may be used to decide whether an action is allowed and where it can run.
The product is designed so sensitive terminal and machine content is not treated as ordinary application data. Security and audit metadata may still be recorded to make actions traceable.
Access is tied to workspace membership, scopes, permissions and device state so authorization can be revoked when the underlying relationship changes.