Why we built official ways to connect Plaud to your other tools, and why we caution against anything that asks for your password.
Plaud is built to do more than capture a conversation. People connect it to their workflows, their own AI setups, and tools we haven't built yet, and we want to support that. We also want to be clear about one request worth treating carefully: any tool that asks for your Plaud login, password, or session token. This blog explains why that request carries real risk, and the official ways to extend Plaud without it.
Why account access is different here
You can change a leaked password. You can cancel a leaked card. You can't change your voice. A leaked password can be reset; an exposed recording cannot. That's why the access that protects your recordings deserves more care than almost anything else in your account, and why it matters who you hand that access to.
What sharing your credentials means
When you give an outside tool your Plaud credentials, you hand it a master key to your entire account. It can use that key at any time, store it on servers you'll never see, or share it with the services it depends on. Even well-intentioned tools get breached. And when your credentials are exposed, you're relying on an operator under no obligation to meet a security standard, to notify you in the event of a data leak, or in many cases, to be reachable at all.
A tool you connect this way also moves your data through infrastructure you didn't choose. Your recordings may pass through servers and AI providers you never reviewed, under privacy terms you never saw.
If you want to do more, there's an official path
You don't need to surrender your credentials to extend Plaud. We've built official, secure ways to connect:
- Plaud MCP connects Plaud to outside tools through OAuth. You authorize access on Plaud's own screen, your password and token never enter anyone else's software, and you can revoke that access from your account at any time.
- Plaud Developer Platform provides the APIs and SDKs to build on Plaud directly.
Even with OAuth, two responsibilities stay with you. Connect only the tools you trust, and review what you're granting before you approve it. OAuth protects your password. It doesn't decide who you let in.
What we commit to
Independently audited security and privacy (SOC 2 Type II, ISO 27001, GDPR, HIPAA). Breach notification within the timelines the law requires. A support team you can reach. And full control to export, delete, and manage your recordings, which remain yours. You can review our practices at our Trust Center: plaud.ai/pages/trust
Before you connect anything
If you want to do more with Plaud, start with Plaud MCP or the Developer Platform. And if a tool ever asks for your Plaud login and you're unsure about it, write to us at support@plaud.ai before you proceed. We'll help you work through it.
