Book a proof session
Trust Center

Your data stays yours.

Where Juron runs, what happens to your data, who can see what, and how every result can be checked.

Security and privacy

Six things your security team will ask about.

Each one in plain words. The architecture below and our security pack go into more detail.

01 · Deployment

Runs on systems dedicated to you

Runs on systems dedicated to you, on your premises or in an environment we operate for you. Never shared.

  • Single-tenant: your system serves only you.
  • Runs on hardware we operate for you, or on your own infrastructure.
  • Network access is limited to the systems you connect.

02 · Your data

Your data stays yours

We use your data only to solve the problems you give us.

  • Never shared with other customers.
  • Never used to train AI models for anyone else.
  • Read where it lives where possible; copies stay inside your system.
  • Removed at the end of the engagement, on your instruction.

03 · Access

People see only what their role allows

Every app has roles. Viewers use the results, builders can change the app, admins manage access.

  • Access set per app and per person.
  • Every version of an app is kept, and can be rolled back.
  • Our team's access is limited to the engagement and agreed with you.

04 · AI models

The AI you approve

Juron is not tied to one AI provider. It works with the models your security team approves, including models that run entirely inside your system.

  • You choose which models may be used.
  • Changing the model does not change how results are tested.

05 · Audit and proof

Every result can be checked

Each solution ships with a report card, and each number can be traced.

  • Tested on recent data the solution never saw while it was built.
  • Compared with your current method; if it doesn't win, it doesn't go live.
  • The data, steps and settings behind each result are recorded and can be re-run.
  • Frozen versions: the same data in gives the same answer out.

06 · Compliance

Certifications

Formal certifications will be listed here as they are completed.

Security questionnaires and architecture reviews are answered as part of every engagement.

Architecture

Your infrastructure. Our operators. Your approval.

"We run it for you" means a system that is yours alone. Runs on systems dedicated to you, on your premises or in an environment we operate for you. Never shared. Our operators monitor, re-check and update it.

You control our access. Each operator is named, their access is limited to this system, and you approve it. You can review or remove it at any time.

Your data is read in place. Copies made for the work stay on your dedicated system. Web access is off unless you turn it on.

Encryption, retention and incident response are set out in our security pack, written for procurement and security teams.

Request the security pack
Questions

Security teams usually ask.

Does any data go to an outside AI provider?

Only if you approve it. Juron can run entirely on models inside your system. Where you choose an external provider, we agree in writing what may be sent.

Where is the system hosted?

Runs on systems dedicated to you, on your premises or in an environment we operate for you. Never shared.

Who on your side can access our data?

Only the named people on your engagement, with access agreed with you and limited to the systems you connect.

Can we review the architecture before anything starts?

Yes. We walk your architecture and security teams through the deployment, data flows and access model before anything is connected.

What happens to our data when we stop?

It is removed from the system on your instruction, and we confirm in writing.