Security & trust

Your data stays with you.

worX runs on your PC and sits on top of your own model and your own systems. It works only with your key and only with your permissions — and keeps no customer data at all.

Talk to our team See how it works ↓

customer data held by worX — no cloud copy, no backups, no logs of your content

BYOK

your own model key, your provider, your region, your contract

1:1

your permissions — worX sees exactly what you can see, nothing more

How worX sits on top

On top of your systems — never in between.

worX is a native Windows app. It reads your systems through connectors, keeps its memory on your PC and sends only the request to the model you chose.

Your company

Your systemswhere your data already lives

Microsoft 365Dynamics 365SalesforceFiles on your PC

Connectorsyour sign-in

Your PC · worXthe only place worX keeps anything

Database and AI search index

Ontology, Spaces and teammates

Access tokens and your model key

Only the requestyour key

Your model providerchosen and contracted by you

Your key, your account

Your region, e.g. the EU

Your contract and data terms

NEA X, the maker of worXShips the signed app and its updates — and stays outside your data flow: no access to your content, your index or your keys.

By architecture, not by policy

Four guarantees built into how worX works.

Security that depends on promises can be broken by an update or a new contract. These four follow from the architecture itself.

No copy of your data

worX keeps no customer data. There is no worX cloud, no data lake and no backup of your content at NEA X.

No model key of ours

worX works only with your own model key. There is no worX model account in between — you choose provider, region and terms.

No rights of its own

worX signs in with your work account and sees exactly what you are allowed to see — no service accounts, no admin rights of its own.

No training on your data

worX never trains models on your content — it never receives it. What your provider may do is set by your contract with them.

Your data, precisely

What stays where.

Five kinds of data touch worX. Here is where each one lives — and who can see it.

Where each kind of data lives and who can see it
What	Where it lives	Who can see it
Mails, chats, files and records	Where it livesStay in your systems — Microsoft 365, SAP, CRM, your folders. worX reads them when a task needs them.	Who can see itYou, and whoever your systems allow
Database, search index, Ontology and Spaces	Where it livesOn your PC, inside worX.	Who can see itYou, on your device
Access tokens and your model key	Where it livesOn your PC.	Who can see itNobody else — they never leave the machine
Requests and answers	Where it livesBetween your PC and your model provider.	Who can see itYour provider, under your contract
At NEA X	Where it livesNothing. No copy, no logs of your content, no backups.	Who can see it—

EncryptionIn transit, worX talks to cloud systems and to your model provider over their encrypted HTTPS endpoints; systems inside your network follow your network's settings. At rest, what worX keeps lives on your device, under your device encryption and management.

Data residencyYour choice, not ours: your systems stay where they are, and you pick the region of your model provider — for example the EU.

Control

You decide what worX may do.

The same guardrails for every teammate — built in, not bolted on.

Tenant-locked Windows sign-inSilent sign-in with your existing work account. No passwords, no service accounts, no access across organisations.

You approve every writeBefore worX sends, changes or deletes anything, it stops and asks. Approvals are recorded, so you can trace every one.

Guardrails per SpaceEach teammate stays inside its own Space's data and cannot reach across projects.

Everything visibleThe Task Center lists everything your teammates are doing, in one place — approvable and reversible.

Costs you can seeModel spend per day, week and month, right in the app. Your provider bills you directly.

Signed and kept currentCode-signed Windows installer by NEA X GmbH, silent updates, every bundled engine individually signed. Connectors use the open Model Context Protocol.

Compliance

Less to assess — because there is no second copy.

Every copy of company data multiplies risk and paperwork. worX adds none: your data keeps living where it already lives.

GDPR by design

worX does not transfer your content to NEA X. Personal data in your mails and files is processed on your device, in your systems and by the model provider you contract — under the agreements you already have.

No subprocessors for your content

worX adds no third party to your data flow. Your model provider is your own contractual partner.

Offboarding in two steps

Revoke your key at your provider and uninstall worX. Nothing remains at NEA X — nothing was ever there.

