Legal
Pinterest Publishing Automation Privacy Policy
Shinkarenko Content Publisher publishes scheduled Pins to a Pinterest board chosen by the account owner. It keeps the access token needed to do that and does not read, collect or sell the data of Pinterest users.
Who is responsible
Sergey Shinkarenko, a self-employed developer registered in the Czech Republic (IČO 24945277), Kubelíkova 1258/43, 130 00 Praha 3 – Žižkov, Czech Republic, is responsible for the processing of personal data (data controller).
Privacy requests and questions: sergey [at] shinkarenko.eu
What the app does
The app is an n8n workflow that runs on a schedule on a private server. It takes the next prepared post from a content queue and creates one Pin on one configured board. It is not a public service: nobody signs up for it, and it has no website or mobile interface of its own. It only works with a Pinterest account whose owner has authorised it through Pinterest.
Data the app handles
- Pinterest access and refresh tokens, received when the account owner authorises the app. They are stored encrypted in the credential store of n8n and are used only to call the Pinterest API.
- The ID of the board that receives the Pins, set in the workflow configuration.
- The content of each Pin: title, description, image alt text, link and image. This content is prepared by the account owner, and it is public on Pinterest once published.
Data the app does not touch
The app requests only the permissions needed to publish Pins to the chosen board. It does not read followers, messages, other people’s Pins, analytics or advertising data, and it does not show Pinterest content to anyone. It does not sell data, share it for advertising or use it to train AI models.
Where data goes
- Pinterest receives the content of each Pin. Pinterest processes it under its own privacy policy.
- The content queue records whether each post was published, and the error message if it failed.
- A private Telegram chat of the people running the workflow receives the post number and term after each run, or the error message if it failed. Telegram processes these messages under its own privacy policy.
- The n8n server keeps run logs, which can contain the content of a Pin, for troubleshooting. They are deleted after two months.
How long data is kept and how to remove it
Tokens are kept while the integration is in use, and run logs for two months. The account owner can withdraw access at any time in the Pinterest account settings; the app then can no longer publish. On request, I delete the stored tokens and the workflow configuration. Published Pins stay on Pinterest until the account owner deletes them there.
Your rights and contact
Where data protection law such as the GDPR applies, you can ask for access to, correction or deletion of your personal data, and you can lodge a complaint with a data protection authority.
Privacy requests and questions: sergey [at] shinkarenko.eu
This app is independent and is not affiliated with or endorsed by Pinterest, Inc.
Changes
This policy will be updated before the app starts processing data differently, with a new date above.