What is this portal for?

I built this portal as a transparency hub that explains ethical data stewardship for AI-enabled mental health in plain language. It helps users understand consent, data use, fairness, accountability, and recourse, and it provides practical templates to support trustworthy AI governance.

Who is this portal for?

I designed it for three groups:

• Patients (18–50) who want clarity, choice, and recourse.
  
  

• Clinicians and care teams who need safe workflows and escalation guidance.
  
  

• Institutions and governance leaders who need repeatable stewardship tools.

Does this portal provide medical advice?

No. I designed this portal for governance communication and education. It does not diagnose, treat, or replace clinical care.

What AI systems does this apply to?

I focus on AI-enabled mental health tools, including screening/triage support, documentation aids, and conversational support tools. I do not evaluate one specific commercial product.

What data do AI mental health tools typically use?

Depending on the tool, data can include account information, usage patterns, self-reported mood or symptom inputs, conversational text, and optional device signals (only if users opt in). I explain these categories clearly so users can make informed decisions.

What does “informed consent” mean here?

I treat consent as a process, not a checkbox. I require clear, plain-language explanations of what data is collected, why it is collected, how it is used, who can access it, and what choices users have, including the option to withdraw.

Can I withdraw consent after I start using a tool?

Yes- ethical systems should support withdrawal or feature-level opt-out where feasible. I explain withdrawal, deletion, and access expectations in the Consent & Data Use section and in the Consent Checklist download.

What does “fairness” mean in mental health AI?

I define fairness as consistent performance and respectful outcomes across different groups. I monitor disparities over time and document corrections, rather than treating fairness as a one-time test.

Why do you emphasize audit trails?

Audit trails make accountability real. Logs help trace access, changes, version updates, and incident actions. Without traceability, institutions cannot reliably investigate harm or prove responsible governance.

What counts as an incident?

I treat incidents as privacy breaches, harmful outputs, fairness failures, or governance failures (like undocumented system changes). I provide a clear response flow and templates to ensure reporting and remediation remain consistent.

What happens after someone reports a problem?

I follow a structured response- report → contain → investigate → notify → remedy and prevent recurrence. I also explain escalation pathways and how recourse works if a user is not satisfied.

What are the downloads, and why do they matter?

The downloads turn governance into action. They provide repeatable checklists and templates for consent communication, fairness monitoring, auditability, and incident response so teams can implement stewardship consistently.

How should I use the dashboard prototype?

I use the prototype to demonstrate what transparency looks like for users in practice - what a person can see about data use, consent choices, accountability, and recourse in one place.

What are the limitations of this portal?

I built this portal using secondary research and governance frameworks, not clinical trials. Organizations must adapt it to local laws, policies, and workflows. I present it as a practical, communication-focused stewardship model.