Data and control
You decide what goes into your office
We explain in concrete terms how information is handled and what depends on third parties. We do not offer absolute guarantees: we document how each deployment is configured and what its limits are.
Request a demoArchitecture per deployment
How data, access and environments are separated is decided and documented for each deployment. The client experience reuses the design of the internal Lynx.studios office, not its data or credentials.
Permissions
You decide which documents and tools the office can use and which people on your team can access each part. Anything not authorised is not part of the working context.
AI providers
Third-party AI services may be involved in generating text. Before we start, we tell you:
- Which provider is involved in each function.
- What information it receives.
- Which terms of use and retention apply.
Human review and logging
Results arrive as drafts and a person reviews them. Actions on other tools are only switched on if they are agreed and verified in your deployment.
Requests, tasks and results are logged in your office.
Does data leave your server?
It depends on the agreed architecture and providers. If a third-party AI provider is involved, it receives the information needed for the agreed function; we detail this before it is switched on.
Where is the privacy policy?
On the site’s privacy page. For each deployment we also document which data is processed and by which providers.
Request a demo
We’ll show you the office with a sample walkthrough.
- A guided walkthrough of the office with sample data.
- We look at which tasks might fit and which would not, with no commitment.
- If we go ahead, we send you a written scope proposal.