Privacy — MediaChecker SafeGuard
Last updated: September 20, 2026 (PT)
Operator: ICBM Magazine / MediaChecker, British Columbia, Canada
Product: MediaChecker SafeGuard reality-verification browser extension beta
Privacy URL: https://mediachecker.ca/privacy
Summary
MediaChecker SafeGuard helps you send selected page media to the MediaChecker SafeGuard API for ephemeral forensic analysis. The product is a closed beta. This page is the site-facing privacy policy for the beta and should remain available at the stable URL above.
What the extension accesses
When you choose a verification action, the extension may:
- Read the active tab URL and page context needed to identify the selected media.
- Capture or receive a representation of that media, often as an in-memory image or data URL.
- Store local preferences in Chrome storage, such as the selected API environment or base URL.
The extension does not require an account login for basic beta use.
What is sent to the API
When you request analysis, the extension may send a forensic payload to the configured API base URL. The default hosted beta endpoint for this package is https://api.mediachecker.ca. Payloads can include:
- Page and media URL metadata and capture context.
- Heuristic observation fields.
- An optional base64 image (data_url) so the server can run pixel-level checks such as ELA-style analysis.
For development, you can switch the environment selector to a local backend such as http://127.0.0.1:8000, so traffic stays on your machine.
Media retention in the beta
MediaChecker does not permanently retain uploaded media as a beta product feature. Image bytes are designed to be processed ephemerally in memory for the duration of a request and are not offered as a user media library or long-term media archive.
Operational logs should avoid storing full data_url payloads.
Transient infrastructure caches or crash dumps outside our control may still exist at a hosting provider layer; the application path is designed not to keep media files on disk for the beta.
If optional anchoring or receipt features are enabled, they store verification receipts or hashes—not a browsable copy of your original media gallery.
Local storage
Extension settings, such as the selected API environment, may be stored using Chrome storage. Clearing the extension or Chrome site data removes those preferences.
Third parties and service providers
- Hosting: The API may run on a cloud PaaS, such as Railway or Render, under a MediaChecker-controlled project.
- Chrome Web Store: Google processes developer, account, and install telemetry under Google's policies.
- We do not sell personal information.
Your choices and responsibilities
- Do not run SELECT MEDIA or verification on content you are not allowed to process.
- Use the Local environment for offline or development testing where appropriate.
- Uninstall the extension to stop further client-side capture.
- Contact us through the channels published on mediachecker.ca with questions about beta data handling.
Children
This product is not directed at children under 13, or under 16 where required by law. Do not use the beta to process children's personal media.
Changes
We may update this policy as the beta evolves. The Chrome Web Store listing and this site privacy URL should point to the current version. The last-updated date above will change when the policy changes.