Privacy Policy
Brintora · Pinterest API application · last updated 22 October 2026
Who operates this application
This application is operated by Brintora (independent operator, Romania), contact adelandoluis@gmail.com. It is an internal automation tool used by the operator to publish the operator's own content to Pinterest. It is not offered as a public service and does not act on behalf of third-party Pinterest users.
What the application does
An internal automation tool that publishes the operator's own content to Pinterest. It creates Pins and boards in the operator's own Pinterest business account, links those Pins to the operator's own websites, and reads analytics for the operator's own account.
Requested Pinterest API scopes: boards:read, boards:write, pins:read, pins:write, user_accounts:read.
What data we access and why
| Data | Why | Kept for |
|---|---|---|
| Pinterest OAuth access and refresh tokens for the operator's own account | Authenticating API calls to create Pins and boards | Until revoked by the operator |
| Pinterest account identifier and username | Confirming which account the token belongs to | Until revoked |
| Board and Pin identifiers and metadata created by this application | Linking published Pins to the operator's own websites; avoiding duplicates | Until deleted or revoked |
| Aggregate Pin analytics (impressions, saves, clicks) | Measuring whether published content performs, for the operator's own account only | Retained as aggregate figures, not personal profiles |
| Email address | Purchase delivery and support, if the operator sells a product | Until you ask us to delete it |
| Payment record (amount, date, product) | Accounting, refunds, dispute handling | 7 years, as required by tax law |
What we do not collect
- Pinterest passwords, session cookies, or any Pinterest login credentials.
- Data belonging to other Pinterest users. The application does not act on behalf of any user other than its operator.
- Card numbers, CVVs or bank details. Card payments are handled entirely by Stripe, which is PCI DSS certified. We receive only the outcome of a payment and the email address entered at checkout.
How tokens are stored
Pinterest OAuth tokens are stored on the operator's own infrastructure, in a restricted file readable only by the operator's automation process. Tokens are never committed to public repositories, never embedded in client-side code, and never shared with third parties. Access can be revoked at any time from the Pinterest account settings, which immediately invalidates the stored token.
Who we share with
- Pinterest — the API provider; requests are made under the operator's own account.
- Stripe — payment processing, where a product is sold.
- Email delivery provider — to send download links or order confirmations.
- Hosting provider — serves these static pages and keeps standard access logs.
We do not sell data, and we do not share it for advertising. We do not combine Pinterest data from one account with data from other accounts or other services.
Cookies and tracking
These pages set no advertising cookies and load no third-party trackers. They are static files. If this changes, this page changes first.
Your rights (GDPR)
You may request a copy of your data, correction of it, or deletion of it. Email adelandoluis@gmail.com and it is handled within 30 days. You also have the right to complain to your national data protection authority.
Legal basis
We process account and content data to perform the service described above (GDPR Art. 6(1)(b)), and payment records to comply with tax law (Art. 6(1)(c)). Where we rely on legitimate interest to measure our own content performance (Art. 6(1)(f)), the data is aggregate and not used to profile individuals.
Data location
Data is stored with EU/US processors under their standard contractual clauses. Static pages are served from a global CDN.
Changes
If the application's data handling changes, this page is updated before the change takes effect, and the date at the top changes with it.