DeskTrust Connect for compliance-sensitive organizations

Compliance-sensitive organizations — healthcare, financial services, defense contractors, any team under GDPR, HIPAA, PCI-DSS, or a specific labor-monitoring statute — have the highest alignment with DeskTrust Connect\'s design principles.

Here\'s why.

Silent monitoring is a legal risk multiplier

Every session where a manager silently views an employee\'s screen is a potential compliance issue. In two-party consent US states (California, Illinois, Pennsylvania, and 9 others), it can be a criminal issue. Under GDPR, it can be a fine multiplier. Under a labor-relations board complaint, it\'s evidence.

The traditional risk mitigation is a signed policy at hire. That works in court but doesn\'t prevent lawsuits. Consent-first mitigates the underlying risk by making every session an actively-consented event, in real time, with logged evidence.

What Connect logs

Every state transition on a manager-initiated screen-view session writes to ScreenViewAuditLog:

• requested — manager submitted a request
• approved — employee explicitly approved
• denied — employee declined
• expired — 30-second timeout, no employee action
• cancelled — manager withdrew before employee responded
• revoked — employee ended a live session by clicking STOP
• ended — session ended normally (manager hangup, network etc.)
• error — session failed to establish

Each row includes:

• Actor (who initiated the action) and target employee
• Jurisdiction — computed from the employee\'s recorded country
• IP address of the manager and employee (best-effort — trust your infra)
• User-agent strings (browser + OS)
• Reason text (if the manager provided one on request)
• Linked CallSession ID (if a session actually established)
• Timestamp with millisecond precision

The rows are immutable. Never updated. Never deleted. Not even by super-admins.

Jurisdiction-aware disclosures

The consent text shown to an employee at approval time depends on their recorded country:

• US, Canada — conservative "two-party consent" language emphasizing recording implications and revocability
• EU, UK — GDPR-framed language emphasizing lawful basis and withdrawal of consent
• GCC states — appropriate to local labor law with Arabic on the roadmap
• Australia, New Zealand — Workplace Surveillance Act-compatible framing
• Default — generic reasonable-person disclosure

Recording as evidence

When recording is enabled, every manager-view session is auto-recorded. The recording IS the evidence — you can prove the manager saw exactly what the audit log says, and only what the employee shared.

Retention is configurable per-org. Set it to your regulatory requirement (90 days, 6 months, whatever applies).

Access-controlled: only the participants, the linked manager-scoped admin, and org admins can play back. Access itself isn\'t (yet) logged — that\'s a v1.1 addition.

Data residency

Connect runs on your DeskTrust deployment. If that deployment is in-region (a specific AWS region for GCC data-residency, or EU for GDPR), so is every byte of Connect data.

Enterprise deployments can be dedicated single-tenant. Contact sales for the isolation options.

The Kuwait Oil Company case

DeskTrust\'s enterprise pilot at Kuwait Oil Company is one of the reasons Connect exists. GCC data-residency, Arabic disclosure requirements, and a strict view of what employee monitoring can look like — Connect\'s design accommodates all three.

The consent-first pattern isn\'t a nice-to-have for those customers. It\'s the entire product criterion.

What Connect doesn\'t solve

• End-to-end encryption for chat messages (chat is server-transported; encryption at rest is standard)
• Advanced DLP integration for chat content scanning
• Automatic redaction of PII from recorded screens
• SOC 2 Type 2 attestation on the recording pipeline specifically (in progress for the overall product)

If any of these are dealbreakers, contact us with your specific compliance framework. Some are v1.1 items, others are enterprise-tier custom work.