Purpose
This framework defines the trust obligations for a product that asks students to discuss identity, motivation, uncertainty, work style, and personal direction. The product must be useful without becoming invasive.
Core Principles
- Private by default.
- No therapy or diagnosis claims.
- Collect only what is needed.
- Let users edit and delete their profile.
- Distinguish student statements from system interpretation.
- Avoid manipulative personalization.
- Do not pressure users into sharing sensitive information.
- Make data retention understandable.
Data Categories
| Data Type | Examples | Collection Rule |
|---|---|---|
| Required Profile Data | education, work experience, goals, activities, strengths | Collect only for profile generation. |
| Optional Context | family expectations, financial constraints, personal background | User-controlled and skippable. |
| Sensitive Disclosures | mental health, abuse, trauma, medical information | Do not solicit. If volunteered, handle carefully and avoid profile exploitation. |
| Generated Interpretations | work style, strengths, risks, career direction signals | Must be editable and evidence-linked. |
| Usage Data | completion rate, conversion, satisfaction scores | Aggregate where possible. |
Consent Language
This tool helps create a practical profile based on your answers. It is not therapy, medical advice, psychological diagnosis, or crisis support. You control what you share. You can skip questions, edit your final profile, and request deletion where supported.Safety Boundary
The workflow should not ask for trauma, medical history, mental-health diagnoses, abuse history, or intimate personal details. If the user volunteers crisis-related content, the product should pause the normal workflow and provide crisis-oriented guidance rather than converting that material into a profile asset.
Privacy Commitments
- Profiles are not public by default.
- The student must approve any shareable version.
- Generated profiles should be editable before export.
- Data retention must be disclosed before collection.
- Deletion process must be simple and visible.
- No sale of identifiable student profile data.
- No employer access without explicit student consent.
University Readiness
If the product moves into universities, the privacy model must mature. Career-center pilots should include institutional review of data handling, student consent, administrator access, data retention, and aggregate reporting.
| Requirement | Reason |
|---|---|
| FERPA-aware posture | Education records and institutional use may trigger additional obligations. |
| Role-based access | Counselors should not see private student material without permission. |
| Aggregate reporting | Universities may need outcomes without exposing individual profiles. |
| Data processing terms | Institutional procurement will require documented controls. |
Red-Line Claims
- Do not claim to diagnose personality or mental health.
- Do not claim to predict destiny or guaranteed career outcomes.
- Do not claim to replace career counselors, therapists, or advisors.
- Do not claim that the output is objectively who the student is.
- Do not imply employers should rely on the profile without student control.