Data Deletion and Access Revocation

Calm Glow Finds Content Operations is the owner-operated workflow for the Calm Glow Finds Pinterest Business account. AutoPoster OS is its internal content-workflow tool.

Monitored support address: [email protected]

What You May Request

A verified request may cover access, correction, deletion, or future Pinterest connection revocation for:

• campaign, content, board-selection, compliance, link-check, approval, and publishing-workflow records;
• manually captured public Pin URLs, posting status, and manually entered performance metrics;
• support, privacy, verification, and deletion-request correspondence; and
• any future locally held Pinterest connection or token material, if a separately reviewed Trial activation ever stores it.

What To Include

• The request type: access, correction, deletion, disconnect, or revocation
• Enough non-sensitive context to identify the affected record
• A public Pinterest profile URL or public Pin URL only when relevant

Do not send a password, cookie, private account ID, API key, client secret, OAuth token, authorization code, or raw API payload. Identity or ownership verification may be requested to prevent unauthorized changes.

Timing and Retention

After identity or account ownership is verified, a deletion request will be completed within 30 days. Pinterest OAuth is not active today and no Pinterest token is stored in the current build. If future reviewed Trial activation stores token material, disconnect or Pinterest-side revocation will block further API use immediately and locally held token material will be deleted within 24 hours.

Raw Pinterest API payloads are not retained. Redacted Pinterest integration audit metadata may be retained for up to 90 days only when needed for security, compliance, incident review, or duplicate prevention. A narrow record may be retained longer only when required by law; it will remain restricted and will not be used for content operations.

Data Outside AutoPoster OS

Deleting AutoPoster OS records does not remove public Pins or data controlled by Pinterest, a retailer, an affiliate destination, an email provider, or the selected hosting provider. Those services must be contacted or managed under their own controls and policies.

Current and Future Service Boundary

Publishing is manual today. Pinterest API publishing, OAuth, automatic analytics, unattended Pinterest/API publishing scheduling, and batch operations are not live. Internal content-calendar dates do not trigger Pinterest publishing. After Trial approval and a separate reviewed activation, the first API test would be limited to the owner's own account and one human-approved Sandbox Pin at a time.