Pending local social jobs are cancelled; Pinterest OAuth tokens, connection configuration and selected Board ID/name are cleared; related Pin schedule, status, remote-ID, and analytics records are removed from active Autopubly systems. Legacy historical integration credentials are included where present.
Disconnect. Delete. Verify.
Use these steps to stop future provider activity and request removal of Autopubly account or connection data. Requests are verified to prevent someone else deleting your workspace.
01Stop provider access
- Use the Pinterest disconnect control for the affected site in Autopubly to remove its active connection and selected Board.
- Sign in to Pinterest and revoke Autopubly in the account’s connected-app settings to stop provider-side authorization.
- Only if you previously configured a legacy third-party connection, revoke that authorization in previous social provider and remove or rotate the associated credentials as well.
- Keep the provider confirmation so remote revocation can be distinguished from Autopubly’s local cleanup.
Submitting a deletion request does not automatically revoke authorization at a remote provider. Disconnecting or revoking access does not remove Pins that were already published. Follow the verified cleanup steps below to request removal of stored records.
02Submit a request
- Open the Privacy Request Center.
- Select Clean up my local Pinterest / previous social provider connection data or Delete my Autopubly account and associated data.
- Enter the account email and, if available, its username or account identifier.
- Complete the human-verification challenge and submit.
If the form is unavailable, email autopubly@gmail.com from the address associated with the account.
03Verification
The operator may ask you to confirm control of the account email or provide information already associated with the workspace. Never send a Pinterest password, previous social provider password, access token, application password, or payment-card number in a deletion request.
04Records in scope
Account profile, active sessions, sites, editorial content and media, schedules, connection records, and other personal data associated with the verified workspace are included.
Articles, editorial drafts, and marketing media remain after a connection-only cleanup because they can also serve the customer’s WordPress workflow. Limited billing, security, fraud-prevention, legal, or dispute records may be retained when required. Where practical, account references are removed or pseudonymized. Backup copies leave service according to the operator’s documented production backup cycle.
05What remains elsewhere
Deleting Autopubly records does not delete Pins already published to Pinterest, posts at previous social provider, articles on WordPress, invoices at Stripe, or information another provider must retain. Manage those records through the provider that holds them.
06Contact
Privacy and deletion: autopubly@gmail.com
General support: autopubly@gmail.com