Kernel — File Sanitizer

Photos you send carry more than the picture. A photo remembers where it was taken, which camera took it, and the second it happened. A scanned PDF keeps the scanner's name, its edit history, and layers you were never shown. Kernel rebuilds files instead of scanning them. It prints the file's own facts in plain language — "Rue de Rivoli, Paris", "iPhone 16 Pro", "Tue 11 Mar, 14:08" — then removes exactly those and writes a brand-new file around the pixels or the pages. Everything that was not content is left behind by construction, not by blocklist. ONE SCREEN Every file states in one sentence what it is giving up. Tap once to see the specifics, struck through. Tap once more to clean the batch. There is no navigation to learn. IT REFUSES TO DAMAGE YOUR FILES Ask for JPEG when a logo has a transparent background and JPEG would paint it white — so Kernel keeps that one as PNG and says so on the row. Ask for JPEG when a photo is HDR and it would be crushed to 8 bits — so Kernel leaves that one alone and says so. It never quietly does the destructive thing, and it never enlarges anything. WHEREVER YOUR FILES ALREADY ARE The share sheet, Photos, Files, drag and drop, Shortcuts, Siri, the Action button and Control Center. NOTHING LEAVES THIS IPHONE No account, no network permission, no analytics, no server. Kernel has no way to send a file anywhere — that is an absence of capability, not a policy. It will not even look up where your coordinates are: place names come only from what the file itself already wrote down. HONESTLY SCOPED On iPhone, Kernel cleans images and PDFs. Heavy video re-encoding and cryptographically sealed archives are Kernel for Mac's job, and the app tells you so instead of pretending otherwise. Your originals are never touched. Kernel only ever writes new files.