Privacy Policy
Last updated: August 10, 2026.
1. Scope and contact
Chris En Camino is a personal, non-public publishing workflow operated by one person for that person’s own Pinterest account. For privacy, access, withdrawal or deletion questions, contact hola@chrisencamino.com.
2. Pinterest data the workflow may process
The installed Postiz provider is currently configured to request the Pinterest scopes boards:read, boards:write, pins:read, pins:write and user_accounts:read. Before activation, this set must be verified and reduced to the permissions needed for the reviewed workflow. If the connection is then enabled, OAuth may return an access token, a refresh token where issued, token expiry, and Pinterest account profile data: account identifier, username and profile image.
The Pinterest API may also return up to 250 board identifiers and names so the operator can choose a board. The workflow may process that selected board, Pin content supplied by the operator, the intended publication time, and delivery or status records needed to operate that Pin.
The workflow does not collect or use a Pinterest password or a Pinterest session cookie.
3. Purpose and operator control
The data is used only to prepare and carry out publication to the operator’s own Pinterest account through the selected workflow. Each Pin is individually selected and approved by the operator before Postiz carries it out at the chosen time. The workflow does not autonomously select content, recycle content, or take bulk actions.
The workflow does not sell data, use it for advertising targeting, scrape Pinterest, or train AI models.
4. Service providers and storage
The workflow uses a self-hosted Postiz installation and the Pinterest API to carry out the approved Pin. Database backups are kept in Cloudflare R2 storage in the EU. Backup retention may keep a copy for up to 185 days.
5. Withdrawal and data deletion
To request deletion of data held by this workflow, contact hola@chrisencamino.com and identify the connected Pinterest account. You can also revoke the relevant Pinterest app authorization from your Pinterest settings.
Live operational data and backup data follow different procedures. Backup copies are not individually edited; they expire under the backup retention schedule. If a backup is restored for recovery, an outstanding deletion request must be reconciled again in the restored environment.
6. Pinterest activation gate
The Pinterest connection is not activated by this policy alone. Before Pinterest API action is enabled, the configured scope set must be reduced to permissions justified by the reviewed workflow, and any persistence of OAuth-returned profile or board data against Pinterest’s no-storage rule, the live deletion and backup-reconciliation procedure, and individual-choice timing must be verified. Until then, this workflow must not execute Pinterest API actions.
7. Pinterest policies
This workflow is intended to operate consistently with the Pinterest Privacy Policy and the Pinterest Developer & API Terms.
8. Changes
This policy will be updated before a material change to the Pinterest data flow, storage, retention or activation conditions described above.