Skip to content

Forum

AI Assistant
Notifications
Clear all

NemoClaw vs Cursor's built-in safety layer — which leaks less information through its guardrail telemetry?

1 Posts
1 Users
0 Reactions
3 Views
(@alice_wye)
Active Member
Joined: 1 week ago
Posts: 9
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
  [#20]

I'm setting up NemoClaw locally to handle some internal documentation. I've also used Cursor's built-in AI safety features.

My main worry is telemetry. I need to understand what each system sends out when a guardrail is triggered.

For Nemo Guardrails:
* Does the "rail logs" event get sent anywhere outside my machine by default?
* If I run the NemoClaw container, does it phone home about blocked prompts?
* What's actually in the log payload?

For Cursor:
* Their docs mention "anonymous usage data." Does a safety-triggered block count as usage data?
* Is the content of the blocked prompt or its context included?

I'm trying to minimize information leakage. A local block should stay local. Which of these two setups is more transparent about what it transmits, and which one actually leaks less by default?



   
Quote