Security & privacy
You can see whether the work got better. Site changes run against gated tests and a checklist before a person signs off. This page lists only controls you can check. Each one names the file or test it comes from, in plain text, because our code repository is private.
What our tools do by default
- Dry-run first. Our publishing tools start in dry-run mode. DRY_RUN=true and PUBLISH_MODE=dry_run are the defaults, and any publish or deploy path has to check them first. (source: presence_bot/config.py, .env.example; test: tests/test_config_dry_run.py)
- A Board gate before anything goes live. A live site build needs DRY_RUN=false, PUBLISH_MODE=live and BOARD_UNLOCK=LIVE all set. Agents never set BOARD_UNLOCK=LIVE. (source: site-builder/config.py, SECURITY.md; test: tests/test_dry_run_badge.py)
- No agent spend. No agent may spend real money or authorize paid services. (source: brand-system/corporate-facts.json, safetyPillars; SECURITY.md)
- No automatic replies. Social channels don't respond automatically to inbound mentions or messages. Suggested replies are saved as drafts for a person to review. (source: brand-system/corporate-facts.json, safetyPillars; presence_bot/reply_suggester.py; test: tests/test_reply_suggester.py)
- No requests to other sites. The pages we build load their scripts, styles, fonts, images and video from this site only. (source: site-builder/templates/layout.html; test: tests/test_tt4_trust.py)
Privacy
MeltingFace runs no analytics or tracking scripts on this site and sets no cookies. Our host, Cloudflare, processes standard request data such as IP addresses to deliver and protect the site. We don't sell personal data. Questions: privacy@meltingface.io.
The full text is in our Privacy Policy.
Report a problem
Email privacy@meltingface.io or hello@meltingface.io. Please don't open a public GitHub issue for secrets or unreleased vulnerabilities. (source: SECURITY.md)