GoMyid Trust Center

Transparency and audit principles for remote desktop operations

This policy explains how GoMyid approaches operational visibility, customer review, responsible use of records, security communication, and requests for relevant assurance information.

Request trust information Review security

Effective date: August 15, 2026. This policy applies to GoMyid software and services supplied by DeskGate LLC. Available records and reporting detail vary by deployment, configuration, licensing, enabled features, and product version.

Relevant visibility

Provide authorized teams with operational context that can support service management, investigation, and review.

Protected evidence

Limit access to logs and reports because operational evidence can itself contain sensitive information.

Proportionate retention

Retain records for a documented operational, contractual, security, or legal purpose and no longer than justified.

Clear communication

Route material product, security, privacy, and contractual questions to the responsible team.

Operational records

Understand what a record can and cannot prove

Depending on the deployment and enabled capability, GoMyid interfaces may present information related to users, devices, groups, connection activity, administrative operations, support workflows, alerts, and reports. Customers should validate the exact fields and timestamps available in their own version before relying on them for an audit procedure.

A record provides context; it does not automatically establish intent, authorization, legal compliance, or the complete sequence of an event. Reviews should combine available GoMyid information with endpoint, server, identity, network, ticketing, and organizational evidence where appropriate.

System clocks, retention settings, account design, shared credentials, unavailable endpoints, and configuration changes can affect interpretation. Findings should be reviewed by qualified personnel and documented with limitations.

GoMyid work analysis interface with sensitive information concealed

Customer audit governance

Define the review before opening the report

Authorization and scope

Identify who may request, view, export, interpret, and approve audit information. Define the systems, users, time period, purpose, and legal authority for each review. Avoid broad searches without a documented need.

Evidence handling

Protect reports and exported evidence against unauthorized access or alteration. Record provenance, collection time, responsible personnel, storage location, transfer, and disposal when the investigation requires a formal chain of custody.

Retention and deletion

Set retention by record category and purpose. Consider active disputes, legal holds, incident requirements, employment rules, contractual duties, and individual rights. Securely delete information when retention is no longer justified.

Independent review

Separate the person under review from the person approving conclusions where practical. Escalate legal, privacy, employment, or security questions to qualified specialists before taking consequential action.

Provider transparency

How DeskGate communicates

DeskGate uses product documentation, contractual material, support channels, trust and policy pages, and direct customer communication as appropriate to the subject and relationship.

Product and deployment information

We explain supported deployment choices, relevant responsibilities, feature scope, and operating considerations through product and technical materials.

Security communication

Material security matters are assessed and communicated through appropriate support, contractual, operational, or direct notification channels based on the circumstances.

Confidential assurance material

Some architecture, security, contractual, or customer-specific information may require identity verification, an appropriate agreement, and restricted disclosure.

Responsible monitoring

Remote access records must not be interpreted as unrestricted permission to monitor people. Customers should establish necessity, proportionality, transparency, a lawful basis, and appropriate authorization before reviewing user-related activity. Employment, communications, privacy, surveillance, and data protection laws can differ by location.

Where appropriate, organizations should inform affected individuals about the categories of monitoring, purposes, recipients, retention, rights, and contact route. Covert or continuous monitoring requires particularly careful legal and ethical review.

Audit requests to DeskGate

Customers seeking contractual, privacy, security, or assurance information should submit a request through the GoMyid contact channel. Include the customer organization, contract or account context, requested subject, business purpose, deadline, and authorized contact.

DeskGate may verify identity and authority, clarify scope, protect information belonging to other customers or third parties, require confidentiality controls, and provide an appropriate response format. A request does not guarantee disclosure of source code, penetration details, credentials, internal security procedures, or information that could weaken system security.

Review workflow

A repeatable path from question to conclusion

Authorize

Document purpose, scope, legal basis, reviewer, and approval.

Collect

Gather relevant records while preserving context and access controls.

Correlate

Compare GoMyid records with other reliable operational evidence.

Conclude

Record findings, limitations, decisions, follow-up, and disposal.

Need GoMyid trust or audit information?

Send a scoped request and we will route it to the appropriate security, privacy, legal, or technical contact.

Submit a trust request