Page 2 of 8~116 min topic

Privacy and smart sharing

What counts as sensitive

Sensitivity is contextual. Direct identifiers, linkable details, private communications, credentials, and consequential inferences can all require protection.

~15 min this pageData classification

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

Smart sharing ladder
  1. 1
    HideDon’t paste it
  2. 2
    ScrubRemove names / IDs
  3. 3
    AskIs this tool private enough?

Climb down before you paste anything sensitive

Sensitivity is contextual. Direct identifiers, linkable details, private communications, credentials, and consequential inferences can all require protection.

Read

A practical lens

Use this three-part method:

  1. Classify secrets, personal data, sensitive attributes, and business-confidential material. Write down what this means in the scenario, what evidence would show it was done, and who owns the decision.
  2. Consider combinations that identify someone. Write down what this means in the scenario, what evidence would show it was done, and who owns the decision.
  3. Raise protection when consequences are serious. 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 meeting note contains no password, but it includes an employee’s illness, performance concern, salary range, and manager comments.. Label three moments where “What counts as sensitive” 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

  • Looking only for names and email addresses. This shortcut removes useful friction, but it also hides an assumption that should be tested. Replace it with an observable check.
  • Assuming public data is harmless in every context. This shortcut removes useful friction, but it also hides an assumption that should be tested. Replace it with an observable check.
  • Ignoring what a model can infer from several ordinary facts. 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 What counts as sensitive 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.

Read

Extra mastery block

For privacy-smart-sharing, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.

Read

Extra mastery block

For privacy-smart-sharing, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.

Read

Extra mastery block

For privacy-smart-sharing, write a transfer example that differs in one constraint from the chapter scenario. Keep the quality bar fixed. Explain which check still applies.

Go deeper

Before you start

Why this matters

A meeting note contains no password, but it includes an employee’s illness, performance concern, salary range, and manager comments.

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.

Check your understanding

Page assessment

Answer from memory. Completion is saved from this evidence, not from opening the next page.

Local focus for What counts as sensitive (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.

1. Explain the page’s core distinction without using the word “smart.”
2. Which fact, source, permission, or test would most change your judgment in the opening scenario?
3. Name one low-consequence use where a light check is enough and one high-consequence use where independent review is required.
4. What should a responsible user do when the available evidence cannot support the requested conclusion?

All responses are required.