Reviewer Guide
A clear guide for reviewing the product's intended behavior.
This page is designed to help platform reviewers understand what the product does, how users stay in control, and where supporting policy information is published.
Overview
What the product does.
The reviewer should be able to understand the service without seeing the private dashboard first.
1. Product purpose
Pinboardy is a workflow assistant for preparing Pinterest-ready drafts. It helps users connect accounts via OAuth, upload their own images, generate draft metadata with AI, and publish only after explicit user approval.
2. Intended users
The intended audience includes creators, small businesses, Pinterest managers, and agencies that need a more structured publishing workflow.
3. Account connection model
Pinterest accounts are connected through OAuth only. The product does not ask for Pinterest passwords.
4. Human approval before publication
AI output is presented as a draft. The user can review, edit, schedule, or discard the draft before publication. The intended workflow does not silently publish content without approval.
5. Content boundaries
The product is intended for user-owned or user-authorized content. It is not positioned as a scraper, account farm, or engagement manipulation system.
6. Support and deletion
Public support, privacy, and deletion information is available on this site. Users can contact support, request deletion, and disconnect accounts.
Scopes and access
Why Pinterest access is needed at a high level.
The exact scopes should be documented in the app dashboard and submission materials, but this public explanation should remain visible and simple.
Read account and board context needed to prepare a valid publishing destination.
Allow publication of user-approved pins to the user's connected Pinterest account.
Support account management, error handling, and publication history inside the product.
Do not request broader access than necessary for the declared workflow.
Reviewer checklist
What a reviewer should verify.
These are the main points this site is designed to make obvious.
Verify that the public site clearly states OAuth-only connection and no password collection.
Verify that the site repeatedly explains user approval before publication.
Verify that privacy, terms, acceptable use, deletion, security, and support pages are publicly accessible.
Verify that the product is described as a workflow assistant rather than a hidden automation tool.
Verify that account disconnect and deletion flows are documented.
Verify that the production dashboard, if separate, follows the same approval-first behavior described here.
Where to look
Public pages that support the review.
These links should remain live and accessible before submission.
Suggested review materials
Additional screenshots or assets to provide manually.
This public site supports the review, but it should be paired with a concise set of materials from the product dashboard.
Pinterest OAuth connection screen
Draft review screen showing editable AI-generated metadata
Approval or scheduling screen before publication
Connected account settings with disconnect option
Deletion request flow or account settings page
Publication history or audit view
Note: the production application dashboard may be hosted separately from this public site. This site is intended to provide the public-facing trust, policy, and reviewer context layer.