One connection. Every action visible.

The current released social scheduler sends customer-approved Pinterest posts to Metricool. A site stores its Metricool user/brand configuration and a selected Pinterest Board identifier. The scheduling service calls Metricool to create, inspect, reconcile, or cancel scheduled posts and to retrieve available Pinterest analytics for that configured brand.

When White Label for Integrators is enabled by the operator, Autopubly can open a short-lived, single-use Metricool connection session restricted to the Pinterest network. Without that commercial configuration, customers use their own authorized Metricool API configuration.

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 general users’ Boards and Pins. Current records are limited to the customer-configured Metricool brand, selected Board, scheduled Pin metadata and status, and analytics returned for that connection.

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

Autopubly plans a direct OAuth-based Pinterest connection for customers who manage their own accounts. It will be enabled only after provider approval and implementation of a user-facing authorization flow, minimum necessary scopes, server-side token protection, disconnect handling, deletion handling, and a demonstrable sandbox-to-production publishing flow.

Until then, public product copy and app-review materials must describe direct Pinterest access as planned, not connected or available. A Standard-access application must not be submitted using only a mockup or the Metricool connection as evidence of direct API functionality.

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.