Why

The cloud/team interest template asks teams to describe workflows, retention, privacy, customer-data, and deployment constraints. That can include sensitive organizational details, so the template should point people to the Security Policy before they post sensitive details publicly.

Scope

Update .github/ISSUE_TEMPLATE/cloud_interest.yml with a short markdown note that links SECURITY.md and tells reporters to use the private security path before posting security-sensitive reports or private trace data. Keep the existing first PR recipe guidance.

Acceptance criteria

• .github/ISSUE_TEMPLATE/cloud_interest.yml links SECURITY.md.
• The template mentions security-sensitive reports or changes and private trace data.
• Add or update a metadata test so this guidance does not regress.
• Do not add any request for stars, upvotes, reposts, or promotional engagement.

Suggested verification

uv run --python 3.11 --extra dev pytest -q tests/test_metadata.py -k cloud_interest
uv run --python 3.11 --extra dev pytest -q tests/test_metadata.py
uv run --python 3.11 --extra dev pytest -q
git diff --check