Security
Here is exactly what is switched on today, and what is not. Where something is only partly built, we say so rather than implying more protection than exists.
Sign-in and second factor
Accounts use email and password with email confirmation, and passwords are checked against known breached-password lists. Staff accounts must set up an authenticator app and pass that second step before any staff screen or staff action will work. Customers may turn the second step on as well.
Who can see what
Every role — customer, advisor, processor, admin, read-only — is checked by the database on every read and write, not just hidden in the interface. Customers see only their own loans and only the files they uploaded themselves, even when several people share one loan file. Role changes are made on the server by an admin who has just passed their second factor; nobody can change their own role, and the last admin cannot be removed.
Where files live
Uploaded files are kept in private storage that has no public address. Opening a file goes through the server, which checks permission first and then hands back a link that stops working after two minutes.
Upload checks and virus scanning
Before anything is stored the server checks the file name, extension, declared type and size; after it is stored the server re-reads the bytes to confirm the contents really match the file type, and a file that fails is deleted and never enters the library. Every new upload is then scanned for malware by a third-party scanning service on our servers: an infected file is deleted immediately and never enters the library. If the scanner cannot be reached, the file is held in quarantine and cannot be opened, reviewed or read by the AI until a scan comes back clean. Files uploaded before these checks existed are marked as never scanned; customers cannot open them, and staff can only open them after acknowledging a warning, which is recorded.
Encryption
Traffic is encrypted in transit with TLS and data at rest is encrypted by our hosting provider. We rely on those provider controls; we do not currently add a separate application-level encryption layer, and no encryption keys are held in the browser.
Audit trail
Sign-in and second-factor events, permission denials, uploads, file opens, status changes, role changes, exports, retention actions and administrative changes are written to a record that cannot be edited or deleted from the application. The trail stores who, what, when and the outcome — never document contents, form answers, identity numbers, passwords or keys. Staff can search it and export it, and the export is itself recorded.
Backups and recovery
Database backups are provided by our hosting platform. We have a place to record backup verifications and restore tests, but a check is only shown as done when someone has recorded evidence for it. Nothing here should be read as a verified or tested recovery capability.
Keeping and deleting records
Retention schedules, legal holds and deletion requests are tracked in the app, and a deletion needs two different approvers with a hold check in between. Deletion is not automatic and no purge job runs against existing records today.
Independent assurance
We are not SOC 2 certified, we have no completed independent audit, and no outside security-monitoring or compliance-automation service is connected. Our written security programme and risk assessment are drafts pending management adoption and legal review. Nothing on this page should be taken as a claim of regulatory compliance or certification.
Data minimisation
The product is scoped to intake, documents and staff-reviewed decisions. It does not store credit reports or third-party scoring data.
Reporting an issue
Demo contact only: security@loaniq.cc.example.
This page is illustrative content for a product demo and is not legal advice.