Restore Limits

Restore only works on values that survive the AI output.

CloakShift replaces private-looking values locally and stores the reversible mapping in your encrypted vault. It cannot restore a value if the AI removes it, rewrites it, merges it, summarizes it away, or invents a substitute.

What to review before relying on restoration.

01

Keep exact values

Keep cloaked aliases, tokens, headers, sheet tabs, dates, IDs, and file names exactly as written.

02

Use Token Mode for labels

Tokens like <PERSON_a3f7> are useful when you want compact placeholders for tables, code, queues, or repeatable workflows.

03

Review before sharing

Use the mapping table to edit aliases or revert false positives before sending a file out.

04

Preserve structure

Ask the LLM not to add, remove, rename, reorder, merge, or split table rows and columns.

05

Detection can miss details

Review the output for missed names, locations, IDs, amounts, and metadata before sharing.

06

Vaults are required

If the vault or passphrase is lost, CloakShift cannot restore real values from the cloaked file alone.

07

OCR has layout limits

Connect includes a local OCR path, but image quality, handwriting, unusual fonts, and complex scanned-PDF layouts still need human review.

08

No certification claim

CloakShift helps reduce exposure. It is not a legal or compliance certification.