Security

Built for firms that answer to regulators.

A model that knows your whole firm has to be careful with it. Here’s where it runs, how your data is kept apart, and what we won’t claim.

  • Runs where you choose.

    Your cloud account, a Niska-managed cloud, or your own servers.

  • A database of your own.

    Each firm gets its own database and search index.

  • Permissions before retrieval.

    Access rules apply before the model sees anything, so each person sees only what they’re allowed to see.

fig. 1 · restricted records stop at the permission check. Illustration.

Where it runs

  • Your cloud

    Niska runs inside a cloud account you own.

  • Niska-managed cloud

    We run it for you, with each firm’s data kept apart.

  • On premises

    On servers in your own network.

What we won’t claim

  • That we hold SOC 2. It’s planned.
  • That every action is logged.
  • That an outside firm has audited us.
  • That no text ever leaves your environment. Ask us which model providers your deployment uses.
Where does our data live?

On the Niska platform, in the deployment you choose: your own cloud account, a Niska-managed cloud, or your own servers. Each firm gets its own database and search index.

Can we start without moving anything?

Yes. Niska can read your current document system in place. Nothing moves until you decide to run a process on Niska.

Who can see what?

Access follows your firm’s rules before the model sees anything, so the model only uses what the person asking may see.

Bring your security questions to the demo.

Book a demo