PINTEREST JULIANA

Privacy Policy

This policy explains how the Pinterest Juliana connector handles information when used as a private visual reference library for reading Pinterest boards, board sections, and Pins.

Effective date: August 22, 2026

1. What the app does

Pinterest Juliana is a read-only connector that helps the app owner review saved Pinterest visual references. It can list boards, list board sections, list Pins in a board or section, and retrieve details for a specific Pin.

The connector does not publish Pins, save Pins, create boards, update boards, delete content, run ads, or access analytics.

2. Information accessed

When authorized by the Pinterest account owner, the connector may access Pinterest data permitted by the approved scopes, including:

• board names, descriptions, identifiers, privacy status, and cover media;
• board section identifiers and names;
• Pin identifiers, titles, descriptions, links, media metadata, and image URLs;
• secret boards or secret Pins only if the owner explicitly grants the corresponding secret-read scopes.

3. How information is used

The information is used only to help the account owner browse, search, compare, and select visual references for personal planning, classes, carousels, presentations, or design direction.

Saved Pinterest content is treated as reference material. Saving an image on Pinterest does not imply permission to reuse it publicly or commercially.

4. Storage and retention

Pinterest access tokens may be stored locally on the account owner’s device or private workspace configuration so the connector can make authorized API requests. The connector does not operate a separate public database for Pinterest content.

Any local token or cached data can be deleted by the account owner at any time from the local environment where the connector is installed.

5. Sharing and sale of data

Pinterest Juliana does not sell personal information. It does not share Pinterest data with advertisers, data brokers, analytics providers, or third-party marketing services.

Data may be processed only as needed to provide the requested connector functionality inside the authorized app environment.

6. User control and revocation

The Pinterest account owner can revoke access at any time through Pinterest account settings, the Pinterest developer app settings, or by deleting the local access token from the connector environment.

After access is revoked, the connector cannot make new Pinterest API requests unless the account owner authorizes it again.

7. Security

The connector uses OAuth tokens instead of Pinterest passwords. The account owner should keep app secrets, access tokens, and refresh tokens private and should not commit them to public repositories or share them in public documents.

8. Changes to this policy

This policy may be updated if the connector’s functionality, scopes, storage practices, or deployment model changes. The effective date above will be updated when material changes are made.

9. Contact

For privacy questions or access revocation requests, contact the app owner through the contact information listed in the Pinterest developer app profile.