HISTORICAL DIG · JUL—AUG 2026
Is this redacted PDF or PNG actually safe to send?
A black box can hide pixels while leaving searchable or copyable PDF text. An image that looks covered still needs its final pixels, transparency, and metadata checked. “Not visible” describes rendering—not removal from the sharing copy.
WHERE THIS RECORD SITS TODAY
Relation to the current subject
A separate historical disclosure record—not a branch of Workflow 001 or the Questions.
Workflow 001 deals with tool overload and project continuity. This record deals only with disclosure control in one final file. They share one method: define the checking scope, reverse-check the final copy, and block sending whenever an item cannot be confirmed.
Record state at the time
- Work and handoff
- Sensitive-data workflows
- In-depth record
- Monitoring · narrowed
- E3 · two exact synthetic PDFs reproduced · no real-file or independent-user result
THE GUIDANCE AT THE TIME
Judgment at the time
Separate “not visible” from “removed from the final copy.”
Open full rationale and return rules
Separate the formats, then inspect the final sharing copy. Use a real redaction command for PDFs and review copyable text, comments, attachments, forms, scripts, metadata, and hidden layers. For images, crop the copy or use a fully opaque mask, export a fresh flattened image, and review transparency and metadata. Any unresolved item blocks sending; consequential files still follow the approved review path.
- Who it was for
- People preparing to disclose an image or PDF copy they are authorized to handle and can inspect locally in its final form
- Why it mattered then
Open note
Sensitive information is often impossible to recover once disclosed. Visual cover, text removal, hidden-information cleanup, and organizational approval are separate checks that one visual review cannot replace.
- Where the judgment stops
Open note
BitShovel reproduced only the difference between two fully synthetic one-page PDFs: one looked covered while its text remained extractable; the comparison produced no extractable text in this run. It did not validate arbitrary tools or PDF, PNG, or JPEG files, metadata removal, cloud history, signatures, accessibility, compliance, or an independent-user outcome. A clean search, copy, OCR, or visual check is not a safety certification.
CHECK BEFORE READING ON
Fit check
Use this record only when the source, copy, and disclosure scope remain under control.
This record may help
- You are authorized to handle the file, have listed the fields that must be removed, and can work only on a local copy.
- You can inspect the final sharing copy rather than only the editable source or an in-app preview.
Do not use it yet when
- A legal, medical, financial, regulatory, or organizational process requires an approved tool, reviewer, or audit record.
- The sensitive scope is unclear, or the file is already present in cloud sharing, version history, or copies you cannot account for.
- Digital signatures, searchable text, or accessibility structure must be preserved and you cannot verify the converted result.
HISTORICAL SYNTHETIC TEST COMPLETED · CHECKLIST NOT USER-VALIDATED
Historical trial
Treat it as stop/go triage, not a safety determination.
- Time needed
- Earlier estimate: about one minute for stop/go triage only; a full review was not timed
- Likely cost
- No site fee; approved tools, professional review, or remediation may add cost
- Permission boundary
- Use only an authorized local copy; do not upload a real file to BitShovel
- 01
First step
Open this step
Identify whether the final sharing file is an image or PDF, make a dedicated copy, and list both the fields to remove and the functions that must remain before running the format-specific checks.
- 02
What should exist
Open this step
A scope record covering visible pixels, copyable text, hidden information, metadata, sharing or version history, unresolved items, and the final decision to stop or seek approval.
- 03
How to record that this run found no blocker
Open this step
Record only that the declared checking surfaces were completed with no unresolved item; do not label the file safe. Consequential files still require the designated reviewer.
- 04
Stop when
Open this step
Stop when policy requires an approved process, hidden structures cannot be inspected, or required signatures, search, or accessibility cannot be confirmed after conversion.
- 05
How to back out
Open this step
Keep the original, discard test or export copies, revoke any active sharing links, and stop disclosure until the issue is resolved.
SOURCES AND EVIDENCE
Sources and evidence
As of August 15, 2026, E3 covers only two byte-fixed synthetic PDFs; official material adds checking surfaces without expanding the tested scope.
Open evidence boundary
E3 covers only two byte-fixed synthetic PDFs: the black-box sample still yielded the fictional price and check token, while the comparison yielded no extractable text in this run. No-text-extracted is not promoted into proof of file safety, compliance, or send-readiness.
- 01Exact BitShovel synthetic artifact · Checked then
Black-box PDF: pixels covered, text still extractable
Open source boundary
One page, 55,315 bytes, SHA-256 d95455f840353c972043d43a50ef1129ae82b0e75fa1155b83ef0ae65cceaa5b. This run still extracted CNY 27,500 and DEMO_PRICE_27500. It proves failure only for this fixed synthetic file.
Open original source ↗ - 02Exact BitShovel synthetic comparison · Checked then
Image-based comparison PDF: no text extracted in this run
Open source boundary
One page, 193,913 bytes, SHA-256 fb57be8b8648ec07deb738b109d08cc165f202c6ecd25b0a0451e91b3a9e7e60. No text was extracted in this run; that does not establish metadata removal, OCR resistance, compliance, or safety for arbitrary files.
Open original source ↗ - 03Regulator guidance · Checked then
ICO: electronic-document and image-redaction boundaries
Open source boundary
The guidance says black rectangles can leave underlying text, recommends working on a copy, reviewing before disclosure, and recording the decision, and warns that blur or pixelation may be reversible. Published July 31, 2025, it is currently marked under review following UK legal changes.
Open original source ↗ - 04Vendor procedure · Checked then
Adobe Acrobat: apply redactions and separately remove hidden information
Open source boundary
Adobe's current documentation treats visible text-and-image redaction, Apply, hidden-information removal, and saving a separate file as distinct steps. It documents the current Acrobat Pro procedure, not a safety certification for arbitrary PDFs.
Open original source ↗ - 05Platform documentation · Checked then
Apple Preview: Redaction Selection is distinct from ordinary Shapes
Open source boundary
Apple lists Redaction Selection separately from Shapes and says a redaction becomes permanent after the document is closed. That wording does not establish removal of metadata, attachments, or every hidden structure.
Open original source ↗
REVISION RECORD
Revision record
R3 narrows E3 and removes the implication that a few clean surface checks establish send-readiness.
Open 2 revisions
- Revision 2
Added who the check is for, a minimal test, success criteria, when to stop, and what to do after a failure, while stating that no user reproduction exists.
- Revision 3
Limited E3 to the difference between two synthetic PDFs, removed the implication that clean search, copy, OCR, and visual checks establish send-readiness, and added metadata, hidden-object, and approved-review boundaries.
- What the record said before
- A copy could be treated as send-ready when search, copy, OCR, and visible-region checks showed no blocker.
- What changed
- Those checks cover only declared surfaces. No unresolved item means no blocker was found in this run—not that the file is safe; consequential disclosure still requires approval.
WHAT THIS RECORD LEAVES
What this record leaves
The last pre-disclosure check belongs to the final copy—not the editor preview.
Define the sensitive fields, functions that must remain, and approval requirements first. An unresolved item is a reason to stop, not a reason to stretch the word safe.
Back to the Dig index