01
Start in a private workspace
Keep a client, matter or project in its own workspace from the outset.
Private by design
Private by design.
A private AI workspace for sensitive, source-led work. Access is permission-based, sharing is authenticated, and your data, outputs and interactions are not used to train Zylox.
No card required.
Permission-basedInvite the people who should be in the workspace, and give them the role the work needs.
Not used for trainingCustomer data, outputs and interactions are not used to train Zylox.
Acme Corp · Deal roomPrivate workspace
Source filesContracts, notes and material added to this workspace.
Answers and draftsWork that stays connected to its source context.
Edits and activityA visible workspace record of meaningful work.
Invited peopleAuthenticated members with the access you choose.
× Zylox training× Uninvited access× Open sharing
How Zylox uses your work
Retrieval, not training.
Zylox retrieves relevant source material from the workspace to answer the question. Customer data, outputs and interactions are not used to train Zylox.
Your question
Asked in the workspace where the work belongs.
Zylox retrieves
Relevant passages are selected from the material you added.
The model answers
The answer is generated from the selected context for that question.
Cited answer
Review the answer with the supporting source material close by.
Customer content is not training data
What you add, ask and produce in Zylox is not used to train Zylox.
Workspace-scoped context
Relevant material is retrieved from the workspace that the authenticated user can access.
Deletion is a product control
Workspace deletion covers related product content and retrieval artifacts; metadata-only audit evidence may remain.
Private work, without extra steps
Keep confidential work under control.
Use one workspace for the work, the source material and the people involved. The structure stays simple because the boundary is already part of the workflow.
02
Share with permission
Invite authenticated people and give them only the access the work needs.
03
Keep the boundary clear
Your data, outputs and interactions are not used to train Zylox.
Acme Corp · Deal room · Private
AccessInvited people
TrainingNot used for Zylox training
Why it is different
Closed by design, not locked down after.
Workspaces are organised around explicit membership, so you start with who should be involved rather than working backwards from an open record.
Permission-based sharing makes it clear what belongs together, and who should have access to it.
Control should not make the work harder. Keep the sources, questions, answers and decisions in the same workspace.
What stays together in a Zylox workspace.
A general-purpose chat
Conversation-first work
- You decide what source material to paste into each chat.
- Context can be separated from the work it relates to.
- Sharing the result can mean moving it elsewhere.
- Access control depends on the wider tool and workflow.
Workspace-first work
- Source material, questions and answers stay connected.
- Answers can show the supporting source material.
- Access is based on authenticated workspace membership.
- Customer content is not used to train Zylox.
Questions
Private by design, in detail.
How does workspace access work?
Workspace access is permission-based. You invite people by email; they authenticate before access is granted. Workspace members receive the role you choose, and access can be changed or removed.
Does Zylox train on my documents?
No. Zylox does not train on client data, client outputs or client interactions.
Can I delete a workspace and what is in it?
Workspace deletion covers related product content and retrieval artifacts. Zylox retains metadata-only operational evidence where needed to keep deletion and activity accountable.
Can I start with one real file?
Yes. Start free with a real document, ask a question in plain words and review the source material that supports the answer.
Cited answersKeep supporting source material close to the answer.→Audit trailsKeep a visible record of meaningful workspace activity.→Collaborative workspacesBring the right people into the work.→
For a security review
The practical appendix.
These are the current hosted-cloud principles. If you need a different operating boundary, we can discuss customer-controlled or on-premise deployment.
Discuss requirementsTraining on customer contentCustomer data, outputs and interactions are not used to train Zylox.
Workspace accessAuthenticated access through workspace membership and invitations.
Hosted-cloud posturePermission-based isolation and least-privilege internal access.
DeletionProduct content and retrieval artifacts are covered by the deletion flow; metadata-only audit evidence can remain.
Stronger custody requirementsCustomer-controlled or on-premise deployment can be scoped with you.