Skip to content
Get in touch
A worker copies a document from a locked company laptop into an AI tool. Records spill from protected storage into the tool, then branch toward a log, a cloud, and a connected network.
Reviewed visual · version 1

RS Glossary

Data Leakage

Data leakage is the unintended exposure, transfer, or disclosure of information to a person, system, model, or destination that is not authorized to receive it.

Note that machine-learning practitioners use the same phrase for a different problem: information from test or future data leaking into training, which makes a model look more accurate than it really is. This entry covers the disclosure sense.

Review state
Reviewed in POC
Freshness
Current
Version
3
  • Data Leakage
  • Information Leakage

Remember it this wayInformation crossed a boundary it was not meant to cross.

In plain language

Leakage can happen through prompts, logs, outputs, training data, retrieval systems, integrations, exports, or access mistakes. The information may be visible immediately or recoverable later.

Why it matters

AI workflows often copy information across several services and contexts. Each handoff can change retention, access, and disclosure risk.

Example

An employee pastes client records into an unapproved public assistant whose service terms permit retention beyond the intended task.

Common misconception

Data leakage is not limited to a public breach. Sending information to an unauthorized internal tool or unintended model context is also leakage.

Related terms

Sources

Learn more

  • Start with [[sensitive-information|Sensitive Information]] and examine every [[handoff|Handoff]].

Public history

46 recorded events · 46 public summaries
  1. A potential shared concept was discussed and selected for initial glossary drafting.

  2. The captured candidate received a complete initial draft and entered section-level human review.

  3. Radar reviewed the initial definition draft for human consideration.

  4. Radar reviewed the initial plain-language-explanation draft for human consideration.

  5. Radar reviewed the initial why-it-matters draft for human consideration.

  6. Radar reviewed the initial example draft for human consideration.

  7. Radar reviewed the initial common-misconception draft for human consideration.

  8. Radar reviewed the initial remember-it-this-way draft for human consideration.

  9. Radar reviewed the initial related-terms draft for human consideration.

  10. Radar reviewed the initial sources draft for human consideration.

  11. Radar reviewed the initial learn-more draft for human consideration.

  12. A proposal was opened for section-level human review while preserving the current version.

  13. A human reviewer opened a proposed revision while preserving the current approved or captured version.

  14. definition approved by a human reviewer.

  15. plain-language-explanation approved by a human reviewer.

  16. why-it-matters approved by a human reviewer.

  17. example approved by a human reviewer.

  18. common-misconception approved by a human reviewer.

  19. remember-it-this-way approved by a human reviewer.

  20. related-terms approved by a human reviewer.

  21. sources returned for revision.

  22. learn-more approved by a human reviewer.

  23. Requested wording was prepared without changing approved or existing sections.

  24. Radar reviewed the pending sources section for human consideration.

  25. Radar must rereview the complete data-leakage term after an accepted text change.

  26. Radar must rereview the complete data-leakage term after an accepted text change.

  27. Radar must rereview the complete data-leakage term after an accepted text change.

  28. Radar must rereview the complete data-leakage term after an accepted text change.

  29. Radar must rereview the complete data-leakage term after an accepted text change.

  30. Radar must rereview the complete data-leakage term after an accepted text change.

  31. Radar must rereview the complete data-leakage term after an accepted text change.

  32. Radar must rereview the complete data-leakage term after an accepted text change.

  33. Radar must rereview the complete data-leakage term after an accepted text change.

  34. sources approved by a human reviewer.

  35. sources approved wording became the current section text.

  36. All section gates are approved; content version 2 is now a fully approved term.

  37. Radar rereviewed the human-approved definition wording for this exact version.

  38. Radar rereviewed the human-approved plain-language-explanation wording for this exact version.

  39. Radar rereviewed the human-approved why-it-matters wording for this exact version.

  40. Radar rereviewed the human-approved example wording for this exact version.

  41. Radar rereviewed the human-approved common-misconception wording for this exact version.

  42. Radar rereviewed the human-approved remember-it-this-way wording for this exact version.

  43. Radar rereviewed the human-approved related-terms wording for this exact version.

  44. Radar rereviewed the human-approved sources wording for this exact version.

  45. Radar rereviewed the human-approved learn-more wording for this exact version.

  46. Definition review recorded as replace.

Source: vault/Glossary/terms/data-leakage/term.md · sha256:7a6215d21ca7e80a3c4939df7a26aa15d23850e29bc5b16095c39af9215cdd63 · Release: rs-glossary-glossary-team-poc-0.5.5-2026-09-02