Ben Reilley Product Publisher

Privacy Policy

Operator: Ben Reilley · Last updated: November 11, 2026

1. Who operates this app

Ben Reilley operates Ben Reilley Product Publisher, a private business tool intended to manage only Ben's own Pinterest business account. It is not offered as a service for other people to connect their Pinterest accounts.

This policy covers the app's Pinterest integration and this privacy page. It does not replace Pinterest's own privacy policy or the policies of the services linked below.

2. What works now and what is planned

As of the update date, the Pinterest integration is not connected. No Pinterest API requests or Pin publishing operations are recorded in the local pipeline. Product publishing and promotional posting are disabled.

The app already contains code to read account details, check a board, inspect existing Pins, create a Pin and retrieve Pin analytics. These Pinterest functions have not been verified against a connected account. Public posting is planned only after the required account authorization, app access approval and checks are complete. Trial-only Pins will not be treated as public promotion.

A browser-based Pinterest authorization flow and automatic token refresh are not implemented. The current adapter expects an access token supplied by the operator. This policy describes both the current storage behavior and the data the implemented adapter would handle once connected.

3. Pinterest data the app would access

Account details: the Pinterest API's account response, such as account identifiers and profile information, to check the connection. The current connection check uses the response in memory and saves the connection result rather than the full profile.
Board details: the configured board's identifier, privacy setting and other fields returned by Pinterest. The app checks that the destination board is public before posting. It does not build a saved directory of all boards.
Pin details: identifiers, destination links and other returned Pin fields on the configured board, used to find an existing matching post and prevent duplicate posting. If enabled, the app would send Pinterest an original promotional image, title, description, alternative text, destination link and board identifier.
Pin analytics: impressions, outbound clicks, saves, reporting dates and any associated fields returned by Pinterest for posts confirmed by this app. These are used to understand promotion performance, not to identify individual viewers.

The current adapter does not request Pinterest passwords, direct messages, contact lists or individual viewer identities. It does not provide a Pinterest advertising, payment or customer-list feature. Public product links may include campaign tags to attribute visits to a promotion.

4. Credentials, local records and security limits

The app runs on the operator's Windows computer. The Pinterest adapter reads its access token from an environment variable or an operator-managed local secrets file. No Pinterest token is currently configured. The secrets directory is excluded from the project's Git tracking rules.

If a local secrets file is used, the token is stored as readable text. The app does not add encryption to that file, its JSON records or its SQLite database. Access depends on the computer's and storage system's permissions and protections; this policy does not claim that disk encryption or a particular backup protection has been verified.

The SQLite database stores jobs and their working data, request counters, timestamps, publication-attempt records and confirmed remote identifiers. Once a real post succeeds, a job can contain its Pin identifier, and publication records can contain that identifier too. The configured board identifier is stored in local configuration. Locally generated images, captions and listing links are saved as product assets.

Connection and status reports are saved locally as JSON and text. Requested Pinterest analytics responses would be saved in local metrics reports. Most raw account, board and Pin-list responses are used in memory rather than deliberately saved as complete responses.

Error records contain job identifiers, stage names, timestamps and error types or short reasons. The Pinterest request code records HTTP status failures rather than response bodies. Tokens are used in authorization headers and are not deliberately written to these app logs. This is a description of the implementation, not a guarantee that all possible failures or third-party software behavior are secret-free.

The Git ignore rules exclude secrets, runtime data and logs. Some summary documentation is tracked and can include connection status, job identifiers or public product information. Git ignore rules alone are not an access-control or encryption mechanism.

Pinterest: connection checks, board and Pin requests, planned promotional uploads and analytics requests go directly to Pinterest's API over HTTPS. Pinterest receives the access token for authentication, request details and ordinary network connection information. Public Pins and their linked content would be visible according to Pinterest's settings and rules.

Ollama, OpenAI and Tavily: the current Pinterest code does not send Pinterest API responses, access tokens or collected Pinterest analytics to Ollama, OpenAI or Tavily. It has no data path that feeds those Pinterest records into an AI model or the separate research scripts.

The broader product-research project separately sends configured research questions and selected public webpage URLs to Tavily for search and extraction. Separate scripts use local Ollama models to process research text. They are not wired to the Pinterest account, board, Pin or analytics responses. The Pinterest adapter contains no OpenAI API call. Having AI-related libraries installed does not by itself establish that Pinterest data is sent to them.

Product destinations: a promotional Pin can link to a Gumroad product. The current code does not send Pinterest account or analytics responses to Gumroad. A person who follows a product link interacts with Gumroad separately, including any campaign tags in that link.

The app has no feature for selling Pinterest data, sharing it with advertisers or supplying it as AI training data. If the implementation changes to send Pinterest data to another provider, this policy will need to be updated before that new use begins.

6. Retention and deletion

There is currently no automatic expiry, scheduled purge or fixed retention period for local credentials, job history, reports, analytics files or error logs. Records remain until the operator deletes them manually. Some current summary files are overwritten on later runs; job history and older artifacts can remain.

The app does not provide a self-service data-deletion screen or an automated erasure process. To request deletion of information held by the app, contact Ben using the privacy address below and identify the relevant account, Pin or record. Do not send passwords or access tokens.

Deletion is a manual process covering relevant credentials, saved reports, job and publication records, logs and any copies the operator holds. Deleting a local file or database record does not automatically erase any backup, Git history or other copy. No automatic backup-erasure process is implemented.

Removing local data or disconnecting the app does not delete a Pin already published on Pinterest, a product on Gumroad, or records held by those services. Existing Pins must be managed on Pinterest. This app does not currently implement Pin deletion.

7. Stopping or disconnecting access

The operator can stop new pipeline requests using the local STOP-file control or by disabling the Windows scheduled task. A request already sent may still complete. Disabling publication alone does not prevent authorized read requests.

To disconnect completely, revoke the app's authorization through Pinterest's available account or app-management controls and remove any local Pinterest token from the app's environment and secrets file. The app has no built-in disconnect or token-revocation button. Disconnecting does not itself remove previously saved local data; deletion is separate.

Pinterest's connected-app help explains where to review connected apps. If the required revocation control is not available, contact Pinterest support.

8. Visitors to this privacy page

This HTML page contains no contact form, JavaScript, advertising, analytics script, tracking pixel, external font or embedded third-party content. It does not set cookies or use browser storage. Visiting an external link or opening an email link uses the chosen destination or email service.

When this page is publicly hosted, its hosting provider will receive ordinary request information, such as an IP address and browser request details, to deliver the page. This local copy has not been published and no hosting provider has been selected. The app does not control a hosting provider's own logs or retention practices.

9. Privacy contact

Operator: Ben Reilley.

Privacy email: benjreilley@gmail.com.

Use this privacy email for questions, correction requests, deletion requests or help disconnecting access. Never include an access token, app secret or account password.