Security & privacy
Built for some of your most sensitive information.
A credit report contains your accounts, balances and addresses. These are the protections MyCreditLab is built on — and what's still being verified before launch.
How your data is protected
Encrypted, file by file
Every uploaded file is encrypted with AES-256-GCM using its own key. That key is wrapped by a key unique to your account, which is wrapped again by a master key held outside the database.
Isolated at the database
Row-level security in the database means each request can only see rows belonging to the signed-in account — a second barrier behind the application's own checks.
Strong sign-in
Passwords are hashed with a memory-hard algorithm. Two-step sign-in with an authenticator app is available, sessions expire after inactivity, and repeated failures lock the account temporarily.
Checked before storage
Uploads are identified by their contents, not their name, and PDFs containing scripts or embedded files are rejected before anything is stored.
No outside AI on your data
Analysis runs inside MyCreditLab with versioned, explainable checks. Your report data isn't sent to external AI services.
No trackers
No advertising pixels or third-party analytics on any page, and a strict content security policy blocks third-party scripts.
Your activity, visible
Sign-ins, uploads, downloads, exports and deletions are logged to an append-only history you can review.
Deletion that sticks
Delete a file or your whole account at any time. Account deletion destroys your key, so any copy left in a backup can't be read.
Before real credit data
MyCreditLab is in a pre-launch build. Until the items on the right are complete, please upload only sample or test reports.
See how it works- Independent security assessment and penetration test
- Threat model review and incident response plan
- Managed encryption keys (KMS) and encrypted backups in production
- Legal review of privacy terms and data handling