Privacy Policy
Last updated: July 31, 2026
Pinspider ("Pinspider," "we," "us") is a Pinterest growth-automation tool: it crawls websites you add, generates pin images and copy from that content, and publishes or schedules pins to Pinterest boards on your behalf. This page explains exactly what data we collect, why, and how you can get it deleted. It's written to be read, not skimmed past — if anything below is unclear, email support@pinspider.com and we'll clarify or fix it.
1. Your Pinterest data
We connect to your Pinterest account exclusively through Pinterest's own OAuth 2.0 login flow. When you click "Connect Pinterest," you're redirected to Pinterest's website to sign in and approve access — Pinspider never sees, asks for, collects, or stores your Pinterest password, and we never touch your Pinterest session cookies. Pinterest hands us back an access token (and, for most connections, a refresh token), and that token is the only credential we ever hold for your account.
That token is encrypted (AES-256-GCM) before it's written to our database and decrypted only at the moment we make an API call on your behalf. It is used solely to read the boards on your Pinterest account and to publish the pins you've explicitly scheduled inside Pinspider — never for anything else, and never on a schedule or trigger you didn't set up yourself.
The token is permanently deleted the moment you disconnect that Pinterest account inside Pinspider, or when you delete your Pinspider account entirely. This is a real deletion, not a deactivation flag — the row is removed from our database.
2. Exact Pinterest OAuth scopes we request
Pinspider requests four scopes when you connect a Pinterest account, and only these four:
- boards:read — lets us list the boards on your account so you can pick which board each pin publishes to.
- boards:write — reserved for a board-creation feature we don't currently expose. Today Pinspider only reads your existing boards; it does not create, rename, or delete boards on your Pinterest account.
- pins:write — the scope that actually does the work: it's what lets Pinspider publish a pin (image, title, description, destination link, and board) to your account when a scheduled pin is due, or when you click "Publish now."
- pins:read — requested alongside pins:write. Pinspider does not currently read back or display your existing Pinterest pins; this is reserved for a possible future feature (e.g. showing real Pinterest-reported performance for pins we published).
We deliberately don't request any scope beyond these four (no messaging, no follower/audience data, no ad-account access).
3. Bring-your-own API keys (OpenAI, Replicate, and others)
Pinspider doesn't run its own AI generation infrastructure — it uses API keys you provide ("bring your own key," or BYOK) for the providers you choose to connect: OpenAI, Anthropic, Replicate, Fal, Google Gemini, Ideogram, Recraft, Stability AI, and Apify (used for optional Pinterest search/keyword research).
Every one of these keys is:
- Encrypted (AES-256-GCM) before storage, the same way Pinterest tokens are.
- Used exclusively to fulfill your own generation requests — your key never processes another user's request.
- Never pooled, shared, or reused across accounts under any circumstance.
- Never used for Pinspider's own purposes (we don't use your key for our internal testing, analytics, or anything outside serving your own account's requests).
- Deletable at any time from Settings → Integrations, which permanently removes the stored key.
Because these are your own keys, usage is billed by that provider directly to your own account with them — see Section 5 of the Terms of Service for cost responsibility.
4. Website crawling
Pinspider only crawls websites (domains and specific URLs) that you have explicitly added to your account. We fetch each site's sitemap and the individual pages listed in it, and extract page content and metadata (titles, headings, body text, images) — this is used only to generate pin copy and pin images for that page. We don't crawl or fetch anything you haven't added.
Pinspider does not currently perform a domain-ownership verification step when you add a site — if you can reach a URL, you can add it. Don't add a website you don't have the right to represent or generate promotional content for.
5. Google Analytics data
If you connect a Google account, we request exactly two OAuth scopes:
- analytics.readonly — read access to the GA4 properties you choose to map to your sites, used only to attribute pin performance (sessions/traffic arriving from the pins Pinspider published) on the Insights page.
- userinfo.email — read once, immediately after you connect, only to label the connection with the Google account's email address (e.g. "you@company.com") so you can tell multiple connected accounts apart. It is not stored beyond that label and is never used again.
We only ever read analytics data for GA4 properties you yourself select and map to a site — we never request or receive data for properties you haven't explicitly connected.
6. What we collect about you — and what we don't
We collect and store:
- Your account email address (used for login and any account-related communication).
- The site records you add (URLs, sitemap URLs, brand settings you configure).
- Pins and pin briefs Pinspider generates for you (titles, descriptions, hashtags, images, and the prompts used to generate them).
- Usage/operational logs (e.g. publish attempts and their outcomes, crawl history) needed to run the product and to help you (and us) debug a failed publish.
- Encrypted OAuth tokens and API keys, as described above.
We do not collect:
- Passwords or session cookies for Pinterest, Google, or any third-party service you connect.
- Payment card details (we don't process payments directly inside Pinspider today).
- Any data from a website you haven't explicitly added, or from a Pinterest/Google account you haven't explicitly connected.
- Precise device location, browsing history outside Pinspider, or any data from Pinterest/Google beyond the specific scopes listed above.
7. Sub-processors — who else touches your data
We use a small number of third-party services to run Pinspider. Here's exactly what each one receives:
- Supabase — our database, authentication, and file storage provider. Hosts your account record, encrypted tokens/keys, site and pin data, and generated pin images.
- Lovable (running on Cloudflare's infrastructure) — hosts the Pinspider application itself (the server that renders pages and runs scheduled publishing). Requests pass through this infrastructure in transit; it does not separately retain your data.
- Pinterest — receives the pin content (image, title, description, link, board) you schedule, at the moment of publishing, per the OAuth scopes in Section 2.
- Google — receives OAuth requests if you connect Google Analytics; returns the traffic data described in Section 5.
- OpenAI, Anthropic, Replicate, Fal, Ideogram, Recraft, Stability AI — receive generation prompts (built from your site's content) and your own API key, if you've connected that provider, solely to generate copy or images for you.
- Apify — if you connect it, receives your API token to run a Pinterest search-scraping actor for optional keyword research; results are stored in your account.
8. Retention and deletion
We keep your account data for as long as your Pinspider account is active. Disconnecting a Pinterest, Google, or BYOK provider connection deletes that connection's stored credential immediately and permanently.
To delete your account and all associated data (sites, pins, briefs, logs, and any connected credentials), email support@pinspider.com from the address on your account. We don't currently have a self-service "delete my account" button in the product — this is a manual request we process directly — and we aim to complete deletion within 30 days of a verified request.
9. Security
OAuth tokens and API keys are encrypted at rest (AES-256-GCM) at the application layer before they're written to the database, in addition to Supabase's own infrastructure-level encryption. Access to production data is limited to what's needed to operate the service.
10. Jurisdiction and your rights
Pinspider is operated from India, and this policy is governed by Indian law. If you're located in the European Economic Area or UK, you have rights under the GDPR — including access, correction, deletion, and portability of your data — which you can exercise by emailing support@pinspider.com. If you're a California resident, you have similar rights under the CCPA, including the right to know what personal information we hold and to request its deletion. We don't sell personal information, to California residents or anyone else.
11. Changes to this policy
If we materially change what we collect or how we use it, we'll update the date at the top of this page. Continued use of Pinspider after a change means you accept the updated policy.
12. Contact
Questions, deletion requests, or anything unclear above: support@pinspider.com.