Love Where You Live Connector

At a glance

Everything the review asks for, in one card

App name

Company

Love Where You Live | Home Organization & Amazon Finds

Developer purpose

Personal API access, single personal use, via an MCP connector

Who uses it

One person, the account owner. There is no sign-up, no user base, and no way for anyone else to authenticate.

Accounts it touches

One Pinterest business account, owned and operated by the developer: @AmeliaCruzx0.

Scopes requested

boards:read, boards:write, pins:read, pins:write, user_accounts:read

Redirect URI

https://localhost/oauth/pinterest

Where it runs

Locally, on the developer's own computer. No server, no hosting, no public endpoint.

Data retained

One OAuth token file on that computer. Nothing else is stored.

Data shared

None. The only service contacted is the Pinterest API.

Commercial model

Not sold, not licensed, not distributed. It is personal tooling for one publisher's own workflow.

Overview

What the app does

Publishing to Pinterest well means writing keyword-led titles and descriptions, matching each pin to the right board, and then checking weeks later which of them actually earned saves and outbound clicks. Done by hand across several boards a day, that is slow and easy to get wrong.

The Love Where You Live Connector closes that loop. It is a small Node program that exposes the Pinterest REST API v5 as a set of tools an AI assistant can call, so the operator can draft a pin, publish it to their own board, and read back its performance in one continuous working session instead of three disconnected ones.

It is deliberately narrow. It publishes original images the operator created themselves, to boards the operator owns, on accounts the operator authorized. It has no interest in anyone else's data and no mechanism to reach it.

Mechanism

How it works

Authorize once, on the owner's own account The operator runs the local OAuth script, approves the app on Pinterest, and the returned access and refresh tokens are written to a single file on their machine. That file never leaves the machine.
Draft the pin Image and copy are produced locally, before Pinterest is contacted at all. Images are original graphics rendered by the operator's own tooling, never scraped or re-hosted from anywhere else.
Publish through the API The connector calls POST /v5/pins to create the pin on a board the operator owns, and PATCH or DELETE to correct or remove one later.
Read back the results Pin and account analytics endpoints return saves, impressions, and outbound clicks for the operator's own pins, so the next batch is informed by the last one.

The access token expires on Pinterest's normal 30-day cycle and is refreshed automatically using the stored refresh token. Revoking the app in Pinterest settings stops every one of these steps immediately.

Permissions

API access requested, and why

Scope	Why it is needed
boards:read	List the operator's own boards so each pin can be filed to the correct existing board.
boards:write	Create a board on the operator's own account when a new topic genuinely warrants one.
pins:read	Retrieve the operator's own pins to check what was already published and avoid near-duplicates.
pins:write	Create pins, and edit or delete them afterwards to fix a title, description, or destination link.
user_accounts:read	Confirm which account the token belongs to, and read account-level analytics for that same account.

No scope is requested for other users' content, follower data, messaging, or advertising.

Handling

Data practices

What is collected

Nothing is collected from any Pinterest user. The app reads only the account that authorized it and the pins and boards on that account.

What is stored

A single local file holding the OAuth access token, refresh token, app ID, and app secret. It is excluded from version control and is not backed up to any remote service. Pin images and text are read from local files at publish time and are not retained anywhere else.

What is transmitted

Requests go to api.pinterest.com and nowhere else. There is no analytics vendor, no logging service, no telemetry, and no third-party API in the request path.

Security

All traffic is HTTPS. Credentials live in a gitignored file on a single machine rather than in a shared or cloud store, which is appropriate given the app serves exactly one operator and has no multi-user surface to protect.

Platform safety

Compliance commitments

Original imagery only. Every pin uses a graphic created by the operator. Merchant product photography is never re-hosted or re-pinned as if it were the operator's own.
Affiliate relationships are disclosed. Where a pin links to an affiliate destination, the description opens with a plain-language disclosure and the image itself carries an #ad marker.
No link cloaking. Destination URLs are the real, full URLs. No shorteners, no redirect chains, no misdirection between what a Pinner sees and where they land.
No spam patterns. Pins are published at a steady human cadence to the operator's own boards. There is no follow or unfollow automation, no engagement automation, and no bulk repinning of other people's content.
Rate limits respected. The connector issues one request at a time in response to a deliberate action, and has no polling loop or background scheduler.
Human approval before anything publishes. The AI assistant drafts; the operator reviews and approves every batch before a single call is made.

Contact

Reaching the developer

For anything relating to this app, its API usage, or these policies, write to lauren.ginart@gmail.com. Messages about the Pinterest app review are answered directly by the developer, who is the sole operator of the integration.