Security, privacy, and controlled access are built into the V2 platform approach.
MyCreditUW V2 handles sensitive readiness information, uploaded documents, AI-assisted insights, profile data, membership access, and partner visibility workflows. The platform is being built around controlled access, account separation, document ownership checks, user consent, and source-layer separation so information is useful without being casually exposed.
This page explains the approach at a high level. It is not a technical audit, legal certification, or security guarantee. It is a plain-language overview of how MyCreditUW is approaching privacy, security, access control, AI use, and document handling as the platform moves through pilot testing and toward production readiness.
Trust depends on more than features.
Users are entering profile details, readiness information, and sometimes uploading sensitive documents. That means the platform must limit exposure, separate user accounts, control access, and avoid showing information to the wrong person.
Useful information, limited visibility.
MyCreditUW is designed to help members understand preparation and readiness while keeping document access, AI insights, partner visibility, and saved state tied to rules, permissions, and user context.
How information is protected in the platform design
Protection is not only about storage. It also includes what gets saved, where it gets saved, who can access it, how it restores after login, and how document or AI-derived data is kept separate from user-entered profile inputs.
Keep data useful, separated, and controlled.
The V2 platform is designed around separated data layers so intake inputs, readiness outputs, document evidence, AI summaries, What-If simulations, and partner summaries do not overwrite each other.
Account-specific restore
V2 uses logged-in account context and user-specific persistence so saved platform data can restore when a member returns. We are actively testing cross-account behavior so one user’s information does not appear for another user on the same device.
Separated storage layers
Intake data, readiness outputs, progress outputs, document wallet records, document evidence, AI summaries, What-If simulations, and partner summaries are intended to remain in separate layers instead of being mixed together.
Secure transmission and access rules
Member-side and partner-side experiences are designed around authenticated access, PMPro membership levels, REST nonces, protected pages, and route-level restrictions so access is not open by default.
Document upload and AI handling
MyCreditUW V2 may allow members to upload documents, including income documents, tax documents, credit reports, bank statements, identity-related documents, or other readiness support. Some documents may be reviewed by AI-assisted extraction tools when the member’s access level allows it.
AI supports review. It does not make decisions.
AI-assisted document reading is used to extract visible facts and support readiness explanations. It does not approve, deny, underwrite, repair credit, or guarantee outcomes.
Document ownership checks
Document AI endpoints are designed to validate that the logged-in user owns or is authorized to access the uploaded attachment before processing it.
AI access controls
Free users should not trigger premium AI document reading. Pilot and Founding access can unlock deeper document-backed intelligence according to platform rules.
AI caching and cost control
AI results may be cached so the platform does not repeatedly call AI services when the same source data has not changed. AI cache belongs in AI or evidence layers, not inside raw intake inputs.
Access, membership levels, and partner visibility
MyCreditUW V2 uses membership levels and protected routes to control what each member can access. Free, Pilot, and Founding members may see different levels of readiness detail, AI insight, document support, and advanced tools.
Partners should not automatically see everything.
Partner visibility is intended to be consent-based, readiness-aware, and limited. Raw documents should not be automatically exposed to partners without a controlled request and release process.
Membership-based access
Platform access is shaped by PMPro membership levels, including Free Preview, Pilot Access, Founding Access, and partner-specific access where applicable.
Locked and blurred sections
Lower-tier members may see previews or locked sections while deeper analysis, AI details, document intelligence, and advanced tools remain limited to the proper access level.
Consent and visibility rules
Partner-facing readiness views are intended to depend on user consent, visibility settings, readiness thresholds, confidence thresholds, and partner access approval.
What MyCreditUW does not do
The platform is preparation-focused. It helps members understand readiness, organize information, view simulations, upload support, and receive educational AI-assisted explanations.
Readiness is not approval.
A readiness score, confidence score, AI summary, document review, or partner-visible profile is not a lending decision, underwriting decision, approval, denial, or guarantee.
MyCreditUW is not:
- A lender or loan originator
- An underwriting system
- A credit repair company
- A credit bureau
- A legal, tax, accounting, or financial advisor
- An approval or eligibility guarantee
MyCreditUW is designed to help with:
- Readiness preparation
- Profile organization
- Document readiness visibility
- Progress tracking
- AI-assisted plain-English explanations
- Controlled partner visibility when permitted
Electronic consent, AI processing, and platform acknowledgment
By creating an account, uploading documents, entering profile information, using AI-assisted features, accessing readiness tools, or continuing to use MyCreditUW V2, users acknowledge and consent to the digital processing and handling of information within the platform.
Using the platform means consenting to digital workflows.
MyCreditUW V2 is a digital readiness and preparation platform. Certain features rely on electronic storage, AI-assisted processing, automated calculations, document uploads, account restoration, and controlled visibility workflows.
Electronic communication consent
Users consent to receiving digital communications related to account activity, readiness updates, membership access, issue reporting, AI processing status, document workflows, billing activity, and platform notifications.
AI-assisted processing consent
Users understand that uploaded documents, readiness information, worksheet data, and profile information may be analyzed by AI-assisted systems designed to support extraction, organization, readiness explanation, and educational insights.
Document handling acknowledgment
Users acknowledge that uploaded documents may be stored, categorized, reviewed, cached, associated with readiness evidence, and processed through document-readiness or AI-assisted workflows according to platform rules and access controls.
User understanding
- Readiness scores are not approvals or denials.
- AI insights are educational and preparation-focused only.
- Document uploads do not guarantee improved readiness or outside approval.
- Partner visibility may depend on consent, thresholds, and platform rules.
- Some features may remain in pilot, simulated, or evolving states.
Platform acknowledgment
- Users are responsible for reviewing information for accuracy.
- Users should not upload documents they are unauthorized to provide.
- Users should report incorrect restore behavior or unexpected account data immediately.
- MyCreditUW may continue improving security, AI governance, persistence, and access controls over time.
Ongoing security and production-readiness work
MyCreditUW V2 is actively moving through pilot testing and production-readiness improvements. Security, access control, persistence, document release, AI governance, audit logging, issue reporting, and partner workflows are expected to continue improving as the platform matures.
Issue reporting is part of the process.
Pilot members can report problems so account access, data restore, calculations, page flow, document behavior, and AI outputs can be reviewed and improved.
More controls may be added over time.
Future updates may include deeper audit logs, stronger server-side source locking, improved document release workflows, AI usage limits, and expanded admin monitoring.
Visibility should remain intentional.
The goal is not to expose more information by default. The goal is to make the right information available in the right context, with the right controls.