Meta, Instagram, Facebook and Threads Permissions
Ai social poster is a preview/beta, safety-gated product. This page explains intended Meta permission use for reviewer and customer clarity. Ai social poster is not affiliated with, endorsed by or sponsored by Meta, Instagram, Facebook or Threads.
What Ai social poster does
Ai social poster helps customers prepare AI-assisted social posts, review platform-specific previews and manage approval workflows for customer-owned social accounts. Current Meta-related surfaces are preview/sandbox-first and do not enable live publishing without completed provider review, customer consent and internal safety gates.
Why permissions are requested
- Show customer-owned Instagram, Facebook Page or Threads destinations inside the workspace.
- Prepare draft captions, media previews and platform payload previews for customer review.
- Validate that a selected destination is eligible before any future publishing flow can proceed.
- Support disconnect, audit and data deletion workflows for connected destinations.
What data may be accessed
- Connected account or Page identifiers, display names, handles and profile metadata needed to show destinations.
- Post, media or container metadata needed to prepare previews when the customer initiates a workflow.
- Permission and connection status needed to explain whether an account is ready, blocked or disconnected.
What data is not accessed
- Ai social poster does not ask customers for Meta, Instagram, Facebook or Threads passwords.
- Ai social poster does not sell connected account data.
- Ai social poster does not access private messages, ad accounts or unrelated personal data for this docs pack.
- Ai social poster does not publish without customer approval and enabled safety gates.
How users connect accounts
Customers choose a Meta connection option from their Ai social poster workspace, review the requested permissions on the provider consent screen and connect only accounts or Pages they own or administer. In the current preview state, live OAuth activation remains blocked until owner-approved provider review work is complete.
How users disconnect accounts
Customers can remove a connected destination from the workspace when disconnect controls are enabled. They may also revoke app access from their Meta account settings. Disconnecting stops new preview or publishing workflows for that destination.
Publishing approval and safety gates
Live publishing remains blocked in this preview documentation state. Future Meta publishing requires provider review completion, a customer-selected destination, customer approval or explicitly configured automation rules, policy checks and internal safety flags that prevent live calls when review or consent is missing.