Skip to main content
Every record in ARUKZ ERP belongs to one company, and the application only ever returns records of the company you are signed in to; automated tests that check one workspace cannot read another’s data run on every release. Inside your company, roles decide which screens each person can use and record visibility decides whose records they see. Pages are served only over HTTPS, passwords are stored hashed, and the database is backed up every night.

One company cannot see another

  • Every business record carries its company. Orders, invoices, lots, employees, roles and attachments are filtered by company on every request, including through the API, search and exports.
  • A company admin manages only their own company. They cannot see other companies’ users, give anyone the ARUKZ platform role, change the shared roles, install plugins or add database fields.
  • Your own address. Your team signs in at erp.arukz.com/<company>/admin; a person who is not a member of that company is refused, and an unknown address returns “not found”. See Company address.
  • ARUKZ staff can reach every workspace to run the platform. At most two staff sign-ins can be open at a time, and their actions on a workspace (activations, suspensions, plan changes, payments) go to an append-only log.

Sign-in and access

Your books

  • Edit log. Changes to the books are logged by the database with who, when, before and after, sealed into a daily hash chain, and cannot be switched off. See Audit trail.
  • Export at any time. An admin can download every business table as CSV, also while the workspace is read-only. See Export all data.
  • Nothing is deleted when you stop paying. A lapsed workspace turns read-only, and a cancelled one stays readable for 90 days. See Read-only mode.

Backups

The database is backed up every night, each backup is checked after it is written, and the last fourteen copies are kept.
Today these backups are kept on the same server as the application. Encrypted copies on a separate server, and a backup location in India, are planned but not live. If your company must keep a daily backup of its books on servers in India under the Companies (Accounts) Rules, take your own regular exports in the meantime.

AI and your data

AI is off until the AI module is switched on for your company and a company admin switches it on in AI settings, which records who agreed and when. After that, questions, the figures needed to answer them and bills you upload are sent to the AI provider. An AI app you connect over MCP is different: it reads with a person’s own API token, so what it reads goes to that app’s provider under the terms of whoever set it up. The assistant and the MCP server only read; they cannot post, pay or change anything. See Ask AI.

What is not in place yet

  • Encrypted backups on a separate server, and a restore drill (planned).
  • A Content-Security-Policy header.
  • Published privacy, terms and refund policies. Ask ARUKZ if you need them for a vendor review.

Known limits

Everything ARUKZ ERP does not do yet, in one list.

Users and roles

Decide who sees what.
Last modified on November 12, 2026