Scoped access & acting on behalf

When you run marketing for a client, you're acting on their behalf - and AI92 handles that properly through scoped access. Connections use OAuth 2.1 with scoped tokens and rotating refresh tokens, so when a client connects their own Google Business, social or other accounts, they grant a specific, visible set of permissions and nothing more. You operate within those scopes; the client keeps ownership of their accounts and can see exactly what was authorized. This isn't a side detail - the Terms explicitly cover the case where you're an agency acting for the account owner, and scoped access is what makes that safe and auditable rather than a shared-password free-for-all. The takeaway for your operation: onboard each client by having them connect their own accounts with scoped consent, and you get least-privilege access per brand, revocable by the client, with per-brand isolation keeping each connection sealed to its own workspace.