DeskGate is designed with security-first principles, ensuring customer-controlled data, isolated system architecture, and clear responsibility boundaries.
Self-Hosted / On-Premise Local data processing No centralized storage No DeskGate system access
Role-based permissions Customer-managed identities Credential responsibility Trusted-user access only
Customer configuration Legal compliance Monitoring lawfulness Security enforcement
DeskGate operates entirely within customer-controlled environments. All connections, recordings, logs, and monitoring data remain local and are never transmitted to DeskGate servers.
Customers define their own security architecture, including network segmentation, firewall rules, and access policies.
DeskGate provides role-based access mechanisms. Customers are responsible for permission assignment, credential protection, and identity governance.
DeskGate operates within secure internal or customer-defined external networks. Encryption, firewall configuration, and perimeter security are customer responsibilities.
DeskGate does not bypass security controls and does not initiate unsolicited inbound connections.
Monitoring features must be used in accordance with applicable labor, employment, and data protection laws.
Customers are responsible for system hardening, patch management, backups, and incident response planning.
DeskGate shall not be liable for incidents caused by misconfiguration, weak credentials, or outdated systems.
DeskGate provides updates for stability and security. Customers decide when and how updates are applied according to internal change management policies.
DeskGate does not monitor customer systems and cannot detect internal security incidents. Incident management remains the customer’s responsibility.
Security effectiveness depends on proper configuration, responsible use, and compliance with applicable laws. DeskGate is provided on an AS IS basis without guarantees of absolute protection.