How Poko Handles Sensitive Information

The principle is restraint

Good support does not need every detail. For Weekly Reset, the useful information is usually functional: what is coming up, what feels overloaded, what needs protecting, what pressure point is likely and what next move would help. You should not have to share a full personal, medical or crisis history to make the week more workable.

Sensitive information belongs in the right setting

Medical details, diagnosis history, trauma, crisis information, safety concerns and deeply personal material may need privacy, consent and professional context. Weekly Reset is not the place to process or assess those details. Keep them for the appropriate support setting.

Private prompts reduce unnecessary disclosure

Private prompts let you work with your own information without broadcasting it. You can name the pressure point in your own words, keep the detail to yourself and still use the structure. That is better for privacy and often better for cognitive load.

What Poko needs to know

Poko needs enough practical information to support the function task: the week, the load, the pattern, the next move and the support conditions. It does not need unnecessary personal story. Where information is collected, the purpose should be clear and proportionate.

What to do if something feels too sensitive

If something feels too sensitive for the resource, session or prompt, do not force it in. Translate it into function language if that is safe: I need recovery after this, this decision carries pressure, this meeting will use a lot of capacity. Or take it to the appropriate private, clinical, legal, workplace or crisis support context.

How to use this

• Share the functional shape, not unnecessary sensitive detail.
• Keep clinical, crisis and deeply personal information for the right setting.
• Ask what information is actually needed to make the next week more workable.