Legal aid intake privacy risk begins at a painful moment. A person looking for free legal help may be facing eviction, debt collection, benefits denial, wage theft, domestic violence, immigration paperwork, guardianship, disability access, or a family crisis. The intake form may ask for legal name, address, phone, income, household size, court dates, opposing-party names, landlord or employer information, benefits status, immigration context, disability details, safety concerns, and uploaded notices or letters. Before a lawyer or advocate has accepted the case, the person may already have shared the most sensitive facts of the crisis.

Legal aid exists for a good reason. The Legal Services Corporation explains that civil legal aid helps low-income Americans with problems involving basic needs such as housing, safety, health care, and income. USA.gov directs people to legal aid and lawyer-referral resources because many people cannot afford private counsel. The privacy problem is not legal aid itself. The problem is that digital triage can make a desperate person type a full life emergency into a web form without knowing who stores it, who screens it, and whether the organization can actually help.

Intake data is unusually revealing because it combines identity with vulnerability. A housing case may expose an address, rent amount, eviction notice, landlord dispute, and household composition. A debt case may expose creditors, medical bills, bank accounts, or collection letters. A benefits case may expose disability, immigration, family, or income details. A safety case may expose where someone is staying and who they fear. These are not abstract privacy preferences; they are facts that could create risk if sent to the wrong party, kept too broadly, or exposed by a compromised account.

The FTC's identity-theft guidance matters because intake packets often include documents that prove identity or hardship: government IDs, Social Security numbers, pay stubs, benefit letters, leases, court filings, medical bills, or bank statements. The FTC's personal-information security guidance gives the practical baseline: protect sensitive information, share it carefully, and reduce unnecessary exposure. For legal aid intake, that means applicants should verify the organization's official website or hotline, avoid random lead-generation ads, and be cautious when a form asks for full documents before explaining why they are needed.

NIST's Privacy Framework is useful here because it treats privacy as a risk-management problem, not just a notice page. A good intake system should collect the minimum data needed to route a case, explain whether the form creates an attorney-client relationship, limit access to advocates who need the information, and protect uploaded documents. It should also separate urgent safety instructions from ordinary analytics. A person asking for help with a protective order or eviction should not have to wonder whether marketing pixels, chat widgets, or third-party form tools are watching the same page.

A practical checklist for applicants is modest but important. Start from an official legal aid directory, court self-help page, or trusted hotline rather than an ad that says instant free lawyer. Read the intake notice before uploading documents. If a form asks for every detail of a conflict, give enough to screen eligibility and urgency, then save the most sensitive evidence for a confirmed secure channel. Use a safe phone number or email if the opposing party might monitor the usual account. Keep copies of what you submitted, and write down the date, organization name, and any case or intake number.

Legal aid organizations can reduce harm by designing intake as a narrow triage lane. Ask for case category, deadline, eligibility, and contact method first; request detailed documents only when necessary; avoid public tracking on crisis pages; and make privacy expectations plain. That does not slow help down. It makes help safer. The point is to connect people to advocates without turning poverty, housing stress, family danger, or immigration fear into another durable data profile.

cloak's role fits this surface because legal problems are leverage points. A person in crisis can be pressured into oversharing by urgency, confusing forms, or fake help offers. A defensive browser layer can flag suspicious legal-aid lookalikes, warn when sensitive uploads or tracking scripts appear, and remind the user to verify the channel before sending documents. cloak cannot provide legal advice, but it can help keep the path to legal help from becoming a new privacy injury.