THE CURATED FIND PIN PUBLISHER

Privacy Policy

Effective date: 7 November 2026 · Last updated: 7 November 2026

This Privacy Policy explains how the independent developer operating The Curated Find Pin Publisher ("the application", "I", "me" or "the operator") handles information when using the application for personal publishing to the operator's own Pinterest account.

1. Who operates this project

The Curated Find Pin Publisher is an independently developed personal-use project operated by the GitHub user RomanGOW. "The Curated Find" is the project name used to identify this application; this statement does not represent that a registered company exists.

Privacy enquiries: [ADD YOUR DEDICATED GMAIL ADDRESS BEFORE PUBLISHING].

2. Scope and intended use

The application is intended for the operator's own Pinterest account. It is not currently offered to other users as a hosted service. It helps the operator prepare original Pin content and submit individually selected Pins to Pinterest using Pinterest's official API.

3. Information the application may handle

Depending on the features used, the application may handle:

The application does not request the operator's Pinterest password or session cookies.

4. Where information is stored

Pinterest OAuth credentials and tokens used by this personal application are intended to be stored locally on the operator's computer. This project does not operate an application server for storing Pinterest credentials or account data.

Pin drafts and source media are handled on the operator's device as part of the local workflow. The operator is responsible for securing the computer, its user account, backups and any local application files.

The public website is hosted by GitHub Pages. GitHub states that it logs visitors' IP addresses for security purposes. GitHub may therefore process technical visitor information when this website is accessed. See the GitHub Privacy Statement.

5. How information is used

Information is used only to operate the personal publishing workflow, including authorising API access, retrieving information needed to select a board, preparing a Pin request, publishing a Pin selected by the operator, and troubleshooting failures.

When a Pin is submitted, the relevant content and request data are sent to Pinterest. Pinterest processes that information under its own terms and privacy policy. The application does not control Pinterest's subsequent handling of published content.

6. Pinterest API requirements and data handling

The application is intended to use Pinterest's official API and OAuth authorisation. It is not intended to scrape Pinterest, collect Pinterest passwords or session cookies, sell or share Pinterest account information, or automate follows, comments, messages or other engagement.

Pinterest's Developer Guidelines restrict storage of information accessed through Pinterest Materials, subject to the exceptions stated in those guidelines. The operator must use API-returned information only as permitted, request information when needed, and avoid retaining Pinterest API data except where Pinterest expressly permits it. See Pinterest Developer Guidelines.

7. Sharing and disclosure

The operator does not sell or rent Pinterest account information and does not share it with advertising networks or data brokers. Information is sent to Pinterest when necessary to make the API request the operator has chosen. The website host, GitHub, may process website visitor technical data as described above.

8. Retention and deletion

Local credentials, drafts and files remain on the operator's computer until the operator deletes them or the application removes them. The operator can revoke the application's access through Pinterest account settings and delete locally stored tokens. Revoking access may prevent further publishing until authorisation is completed again.

Information already submitted to Pinterest, including published Pins, is subject to Pinterest's systems and applicable Pinterest controls. Deleting local files does not automatically delete content already published to Pinterest.

9. Security

Credentials should be kept private and must not be committed to a public source-code repository, included in website files, or shared with other people. Local security depends in part on the operator's device and operating-system protections. No method of electronic storage or transmission can be guaranteed to be completely secure.

10. South African privacy considerations

This project is operated from South Africa. Where applicable, personal information will be handled in a manner intended to respect the Protection of Personal Information Act 4 of 2013 (POPIA). This notice describes the project's intended handling practices; it is not legal advice or a guarantee of compliance in every circumstance.

11. Children's information

This application is not designed for children and is not intended to collect children's personal information.

12. Changes to this policy

This policy may be updated if the application's functionality or information-handling practices change. The revised version will be published on this page with an updated effective date. The operator should review the policy before materially changing how the application handles information.

13. Contact

For privacy questions or requests, contact: https://github.com/RomanGOW.

This is a project-specific draft privacy notice, not legal advice. Replace the contact placeholder and verify every statement against the application's actual implementation before publishing or submitting it to Pinterest.