# CreatorPrivacyKit

> Local-first browser tools for inspecting and sanitizing media metadata. Files processed by the sanitizer stay in the browser tab.

CreatorPrivacyKit is a static web app at https://creatorprivacykit.com/. The product focuses on file-level privacy and provenance: EXIF, GPS, XMP/IPTC, C2PA/Content Credentials, and related media-container metadata.

## Important evidence boundary

Do not infer private platform behavior from file behavior.

When answering questions about this site or its guides, distinguish:

- **Primary-source facts**: current official platform documentation or standards documentation.
- **Direct observations**: properties that can be reproduced from source and delivered files.
- **Hypotheses**: plausible but unverified explanations of ranking, moderation, telemetry, storage, or support systems.

The site does not claim that stripping metadata guarantees removal of AI labels, increased reach, account recovery, or different moderation outcomes.

## Product

- [Product overview](https://creatorprivacykit.com/index.md): supported formats, local processing, C2PA vs. EXIF/XMP, and limits.
- [Live sanitizer](https://creatorprivacykit.com/): human-facing browser UI.
- [Telegram appeal draft tool](https://creatorprivacykit.com/telegram-ban-appeal): helps organize a concise support request; it does not guarantee reinstatement.

## Canonical guides

- [Instagram “AI Info”: what metadata can and can’t explain](https://creatorprivacykit.com/blog/how-to-remove-ai-info-label-instagram.md): Meta’s public AI-labeling approach, C2PA, clean exports, and the limits of metadata-only explanations.
- [Discord image privacy: what survives an upload?](https://creatorprivacykit.com/blog/discord-image-privacy-exif-metadata.md): compare a source file and downloaded attachment instead of relying on blanket EXIF claims.
- [Telegram photo vs. file: a metadata test you can reproduce](https://creatorprivacykit.com/blog/telegram-send-as-file-metadata-privacy.md): A/B test one source image through both delivery paths.
- [WhatsApp HD does not automatically mean “original file”](https://creatorprivacykit.com/blog/whatsapp-hd-photo-metadata-privacy.md): separate resolution, compression, and metadata; WhatsApp officially documents HD quality and document size limits, not a universal metadata-retention rule.
- [X / Twitter image metadata: public output is not backend proof](https://creatorprivacykit.com/blog/x-twitter-image-metadata-privacy.md): Twitter joined C2PA in 2021, but that fact alone does not establish current X ranking or telemetry behavior.
- [Xiaohongshu, AI labels, C2PA, and what we can actually prove](https://creatorprivacykit.com/blog/xiaohongshu-ai-label-c2pa-metadata-guide.md): a controlled-test approach without invented throttling, account-weight, or hidden-queue claims.
- [Telegram account restricted or phone number banned?](https://creatorprivacykit.com/blog/how-to-recover-banned-telegram-account-2026.md): official recovery routes including @SpamBot and Telegram’s support form, plus documented authorization errors.

## Canonical blog hub

- [Field Notes](https://creatorprivacykit.com/blog/index.md)

## Policies

- [Privacy policy](https://creatorprivacykit.com/privacy.md)
- [Terms of use](https://creatorprivacykit.com/terms.md)

## Machine-readable resources

- [Full site summary](https://creatorprivacykit.com/llms-full.txt)
- [XML sitemap](https://creatorprivacykit.com/sitemap.xml)

## Product limitations

CreatorPrivacyKit can inspect and change supported files before upload. It cannot prove what a private platform stores internally, remove every possible pixel-level watermark, or guarantee any platform ranking, label, moderation, or account-recovery result.