Privacy and smart sharing
Choose a safer workflow
Privacy is shaped by the whole workflow: provider terms, account configuration, retention, training reuse, access controls, human review, and deletion.
1Try it yourself
Playground
Share or hide?
One item at a time — decide what is OK to paste into a chatbot.
Message 1 of 6
A public recipe you want rewritten
2Learn the idea
Read
The core idea
See it
- 1HideDon’t paste it
- 2ScrubRemove names / IDs
- 3AskIs this tool private enough?
Climb down before you paste anything sensitive
Privacy is shaped by the whole workflow: provider terms, account configuration, retention, training reuse, access controls, human review, and deletion.
Read
A practical lens
Use this three-part method:
- Compare whether data is stored or reused. Write down what this means in the scenario, what evidence would show it was done, and who owns the decision.
- Prefer approved and purpose-limited tools. Write down what this means in the scenario, what evidence would show it was done, and who owns the decision.
- Test deletion, access, and incident routes before routine use. Write down what this means in the scenario, what evidence would show it was done, and who owns the decision.
Read
Worked example
Walk through A team can use a public chatbot, an approved enterprise account with limited retention, or a local template that needs no AI.. Label three moments where “Choose a safer workflow” changes what you trust: (1) the first fluent answer, (2) the first missing source or permission, and (3) the decision a human must own. Write the before/after task so the model only does the slice that evidence supports. Keep one sentence that states how this page’s idea differs from a generic “AI is smart/dumb” score.
Read
Common traps and better moves
- Trusting a privacy label without checking configuration. This shortcut removes useful friction, but it also hides an assumption that should be tested. Replace it with an observable check.
- Using a personal account for company records. This shortcut removes useful friction, but it also hides an assumption that should be tested. Replace it with an observable check.
- Collecting more context merely because storage is available. This shortcut removes useful friction, but it also hides an assumption that should be tested. Replace it with an observable check.
Read
Build the habit
Before you close the tab, capture a reusable habit for Choose a safer workflow inside Privacy and smart sharing: name the observable check, the evidence you would open, and the stop condition. Rehearse it once on a low-stakes example, then once on a higher-stakes variant. The habit succeeds when you can explain the check without reopening this lesson. Target outcome: Recognize personal, sensitive, confidential, and secret information before sharing.
Go deeper
Before you start
Why this matters
A team can use a public chatbot, an approved enterprise account with limited retention, or a local template that needs no AI.
In the wild
See how this idea shows up as a product and a company — then come back to the lesson. Skills transfer across vendors.
Related lessons
Check your understanding
Page assessment
Answer from memory. Completion is saved from this evidence, not from opening the next page.
Local focus for Choose a safer workflow (Privacy and smart sharing): write the smallest test that would falsify a confident claim on this page, name the evidence you would open first, and note who must approve if the cost of being wrong is more than a redo. Keep the note under ten lines so you will actually reuse it.
All responses are required.