Trend report · gnews_detection · 2026-06-17
When an Accra High Court case exposed a sophisticated AI deepfake fraud ring targeting Ghanaian businesses and individuals, it confirmed what investigators had suspected: AI-generated content is no longer just a viral meme problem—it's a primary attack vector for financial fraud and identity crime across Africa.
Most creators assume platforms detect AI content by analyzing pixels or recognizing a specific tool's output. That assumption is wrong and getting flagged will cost you.
In 2026, Instagram, TikTok, YouTube, and Reddit run automated scans within seconds of upload. They're not looking at whether your video "looks fake"—they're reading the invisible metadata layer underneath every file. Here's what's actually triggering those shadowbans and removal notices:
assertion_c2pa with digital_source_type: trainedAlgorithmicMedia. Platforms parse this manifest before the first frame renders. A single export can carry 18+ JUMBF atoms and 16 C2PA references—all screaming "AI-generated" to automated systems.xmpMM:History entries referencing generator software, and the photoshop:AuxiliaryMetadata block containing DigitalSourceType: trainedAlgorithmicMedia. These persist even after you rename the file.glbl, avcC) contain telltale signatures. A phone recording and an FFmpeg export from Sora have structurally different bitstream syntax.Make: Apple, Model: iPhone 16 Pro, Software: 18.3, GPS coordinates, and a capture timestamp in EXIF. An AI export has none of these. Platforms flag files with missing device identity—it's a fast, cheap heuristic for AI-generated content.The Ghana fraud case illustrated the stakes: investigators traced payments through deepfake videos used to impersonate executives, and the same metadata fingerprints that exposed the fraud are the ones getting ordinary creators flagged on social platforms today.
Calabi doesn't edit your video's pixels, paint over regions, or reconstruct any part of an image. It works entirely on the invisible metadata and structural signals that platforms actually scan.
Stage 1 — Strip: Calabi removes every detection signal in a single pass. All 18+ JUMBF / C2PA atoms are zeroed to 0. The trainedAlgorithmicMedia flag and every XMP AI reference get stripped. Encoder fingerprints—Lavc, x264 SEI units, QuickTime metadata—are removed. The result: your file has no cryptographic record of AI generation.
Stage 2 — Inject: Calabi injects authentic phone-capture identity. You select a real device profile—iPhone 16 Pro, Pixel 8 Pro, or Galaxy S24 Ultra. The tool writes genuine Make, Model, Software, GPS coordinates, and capture timestamp into EXIF. It uses the same encoder name that a real phone uses. The file now looks, structurally, exactly like a phone recording.
Stage 3 — Verify: Before download, Calabi generates a forensic proof card—running the same ExifTool scan platforms use. You'll see exactly what was stripped (18 JUMBF atoms → 0, 16 C2PA references → 0, 144 AI metadata tags → ~94 neutral structural tags) and what was injected (device profile, GPS, timestamp, encoder). You get a verifiable audit trail.
If your AI export has a visible watermark in the corner—a sparkle icon, a tool logo—cropping removes it. Calabi does not claim to erase logos pixel-by-pixel. What Calabi removes is the invisible detection layer that survives cropping: the C2PA manifest, XMP flags, and encoder fingerprints that platforms read even after you've cut away the visible mark. Remove the visible watermark with your editor; then run Calabi to strip the invisible signals that would still get you flagged after upload.
Does re-encoding or compressing my video work instead?
Re-encoding disrupts perceptual hashes and can help with pHash-based detection, but it does nothing for C2PA manifests, XMP AI flags, or encoder fingerprints—these persist through recompression. It's a partial solution at best.
What if my export doesn't have a visible watermark?
Most AI content gets flagged for metadata signals alone—no visible watermark required. A clean Sora or Runway export with no visible mark can still trigger platform detection because the structural metadata is what platforms scan first.
Can Calabi guarantee my content won't be flagged?
No tool can guarantee this. Platform detection systems update constantly, and results vary by platform and source model. Calabi removes every metadata and structural signal it can control—the C2PA layer, XMP flags, encoder fingerprints, and device identity—which addresses the primary detection vectors platforms use today.
→ Try Calabi free at calabilabs.com — 10 cleans, no card.