Skip to main content

Security & compliance

Easy to enter. Hard to cross.

Proaqsa ERP enforces company, location, role, record and field boundaries on the server for every request. Identity, company selection and permissions are separate, checked decisions — a simple sign-in never blurs a company boundary.

Layered shields representing company, location, role and field boundaries

Boundaries

Four layers, all enforced server-side.

01

Company isolation

Every record carries its company. Queries, pages and actions are scoped to the signed-in company; cross-company reads are rejected, not merely hidden.

02

Location scope

Branches see their own stock, sales and people. Wider visibility, such as sub-branches or peer branches, is an explicit setting on the user or role.

03

Role & record rules

Row-level security filters lists and reports by company and location scope; actions check the same rules before they run.

04

Field-level security

Cost prices, margins, salaries and other sensitive fields can be hidden or read-only per role, in forms, lists, prints, ledgers and stock reports.

05

Verified identity

Email verified at sign-up with a six-digit code, password sign-in, password reset by a single-use emailed link, and passkeys for platform operators.

06

Document history

Every posting traces back to its document; voided invoices stay on record and can be restored, and audited revisions keep the original as superseded.

Platform operations

Administration that cannot act alone.

Two-operator control for sensitive platform changes

Platform-level changes such as plan catalogue publishing or operations activation follow a propose-and-witness protocol with passkey-verified operators, signed audit events and checkpoints. No single browser session can enable privileged operations by itself.

  • Passkey (WebAuthn) for platform operators
  • Signed, hash-chained audit events
  • Fail-safe relock available at all times
Two operators completing a witnessed approval

Data handling

Data is stored in a managed MariaDB database with daily backups, transport encryption (HTTPS) and strict security headers. Private configuration and keys live outside the web root.

  • HTTPS everywhere
  • Daily backups
  • Secrets outside public_html
Encrypted data flows between browser and database

Questions?

Need a security questionnaire or data-processing details?

Write to us and we will respond with the documentation your team needs.

FAQ

Frequently asked questions

Where is my data stored?

In a managed MariaDB database on the hosting platform used by Proaqsa ERP, with daily backups. Each company's records are isolated by tenant identifiers enforced in every query.

Does hiding a menu item secure a feature?

No. Navigation is only presentation. Every page, list, report and action is checked on the server against company, location, role and field rules.

Do you support passkeys?

Platform operators sign in with passkeys (WebAuthn) and fresh re-verification for sensitive actions. Business users sign in with a password; their email is verified at sign-up and password resets use a single-use emailed link.

Can I export my data?

Yes. Reports print on A4 and download as CSV, the analysis and financial reports also export to Excel (XLSX) and PDF; full data exports are available on request.