This addendum supplements the Savvy Stylish Privacy Policy and governs our use of the Pinterest API v5. In the event of any conflict between this addendum and the main Privacy Policy, this addendum controls with respect to Pinterest-related data.
1. Use of the Pinterest API
Savvy Stylish uses the Pinterest API v5 (https://api.pinterest.com/v5/) solely to manage and publish content to our own official Pinterest business account at pinterest.com/savvystylish. We do not use the Pinterest API to access, collect, or process data from any other Pinterest user's account.
We use the following Pinterest API v5 endpoints:
Endpoint
Method
Purpose
/v5/pins
POST
Create new image pins linked to Savvy Stylish product pages
/v5/pins/{pin_id}
GET
Retrieve pin metadata to verify successful publication
/v5/pins/{pin_id}
DELETE
Remove or reschedule incorrectly created pins
/v5/boards
GET
Retrieve our own board list to assign pins to the correct board
/v5/boards/{board_id}
GET
Retrieve metadata for a specific board prior to pinning
/v5/boards/{board_id}/pins
GET
List existing pins on a board to avoid duplicates
/v5/media
POST
Register image/video upload intent prior to pin creation
/v5/media/{media_id}
GET
Confirm media upload status before creating a pin
/v5/user_account
GET
Verify authentication status of our own business account
OAuth 2.0 Scopes requested:
boards:read — to list and retrieve our own boards
boards:write — to create or update boards for our own account
pins:read — to verify pin status and avoid duplicate publishing
pins:write — to create and delete pins on our own account
user_accounts:read — to confirm account identity and authentication state
All API calls are made exclusively on behalf of the Savvy Stylish business account. No third-party user authorization flows are implemented.
2. Disclaimer of Affiliation with Pinterest
Savvy Stylish is not endorsed by, affiliated with, sponsored by, or officially connected to Pinterest, Inc. in any way. The Pinterest name, logo, and related marks are trademarks of Pinterest, Inc. Our use of the Pinterest API is subject to Pinterest's Developer Guidelines and Terms of Service.
3. Pinterest-Derived Data We Access
Through the Pinterest API v5, we access only the following data — all associated exclusively with our own Savvy Stylish Pinterest business account:
Board metadata: Board names, board IDs, and board privacy settings (used to route pins to the correct board)
Pin metadata: Pin IDs, titles, descriptions, destination URLs, and publication status (used to confirm successful pin creation and avoid duplicates)
Media upload IDs: Temporary media identifiers returned by /v5/media during the image upload workflow
Account identity: Username and account ID from /v5/user_account (used solely to verify API authentication)
We do not access follower data, audience analytics, other users' boards or pins, or any personal information belonging to Pinterest users outside our own account.
4. How We Use Pinterest-Derived Data
Pinterest-derived data is used exclusively for:
Pin creation: Submitting product images, titles, descriptions, and destination URLs to our own Pinterest boards via POST /v5/pins
Scheduling and queue management: Determining which boards exist and selecting the correct board ID before publishing
Publication verification: Reading back pin status via GET /v5/pins/{pin_id} to confirm successful creation
Deduplication: Checking GET /v5/boards/{board_id}/pins to avoid re-publishing identical content
This data is never used for audience profiling, advertising targeting, or any purpose unrelated to managing our own Pinterest content.
5. Data Retention and Deletion Upon Disconnection
If our application is disconnected from the Pinterest API, or if Pinterest revokes our API access:
OAuth access tokens are invalidated and deleted from our systems immediately upon disconnection or revocation
Pinterest-derived metadata (board IDs, pin IDs, media upload IDs) stored in our pipeline is deleted within 30 days of disconnection
Backup copies containing any Pinterest-derived data are purged on the next scheduled rotation, which occurs within 30 days
No Pinterest-derived data is retained beyond these windows for any purpose
Sell, license, rent, or otherwise transfer Pinterest content or Pinterest-derived data to any third party
Redistribute, republish, or make available Pinterest API data outside of our own pin scheduling workflow
Use Pinterest-derived data to build datasets, train machine learning models, or create derivative products for external use
Share Pinterest API access tokens or credentials with any third party
Pinterest content and API data accessed by our application is used solely to operate and manage the official Savvy Stylish Pinterest presence.
7. Data Security
Pinterest API OAuth tokens and associated metadata are stored in our internal pipeline with access restricted to authorized personnel only. We apply industry-standard security practices including encrypted storage of tokens and access logging. Tokens are rotated upon expiration and revoked immediately upon disconnection.
8. Contact Us
For questions about our Pinterest API data practices or this addendum:
