PRIVACY
Operational data should stay inside its authorized boundary.
NexusWork is designed to separate public contact information from customer workspaces and to keep authenticated records governed by their deployment and tenant boundaries.
Ask a privacy questionWork
Work stays connected to the outcome it serves.
A plain-language description of current behavior.
These sections describe the public site and product boundary. Formal commercial privacy terms still require legal review and approval.
What this public site collects
The contact form collects the name, work email, organization, role, topic, and message a visitor chooses to provide. It also records the page from which the request was sent.
How contact details are used
Contact details are used to respond to the request, coordinate a relevant conversation, and protect the form from repeated automated submissions. They are not written into a customer workspace.
Workspace data
NexusWork operational data is processed within the workspace and deployment environment selected for that organization. Access is governed by authenticated sessions, role checks, and application permission boundaries.
Cookies and sessions
The application uses session cookies to maintain authenticated access. Public marketing pages do not require a workspace session to read.
Security and retention
Deployment-specific retention, backup, logging, and deletion rules must be established by the organization operating the environment and reflected in its approved policy and agreement.
Before commercial launch
This page is a plain-language description of current behavior, not a substitute for counsel-approved privacy terms. It must be reviewed and formally approved before commercial public launch.
Ask about a specific deployment or data boundary.
Do not include sensitive customer or operational information in the public form.
Contact NexusWork