Skip to answer
C CreatorPrivacyKit

Platforms

Platform privacy

A platform guide is the workflow. A lab page is the measurement. A blog post is a narrower field note. Tools are what you run on the file you still control.

Discord image privacy

You can control the file you upload. You cannot audit Discord’s private storage from a downloaded attachment. If GPS or camera identity would be a problem in that server, strip them first.

Telegram image privacy

Treat photo send and file/document send as two experiments. Until a dated lab run exists, sanitize before either button if location would be a problem.

LINE photo privacy

Do not assume LINE removes location data. Chat image, album, Keep, and file-like sends may not share one pipeline. Strip GPS on the file if a home or workplace could leak.

WhatsApp image privacy

WhatsApp documents Standard and HD as quality choices. That is not a statement about EXIF. Document send is a third path. Sanitize before any of them if GPS should stay on the phone.

Instagram image privacy

Cleaning a file controls what you send. It does not guarantee how Instagram labels or ranks a post. Meta has described using provenance signals such as C2PA for AI labels, among other possible inputs.

X image privacy

You can inspect the file you post and the asset a viewer can save. Neither is a ranking report. Strip GPS before a public post if the photo could place you.

TikTok image privacy

Do not copy an Instagram EXIF claim onto TikTok. Name the surface you care about, then measure that file. Sanitize stills before upload if location is sensitive.

Facebook image privacy

Sanitize GPS before a Facebook post if the photo could place a person. File cleanup is not a ranking or label guarantee. AI-label policy is documented separately from EXIF folklore.