Security
Built to be vetted.
For the IT and compliance teams reviewing NinthOar: where your data lives, who can reach it, what is recorded, and what is never stored at all.
How NinthOar protects your data
A separate instance for every lender
Your company runs its own NinthOar instance on Amazon Web Services in the United States — its own server and data, its own address, its own fixed outbound IP. No other lender’s data shares it.
Sign-in through your identity provider
Microsoft Entra ID or Google Workspace, restricted to your tenant or domain. NinthOar holds no passwords, so your MFA and conditional-access policies apply, and turning off a work account turns off NinthOar.
New accounts wait for approval
Someone who signs in for the first time without being added gets a pending account and no access until an admin approves them and gives them roles.
Role-based access, explained
Every permission is granted by a role, with per-person exceptions. Managing people, roles, sign-in secrets and impersonation are admin-only. Effective Access shows what anyone can do and exactly why.
An append-only audit trail
Approvals, role and exception changes, enabled and disabled accounts, support impersonation starting and ending, note edits and deletions, and training events are recorded. Audit rows cannot be edited or deleted.
Compliance records that can’t be rewritten
Submitted exams, certificates and published course versions are frozen in the software, and the database refuses to delete a person or course that has training history.
Less data, by design
Social Security numbers and dates of birth are never stored. Loan data arrives from your LOS and nothing is written back to it.
Secrets encrypted at rest
Credentials for your LOS, email, e-signature and sign-in connections are encrypted in the database. Sign-in secrets can be changed by admins only.
Encrypted in transit
Every instance is served only over HTTPS, and session cookies are HTTP-only.
Records that outlive employees
People are disabled, not deleted, so their history — notes, approvals, training — stays attributable after they leave.
Questions IT asks
Security questions
Where is our data stored?
In your company’s own NinthOar instance on Amazon Web Services, in the United States. Each lender’s instance is separate — its own server, its own data, its own address and its own outbound IP.
Who at NinthOar can see our data?
We operate your instance as your service provider and act on your instructions. Inside the application, signing in as another user — an admin-only function — is recorded in the audit trail when it starts and when it ends.
Does NinthOar store borrowers’ Social Security numbers?
No. Social Security numbers and dates of birth are never stored in NinthOar. It keeps what operations needs: the loan, its status, dates, team, lock, disclosures and conditions.
How do people sign in, and how do we cut off access?
Through your identity provider — Microsoft Entra ID or Google Workspace — restricted to your tenant or domain. NinthOar has no passwords of its own, so your multi-factor and conditional-access rules apply, and disabling someone’s work account ends their access. An admin can also disable them in NinthOar, which keeps their history.
Can a vendor allowlist our instance?
Yes. Each instance sends from its own fixed IP address, which a vendor can allowlist.
How do we report a security issue?
Email security@ninthoar.com. A person reads it.
How this website handles what you send it is in the privacy policy.
Early access
Bring your security questionnaire.
We’ll walk your IT team through the instance, the sign-in, the audit trail and the data we never keep.