One connection. Every action visible.

The released connection uses Pinterest’s official OAuth 2 authorization-code flow and v5 API. The customer leaves Autopubly for Pinterest’s consent screen, authorizes the requested scopes, returns through a single-use callback, and selects one of their own Boards.

Autopubly stores tokens encrypted on the server and can prepare local Pin drafts for individual review. Public production Pin creation is held while this app has Pinterest Trial access. After Pinterest grants Standard access, the scheduler can release individually approved Pins through the official API at their scheduled time. No draft is represented as a public Pin before Pinterest confirms it.

1. The customer connects or configures the site and selects a Board they control.
2. Autopubly creates a draft with a Pin image, title, copy, destination, and proposed schedule. Copy or imagery may be AI-assisted from that customer’s own site content and instructions, and the review screen identifies AI assistance.
3. The draft remains visible in the Social queue; connection or generation alone does not publish it.
4. The customer opens that specific draft, inspects its exact image, destination and Board, and may edit its title, copy, and proposed schedule.
5. The customer presses that Pin’s individual Approve & Schedule action.
6. The server validates limits and submits only that individually approved Pin.

Autopubly does not treat account connection, article generation, page viewing, or approval of a different Pin as consent to publish.

Autopubly does not collect Pinterest passwords, session cookies, private messages, or payment information. It does not scrape profiles or access other Pinners’ Boards and Pins. Current direct records are limited to encrypted OAuth tokens, the authenticated customer account, granted scopes, own Boards needed for selection, the selected Board, and the metadata/status of that customer’s own scheduled Pins.

Pinterest account data, Board data, Pin performance data, historical integration credentials, and provider tokens are not sent to AI providers and are not used by Autopubly to train models.

A customer can disconnect Pinterest for a site in Autopubly, which removes the active encrypted token record and selected Board and cancels that site’s unpublished Pin drafts and schedules. Reconnecting does not reactivate those approvals; each new Pin requires fresh review. The customer can separately revoke Autopubly in Pinterest’s connected-app settings.

Verified access, export, correction, connection-cleanup, and account-deletion requests are available through the Privacy Request Center and the public data-deletion instructions.

Customers revoke current authorization in the relevant provider settings and submit a verified request for local cleanup. Autopubly cancels pending local social jobs, clears provider/Board configuration, and removes related Pin schedule, status, and analytics records while preserving articles and marketing media. The request form enters a manual review queue; it does not claim immediate deletion or automatic remote revocation. Provider-side revocation must be separately confirmed.