Publish + analytics + ads + comments scoped API keys that exclude private DM/message access

Hi team,

(It's been confirmed there's no current mechanism to exclude inbox data at the account, profile, or key level, and suggested I file this here.)

The request: an API key scope that includes everything Zernio offers — publishing, scheduling, analytics, ads/boosting, and public engagement (comments, reviews, mentions) — except private messages/DMs specifically.

One clarification on scope, Zernio treated "DMs/comments/history" as one bucket ("Inbox data"): I'm not asking to exclude comments, reviews, or mentions — those are public content, and I'd still want API access to them for engagement features. The specific thing I want excludable is private, 1:1-style conversations (DMs) — the messages endpoints, not the comments endpoints. If Inbox is currently modeled as a single resource internally, splitting "messages" out as its own resource type (separate from "comments") is really the core of this request.

Why this matters: I'm building a multi-tenant platform where each of my customers connects their own social accounts. My team-level API key currently has standing access to every connected customer's private DMs by default, whether or not my product ever touches that data. That's a real privacy exposure for a service that's supposed to only be publishing and reporting on their behalf — and it's the one gap keeping me from using Zernio more broadly across my product (including the ads/boosting features, which I'd otherwise like to build on Zernio).

Concretely, either of these would solve it:

- A resource-type dimension on scoped API keys, e.g. `resources: ["posts", "comments", "ads", "analytics"]` that simply omits (private) `"messages"`

- An account/profile-level toggle to disable inbox message ingestion specifically, while leaving comments, reviews, and mentions untouched

Happy to give more detail on the use case if useful. Thanks for considering it.