Security

How UnitedStatesCredit separates public content, general tools and sensitive product-request information.

Last updated
Effective November 3, 2026Version 1.0All UnitedStatesCredit experiences
Separated experiencesPublic content, tools and secure product flows have different data needs.
Restricted sensitive dataSSNs and account information require dedicated controls.
No absolute guaranteeSecurity reduces risk but cannot eliminate every possibility.

1. Security approach

USC uses administrative, technical and physical safeguards designed for the nature of the information processed. No website or transmission method is completely secure, and this page should not be read as a guarantee against every incident.

2. Separate information zones

Public content

Guides, articles, public rate data and general calculators should avoid collecting identity information.

Product request

Contact, eligibility and financial information belongs in the secure product flow, not in editorial pages or site search.

Sensitive identity and account data

SSNs, bank details and credit-report authorizations require tighter access, logging and vendor controls.

3. Core controls

  • Encryption in transit for data submitted through secure forms.
  • Role-based access and least-privilege administration.
  • Separation of sensitive fields from advertising and general analytics systems.
  • Audit logging for material access, consent and routing events.
  • Vendor due diligence, incident response and tested backups.
  • Masking or disabling sensitive fields in session replay, logs and support tools.

4. What visitors can do

Verify the USC domain before submitting information, use a private device and secure connection, do not place SSNs or bank information in search or email, and review the destination before leaving USC for a provider site.

5. Report a concern

Report a suspected security issue to info@bluekeel.com. Do not include sensitive personal information in the initial message.