Loop security model and user permissions

Summary

Goal: Understand Loop's permission model and data access restrictions for security planning.

Features: Loop session-based permissions, project access control, user-level data restrictions.

Applicable To

Plans: Any

Deployments: Any

Permission Model

Session-based access

Loop operates as an extension of your user session with identical access restrictions.

Project data access

Loop cannot query or access any project data that your user account doesn't have permission to view.

No elevated permissions

Loop has no additional permissions beyond what's available through the UI or API for your user.

Tool and query restrictions

All Loop tools and queries are subject to the same project-level access controls as other Braintrust interfaces.

Data Privacy for Self-Hosted

Model provider communication

Loop sends conversation data directly to your configured model provider using your API keys.

Logging

Loop exchanges are not logged by Braintrust for self-hosted deployments.