openclaw - 💡(How to fix) Fix Please review the restriction on person-related search requests

Hi Peter,

I would like to raise a concrete policy concern that feels unnecessarily restrictive in practice.

Currently, OpenClaw appears to block person-related search requests very broadly, even in cases where the information may be publicly available and the request is harmless and legitimate. This creates situations where the system becomes less useful than other assistants, even when there is no obvious privacy or safety risk.

Example: If I ask for the birthday or date of birth of a public person, or a similar piece of information that may already be publicly available online, the request is rejected categorically instead of checking whether it is a legitimate public-information lookup.

My request:

• The rule should be made more precise.
• Public, non-sensitive person-related information should not be blocked categorically.
• Instead of a general refusal, OpenClaw should apply a risk-based distinction between sensitive private data and publicly available, low-risk information.

Why this matters:

• The current rule unnecessarily reduces usefulness.
• It makes OpenClaw stricter than other assistant systems in some cases without a clear benefit.
• A more nuanced policy would make the platform more helpful without abandoning privacy or safety goals.

If useful, I am happy to help formulate a more concrete policy alternative or examples of allowed vs. disallowed requests.

Best regards