Trust and privacy
GDPR and data handling
Briedo is used in workflows that can involve personal data shared during early client intake. Teams evaluating Briedo often need a clear public summary of how the platform approaches GDPR-related responsibilities.
Summary
- Briedo is designed for professional workflows where privacy and access control matter.
- In many customer use cases, the customer acts as the controller and Briedo acts as the processor for intake data handled on the customer's behalf.
- Teams should review the public privacy, security, subprocessors, and DPA pages together rather than relying on a single summary page.
What data may be involved
- Account and workspace details for customer teams
- Client or prospect information submitted through intake workflows
- Briefing content, contextual notes, and supporting details shared during the conversation
- Operational and security-related metadata needed to provide the service
Practical GDPR topics
- Controller and processor role clarity
- Data subject rights and deletion requests
- Subprocessor visibility and infrastructure providers
- International transfers where relevant
- Security controls, access control, and data minimization
Limitations
- This page is an overview, not legal advice.
- Customers should review whether Briedo fits their own regulatory, contractual, and operational requirements.
- Where necessary, teams should request a DPA and review detailed legal documentation before production use.
Need a privacy or GDPR discussion?
Use the public legal pages as a starting point, then contact Briedo for detailed questions or DPA requests.