Privacy First

When to Activate

• User asks: "prevent emails", "remove personal data", "privacy check", "never use email"
• Before writing any new code, Cargo.toml, config, or documentation file
• During code review or quality gate checks
• When adding contact information to any file

Agent Workflow

1. Before Writing Any File

Before creating or editing any file, check for email patterns:

# Scan the file being edited for email patterns
grep -E '[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}' <file> || true

2. Replacement Rules

3. Rust-Specific Rules

Cargo.toml

# Bad
[package]
authors = ["Dominik Oswald <user@example.com>"]

# Good
[package]
authors = ["Dominik Oswald"]

README.md / CONTRIBUTING.md

# Bad
Contact: support@example.com

# Good
Report issues: https://github.com/owner/repo/issues

Rust source code

• Never hardcode email addresses in const, static, or fn bodies
• Use placeholder example.com domain only in #[cfg(test)] blocks
• Keep deny.toml and CI configs free of personal email addresses

4. Exceptions (Allowed)

The following are permitted and should NOT be flagged:

• Test data in tests/ or #[cfg(test)] using standard test domains:
  • example.com, example.org, test.com
• URLs in documentation pointing to external services
• Git history (cannot modify)
• Skill reference files with generic examples (for demonstration)

Quality Gate Integration

Add to scripts/quality-gates.sh or CI:

# Scan for email patterns (exclude test data and git)
EMAIL_PATTERN='[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}'
EXCLUDE_PATTERN='example\.com|example\.org|test\.com|\.git|node_modules|target'

# Check source files
if grep -rE "$EMAIL_PATTERN" \
  --include="*.rs" --include="*.toml" \
  --include="*.yaml" --include="*.json" --include="*.md" . \
  2>/dev/null | grep -vE "$EXCLUDE_PATTERN"; then
  echo "ERROR: Email address detected in codebase"
  exit 1
fi

Quick Reference

Never do:

• Add authors = ["Name <email>"] in Cargo.toml
• Write contact@example.com in any markdown
• Use real email addresses in examples
• Include personal emails in deny.toml or CI configs

Always do:

• Use GitHub Issues URLs for support
• Remove email from Cargo.toml authors field
• Use test domains (example.com) only in #[cfg(test)] blocks
• Link to SECURITY.md for vulnerability reporting

Rationalizations

Red Flags

• Email addresses in Cargo.toml authors field
• Personal emails in README.md or CONTRIBUTING.md
• Real emails in Rust source code (not in #[cfg(test)] blocks)