Customer name, phone, address, company name.
Illustrative browser demo: use fictional details only. This is not a security audit or a guarantee about every deployment.
Security demo
See how protected personal details differ from financial records.
When optional PII protection is enabled, personal fields are encrypted at rest while authorized app workflows can still use them after unlock.
View in:
Personal details turn into secret code before saving.
Your business numbers keep working. Identity stays hidden.
Step 1
Type sample details
Use fictional details only. This demonstration runs in your browser.
This is the secret key that locks customer data. It is not the app login password.
Identity details get locked. Loan amount stays readable so reports and collections can work.
Step 2
See the difference
This is what your data looks like with and without protection.
Click "Run demo" above to see the comparison.
Personal identity is unreadable. Business numbers still work.
Anyone with database access can read everything — name, phone, address.
Loan amounts are saved normally so your business runs fine. But customer names and phone numbers look like random letters.
Final check
What can someone see if they open your records?
This is the simple result when someone opens the saved records directly.
Can someone see the customer, borrower, company, or other personal details?
No
Can someone see the phone number?
No
Can someone see the address?
No
Can authorized app users view protected customer data?
After unlock
Can someone figure out which customer or company has which financial information from the saved data?
No
Can the wrong key unlock the data?
No
Waiting for test…
With optional PII protection enabled, selected personal fields are encrypted at rest. Authorized app users can unlock them with the company passcode; financial records remain available for calculations and reports.