Inspiration
Phones became scanners. A passport page for a hotel check-in, both sides of a card for an online form, a screenshot of two-factor recovery codes. Automatic backup files them next to holiday photos, often in a family folder that relatives, a TV app or a guest account can open. Nobody searches for files they forgot exist.
What it does
- Maps what other accounts can reach: shared folders with their permission level, other users' folders, external devices, and albums the user has shared. The user says who each folder is shared with, so reach is either confirmed or clearly marked as estimated.
- Proposes candidates from the photo index (OCR signature words and scene search) and splits large result sets month by month past the 20-photo preview, so no candidate hides behind it.
- Confirms a photo only when two independent readers agree: a vision classifier and OCR signals such as a passport machine-readable zone, a card-length digit group or a numbered 24-word list. Photos too dark or angled to judge go to "look yourself" instead of being dropped. PDFs are checked page by page for identifier types.
- Builds an exposure map that stores class, path, reach and a masked shape such as "16-digit number present" - never the value. Digits in file names are masked too.
- After platform approval, moves chosen files into the personal folder and checks digests before and after; tags files kept shared on purpose; and can leave private condition albums that keep catching new matches between sweeps.
- Re-checks every fix on the next run, including album removals made by hand in Photos.
How we built it
Step by step, starting from the capability catalog rather than from the idea: first a list of every Action that could see reach (folder roots, permission labels, shared albums), then the readers, then the fixes. Eleven steps delegating to four registered experts, all reads before any write. The uliya-skill-kit 0.7.7 checker reports static-pass for the package, zero errors and zero warnings.
Challenges we ran into
Making the report safe to keep. A list that quotes the card number it found is a second copy of the leak, so every expert instruction forbids returning recognised text, and the parent removes any digit run that slips through before the map is written.
What we learned
Exposure is about reach, not content. A passport photo in a private folder is fine; the same photo inside a shared album is not.
What's next
On a finalist NAS: what the root types and permission labels really return, OCR signature recall on angled and low-light photos, whether moving a file clears it from an album, and timing on a large photo library.
Built With
- claude
- markdown
- ugos
- uliya-skill-kit