How emberdesk handles your Firestore credentials

You're connecting a tool to your production Firestore. Before you do, you should know exactly what happens under the hood: who holds what, what we can access, and how to walk away if you change your mind. This isn't a legal page. It's a plain-language breakdown of how Emberdesk works, written for developers who read code and ask hard questions. Our trust model Every tool that connects to your cloud resources creates a trust relationship. Here's ours, stated plainly: Party What they hold You Your Google account, your GCP projects, your Firestore data. You control what you connect and when you disconnect. Emberdesk A Firebase session to identify you. An encrypted refresh token to call Google APIs on your behalf, limited to the scopes you approved. Google Issues and enforces tokens. Controls the consent screen. Respects revocation. If you use our app , you're trusting us the way you trust any OAuth-integrated SaaS product; we hold an encrypted credential that lets us act within the scopes