Your data, and who can reach it

Local means local

On the Mac deployment, your business data is on your machine. It is not uploaded to be understood, not copied to a vendor's infrastructure for processing, and not held anywhere you cannot point at.

This is a structural property of the deployment, not a policy commitment. There is no pipeline to a service we operate, so there is nothing to audit, no sub-processor list to review for that path, and no transfer to account for.

For the on-premises deployment the same holds at the scale of your data centre: the system runs inside your network, governed by your team.

Why reviews get shorter

Most of a data protection review is spent establishing where data goes, who else can see it, and what happens if the vendor is compromised. When the answer to the first question is "it does not leave this machine", the rest of the questions largely resolve themselves.

That is usually the difference between an evaluation that takes a quarter and one that takes an afternoon.

Access

Nexyron requires authentication. People hold accounts, accounts hold roles, and roles determine which databases they may reach and what they may do there.

Grant the narrowest access that lets someone do their work, review it when people change roles, and remove it when they leave. This is ordinary practice and Nexyron is built to support it rather than to work around it.

AI, and what it is allowed to touch

Two capabilities are worth distinguishing, because they have different properties.

Understanding your data happens on your machine. Working out what your records mean and finding what is relevant to a question does not involve an external service.

The reasoning layer of the assistant currently uses an AI provider you choose and supply credentials for. Your data is not used to train that provider's models, but the requests do reach it, and that is a fact your review needs. If that is unacceptable in your context, the query language, the analytics and the Lenses all work without the assistant.

Deletion

Data you remove is removed. On the local deployment the database is a file on your machine, which makes both retention and disposal something you control directly rather than request.

What to ask us

If you are preparing a review, ask for what you actually need: a description of the deployment you are choosing, the credentials and access model, and where any external service appears in the path. We would rather answer precisely than send a brochure.