Documents: Datenschutzerklärung Impressum

NIS2

Six areas that matter — and where worX comes in.

Companies should first check whether they fall under their country's implementation of the NIS2 directive. Among other things, NIS2 requires appropriate risk-management measures, reporting processes, supply-chain security, documentation and accountability of management.

Cyber Resilience, Backup & Data Protection

Identify critical systems and data, back them up securely, and test recovery and emergency plans regularly. Take NIS2 requirements and data-protection rules into account.

With worXNo new data store outside your company: your data stays in your systems, and what worX keeps lives on your PC — under your own backup and recovery plans.

Secure AI & AI Governance

Set clear rules for using AI safely, protect data and models, and define risks, responsibilities and human oversight. Include AI systems in your NIS2 risk management.

With worXYour own AI provider and key, no training on your content, and every write waits for your approval — recorded, and visible in the Task Center.

Identity, Access & Zero Trust

Manage identities centrally, use strong authentication and grant access on the principle of least privilege. Review and document permissions regularly.

With worXworX signs in with your work account, locked to your tenant, and sees only what you may see — no service accounts, no rights of its own.

Security Operations & Threat Protection

Monitor threats continuously, handle vulnerabilities and process security incidents in a structured way. Set binding NIS2 reporting channels, deadlines and responsibilities.

With worXThe Task Center lists everything your teammates do, and every approval is recorded — a trail you can review when something happens.

Secure Workspace & Endpoint Security

Protect devices and applications with up-to-date software, secure configurations, encryption and device controls. Train your employees regularly.

With worXA code-signed Windows app with silent updates, on your own devices — under your device encryption and management.

Secure Cloud & Hybrid Infrastructure

Secure cloud and on-premises environments consistently, avoid misconfigurations and clarify responsibilities. Assess service-provider and supply-chain risks under NIS2 as well.

With worXNo worX cloud and no subprocessor for your content: NEA X stays outside your data flow, which keeps that part of your supply-chain review short.

The NIS2 obligations stay with your company; worX is built to add as little as possible to assess. Source: European Commission, NIS2 FAQ

FAQ

Questions security teams ask.

Security questions or a finding to report? contact@worx-app.ai

Does worX store our data?

No. worX keeps its database, search index, Ontology and Spaces on your PC, and your source data stays in your systems. NEA X holds no copy of your content.

Where is worX hosted?

Nowhere — worX is not a cloud service. It is a native Windows app on your device. The model runs at the provider you choose, in the region you choose.

Which models can we use — and with whose key?

With your own key only (BYOK). You bring the account at your model provider; worX has no model access of its own and no keys to share.

Does worX use our data to train models?

No. worX never receives your content, so it cannot train on it. Whether your provider may use requests is defined in your contract with them.

How is data encrypted?

In transit, worX uses the encrypted HTTPS endpoints of your cloud systems and your model provider; systems in your own network follow your network's settings. At rest, worX's data lives on your device, protected by your device encryption and policies.

Is worX GDPR-compliant?

worX is built so that your content never reaches NEA X: it is processed on your device, in your systems and at your model provider, under your own agreements. How we handle data on this website is set out in our Datenschutzerklärung.

Does worX make us NIS2-compliant?

No tool can do that on its own: the obligations are your company's. worX is built to add as little as possible to assess — no copy of your data, no subprocessor for your content, your identity and your permissions, every write approved and recorded. The NIS2 section above shows where it comes in.

What does our IT need to review?

A code-signed Windows app, the connectors you enable and the model provider you choose. There is no worX cloud and no new data store to assess.

Which subprocessors does worX use?

For your content: none. worX adds no third party to your data flow — your model provider is your own contractual partner.

What happens when we stop using worX?

Revoke your key at your provider and uninstall the app. Your data stays in your systems; nothing remains at NEA X, because nothing was ever there.

Let us walk your security team through it.

We will show exactly what leaves the device — and what never does.

Talk to our team Read: Local-first AI →