Security

You are trusting us with your customers and your money.

That deserves specifics rather than a badge wall. This page describes how Nolira is built, what we protect, and what we have not finished yet.

Flat illustration of a locked cabinet of client records behind a shield panel.

Encryption

Data is encrypted in transit with modern TLS. The database runs in Singapore on our hosting provider's storage, and every nightly backup is encrypted with AES-256 before it leaves for a second location.

Tenant isolation

Every business record carries an organisation identifier derived from the verified session, never from client input. Repository filters, authorisation checks and tenant-aware cache keys enforce it, and automated tests specifically hunt for cross-tenant leakage.

Authentication

Short-lived access tokens with rotating refresh, a list of every signed-in device with remote sign-out, a lockout after repeated wrong passwords, and rate limits on every public sign-in and booking route.

Least privilege

Access is denied by default. Every permission is granted over a scope, and the riskiest acts need a second person: a branch manager can agree to a refund at the outlets their role covers, never at another, and never one they asked for themselves.

Audit trail

Sensitive actions record who did it, their role, the device, what it was done to, the reason, the time and a correlation ID. Passwords, tokens and customers' details are never written to it.

Backup and recovery

A backup every night, checked to be complete before it counts, kept for thirty days in a second location, encrypted. Restoring one is written down and has been tested: a full restore took seconds and the restored copy took a sale.

Sensitive by default

Customer data is kept to what the counter needs.

The less a salon system holds about a person, the less there is to leak. Nolira keeps a customer to a name, a number, an email, a language and one note, and treats anything more sensitive as a class of its own to be designed before it is built.

  • A customer record holds a name, phone number, email, language and one general note, and nothing else
  • No photographs, allergy records or treatment notes are kept today; when they are built they will be a restricted class of their own
  • A customer who asks to be forgotten is erased, and their bills stay for the accounts without their name
  • Customer details never appear in logs or in the audit trail, which records only that something happened and to which record
  • Nolira is not a medical records system and does not store diagnoses or prescriptions

How we build

  • Thousands of automated tests, including tenant boundaries, authentication and every money path
  • Tests deliberately broken to prove they catch the fault they guard against
  • Concurrency tests run against real PostgreSQL, because two tills at once is where money goes missing
  • A backup taken before every release that changes the database
  • Signed application builds, with signing keys kept off the code
  • Independent penetration testing before broad launch

Payments

  • Nolira takes no payment online today: cards are taken on the salon's own terminal and recorded in Nolira
  • Nolira never sees or stores a card number or CVV
  • Every payment recorded carries a key, so a retried request can never record it twice
  • When online deposits are built they will go through a hosted payment page, never through our servers

Reporting a vulnerability

If you believe you have found a security issue, write to [email protected] with enough detail to reproduce it. We will acknowledge receipt and keep you updated. Please give us reasonable time to fix an issue before disclosing it publicly.

What we have not done yet

Nolira is an early-stage product. We hold no SOC 2 or ISO 27001 certification today, and we would rather say so than imply otherwise. Enterprise single sign-on, SCIM provisioning and data residency options are on the roadmap rather than shipped.

If your procurement process requires a certification we do not hold, tell us early and we will be straight with you about whether the timeline works.

Send us your security questionnaire.

We would rather answer it properly before you buy than discover a blocker during onboarding.