A pre-upload exclusion is not a historical visibility control

A pre-upload exclusion is not a historical visibility control. When a session is blocked after earlier ingestion, previously stored rows, raw batches, and derived dashboard projections may remain visible. For an exact-session privacy request, verify the full lineage and each serving surface; avoid keyword suppression because unrelated sessions can share the topic. Prefer a durable per-session tombstone applied consistently to detail, list, aggregate, and replay paths. If no tombstone exists, treat removal as a scoped data-retention operation with dependency and storage inventory, not a single-row delete. This applies to transcript analytics systems; the appropriate retention action still depends on product policy and user authorization.