Privacy, without the fog.

For supported self-hosted sites, you may authorize Autopubly on your own WordPress website instead of manually copying an Application Password. Your normal WordPress login stays on that website. WordPress creates a separate, revocable Application Password and returns it to Autopubly over HTTPS. We verify the connection and store the installation address, WordPress username and encrypted Application Password server-side to perform your requested article, media and scheduling operations. Approval requests are single-use and expire after ten minutes.

WordPress Application Passwords inherit the permissions of the authorizing user; they are not limited OAuth scopes. Use a dedicated publishing user with only the capabilities needed for your workflow. Connection credentials are not sent to AI providers. Connecting does not itself publish an article or change a theme.

You can stop access immediately by revoking the Autopubly Application Password in WordPress under Users → Profile → Application Passwords. Contact autopubly@gmail.com to request verified removal of locally stored connection credentials. Removing a connection does not delete articles or media already on your website. If an approval fails after WordPress creates a password, revoke that unused password before reconnecting. Theme installation and WordPress.com OAuth are separate capabilities and are not granted by this publishing connection.

Nadir Dahhak operates Autopubly and is responsible for personal information processed through the public website, accounts, customer workspace, billing, support, and publishing controls described here.

This policy does not cover information a connected provider processes independently under its own policy.

• Account and security data: email, username, password hash, sessions, activation and plan state, human-verification results, audit events, coarse country information, keyed device/IP identifiers, and encrypted IP addresses.
• Publishing data: sites, article content, generated media, schedules, destination URLs, job state, failures, and usage/cost records.
• Pinterest connection data: encrypted OAuth access and refresh tokens, the authenticated account identifier/username, granted scopes, the customer-selected Board identifier/name, scheduled Pin metadata, provider identifiers, publishing state, and available own-account reporting. Legacy customer-configured previous social provider records may remain for workspaces that still use that route.
• Requests and support: the contact details, account identifier, and message supplied with a privacy or support request.

Autopubly connects to Pinterest through Pinterest’s official OAuth authorization screen. Autopubly receives an authorization code, exchanges it server-to-server, encrypts the resulting tokens at rest, reads only the authenticated customer’s own Boards, and publishes only the individually approved Pins scheduled for the selected Board.

Autopubly never receives the customer’s Pinterest password. Customers can disconnect a site in Autopubly and can also revoke access in Pinterest’s connected-app settings. Historical provider records can be removed through a verified privacy request.

Information is used to authenticate customers, operate subscriptions, generate requested content, protect isolated workspaces, connect sites, show provider status, and carry out customer-selected publishing actions.

For social publishing, connecting an account does not itself publish anything. Every Pin remains a draft until the customer inspects its exact image, link and Board, reviews or edits its title, copy and schedule, and presses its individual Approve & Schedule action. The server then validates and submits only that approved Pin.

The owner-only Pinterest sandbox panel in Sites is a separate test connection. It performs OAuth on Pinterest, reads the authorized account and its own sandbox Boards, and creates only the individually reviewed test Pin. It does not change a customer's production connection or publishing queue. The selected article, image and destination link come from the owner's workspace; an AI-assisted image is disclosed to Pinterest.

Sandbox access tokens, account labels, selected Board and Pin identifiers, and response details are held only in server-process memory for this test session, with a one-hour session limit and expiry cleanup every minute. They are not written to the application database or its backups. Disconnecting sandbox removes the local test session; it does not revoke the application at Pinterest or delete the test Pin. Access can also be revoked in Pinterest's connected-app settings. An operator may separately record the review flow for Pinterest's application review, without displaying tokens or passwords.

AI providers may process customer-requested source material and editorial instructions to create article or social copy. Autopubly does not send Pinterest account data, Board records, Pin performance data, integration or OAuth credentials, or provider access tokens to AI providers. Autopubly does not use that connected-account data to train models.

Generated copy may later be reviewed and selected by the customer for publishing, but generation occurs before and separately from the provider publishing action.

Autopubly does not ask for or store Pinterest passwords, session cookies, or private messages. It does not automate a consumer browser, scrape profiles, follow people, generate engagement, manage ads, or read other Pinners’ Boards and Pins. Direct provider access is limited to the authenticated customer’s own account, own Boards, selected destination Board, and approved publishing actions.

Information is shared only as needed for requested functionality: with Pinterest for customer-authorized Board access and Pin publishing; the customer's WordPress site for website publishing; Google when the customer chooses Google sign-in; configured AI providers for requested generation subject to the boundary above; and infrastructure or professional providers needed to host, secure, support, or lawfully operate the service. Historical third-party connection records may be retained until verified cleanup.

When an available checkout is used, the payment provider identified there processes payment information under its own privacy notice. Autopubly handles account, plan, billing-status and transaction-reference information needed to administer access and support. Existing Stripe integration or transaction records do not mean Stripe checkout is available to every customer. Lemon Squeezy is not represented as an approved or active payment provider. Creating an account does not itself authorize a charge.

Autopubly does not sell connected Pinterest data or share one customer’s publishing configuration, analytics, credentials, or content with another customer.

Encrypted IP addresses are automatically removed after the configured IP_ADDRESS_RETENTION_DAYS period, which defaults to 30 days. Keyed security identifiers and audit records may remain longer when needed to prevent abuse or resolve security events.

Account, publishing, provider-configuration, schedule, and analytics records remain while needed to operate the account and until they are changed, removed after a verified request, or retained for a documented legal, fraud-prevention, billing, security, or dispute purpose. Article-generation and billing records may be checked to verify refund eligibility. Access-restricted database backups are created daily and expire through a rolling 30-day retention cycle. Information removed from active systems may remain in a protected backup until that backup expires.

Autopubly requests only the minimum Pinterest scopes needed for Board selection, Pin publishing, and own-account status. OAuth tokens are protected server-side and removed from active storage after disconnection or account deletion, subject to the protected backup rotation and legally required records described above.

The public request form creates a request for manual review; submitting it does not instantly erase records or revoke access at a third party. After identity and authority are verified, a connection-only cleanup cancels pending local social jobs, clears the site’s provider and Board credentials/configuration, and removes related Pin schedule, status, and analytics records from active Autopubly systems, subject to limited records that must lawfully be retained.

A connection-only cleanup preserves articles, editorial drafts, and marketing media because they may also belong to the customer’s WordPress workflow. Those are removed only as part of a verified full-account deletion request. Autopubly marks local cleanup separately and does not claim remote revocation is complete until the customer or operator confirms revocation in Pinterest settings or the settings of a previously connected provider. Published Pins remain at Pinterest until the customer removes them there.

Autopubly is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child supplied personal information, contact autopubly@gmail.com.

Depending on applicable law, a customer may request access, correction, export, restriction, objection, disconnection, or deletion. Autopubly verifies requests to protect the account. Contact autopubly@gmail.com or use the public request form.

General product questions can be sent to autopubly@gmail.com.

If you install Autopubly Connector, you can request theme installation, activation and restoration from your workspace. We process your connected site address, active and previous theme names, installed Autopubly editions and an account-scoped record of requested and confirmed or unconfirmed theme operations. Your existing encrypted WordPress connection is used server-side; it is not included in theme downloads.

On your installation request, the connector downloads a checksum-verified package from app.autopubly.com. That request exposes ordinary connection information, such as your server IP address, to our hosting infrastructure. The connector and supplied themes do not add background analytics or visitor tracking. Each live theme change requires your separate confirmation and WordPress administrator permissions. Deactivate or remove the connector to stop its theme-management endpoints; revoke the Application Password in WordPress to revoke the publishing connection as well.