PERGO CREATOR

Privacy Policy

Effective date: October 4, 2026

Pergo Creator is operated by Juan Cruz Pergolesi, the creator behind @pergoreviews. This policy explains how the Pergo Creator Instagram, YouTube and Pinterest integrations and this policy website handle information. It does not replace Instagram’s or other linked services’ privacy policies.

What the integration does

Pergo Creator helps manage the operator’s own Instagram content. It uses Instagram’s API and signed webhook notifications to receive comment events, identify requests such as “link,” and associate a request with the exact Reel and a verified product link. When the private-reply feature is enabled and a request passes its checks, it can send the requesting Instagram user a private reply containing the requested product or affiliate link. A comment is not permission for unrelated marketing messages. Requested private replies are enabled for qualifying new comments; historical comments are not backfilled.

Information processed

The comment-processing queue stores identifiers, timestamps and processing status rather than a copy of the comment text. Comment text is evaluated during receipt and may be read again from Instagram before a reply. Operator access tokens and app credentials are used to authenticate the integration; they are not published on this website. We do not ask commenters for their Instagram password, payment details, address or identity documents.

How information is used

We use this information to handle the request you make, verify account and media ownership, retrieve the corresponding product link, send an authorized requested reply, enforce rate limits, prevent duplicate or unintended messages, investigate errors and secure the service. We do not use commenters’ information to build advertising audiences or sell personal data.

Third-party services and affiliate links

Meta/Instagram provides the APIs, delivers webhook events and handles Instagram comments and messages. DigitalOcean hosts the application and its operational records. Cloudflare provides DNS and, for proxied services, network and security processing. Buffer is used for the operator’s content distribution and Backblaze B2 for the operator’s media storage; neither is the private-reply delivery mechanism. The private-reply flow does not send the commenter’s identifier or comment text to Amazon to select a product.

Product links may lead to Amazon and include an affiliate tracking tag identifying the operator. Qualifying purchases may earn the operator a commission. If you follow a link, the destination may process connection, browsing or purchase information under its own policy. Pergo Creator does not receive your payment information through this comment-to-link feature.

Minimization, security and retention

We limit processing to the identifiers, content checks and operational records needed for these functions. Credentials and application state have restricted filesystem access, the public endpoints use HTTPS, and webhook signatures are checked before accepting events. No security measure is an absolute guarantee.

Comment-event, reply and duplicate-prevention records persist in the application database. There is currently no automatic fixed-age deletion schedule for those records. Records are retained for operation, duplicate prevention and incident investigation, subject to manual review and deletion requests. Operational logs and backups may also contain identifiers or processing records; their lifetime depends on their rotation and backup handling. We do not claim that deleting an Instagram comment automatically deletes the corresponding operational records.

Access, deletion and privacy requests

To ask about your information, request access or correction, or request deletion of Pergo Creator’s records associated with you, send a private message to @pergoreviews on Instagram with the words “Pergo Creator privacy request”. Include your Instagram username, the relevant Reel permalink and what you want us to do. The operator handles privacy requests manually; the automated product-link feature is not required for this contact method. Please do not send passwords or access tokens.

We may ask you to contact us from the relevant Instagram account to confirm the request. We will review the request, remove data no longer needed and explain any limited retention necessary for security, legal obligations or resolving an outstanding request. Backup copies may persist until removed or replaced; any restoration must take completed deletion requests into account. We do not offer an automated deletion callback or promise immediate deletion from backups. Deletion from Pergo Creator does not delete comments, messages or records held independently by Meta, Amazon or other providers. You can also use Instagram’s own controls for your comments and messages.

YouTube account authorization and API use

The operator authorizes their own YouTube channel through Google OAuth. Pergo Creator uses the YouTube Data API to verify the authorized channel and video ownership and to create one affiliate-link comment on the operator’s verified videos. It stores the authorized channel identifier, video identifiers, affiliate-comment identifiers, timestamps and delivery status to prevent duplicate comments. Google access and refresh tokens are stored privately on the production host and are used only for the authorized integration. They are not exposed to site visitors or shared for advertising.

Google/YouTube processes authorization and API requests under the Google Privacy Policy. This integration uses YouTube API Services and is subject to the YouTube Terms of Service. The account owner can revoke access in Google account permissions. Revocation stops future authorized access but does not automatically delete existing publication/comment receipts. To request deletion of locally stored Google/YouTube authorization or API records, contact pergoyt@gmail.com; requests are reviewed manually. We do not sell Google user data or use it for unrelated advertising, profiling, or model training.

Pinterest integration (being prepared)

Pergo Creator is preparing direct Pinterest API access for the operator’s own Pergo Reviews account. After authorization and Pinterest approval, it will upload the operator’s videos and cover images, create Pins on the operator’s own board with titles, descriptions and product or affiliate destination links, and read the operator’s account, board and Pin data to verify ownership and publication. Until approved and validated, existing Pinterest publishing continues through Buffer.

The integration will retain account and board identifiers, Pin identifiers, source-media fingerprints, publication timestamps and delivery status for verification and duplicate prevention. Access credentials will be stored privately on the production server. This integration does not access unrelated users’ private boards, sell Pinterest user data, or use Pinterest data to train AI models. Pinterest processes API requests under its Privacy Policy. The operator can revoke access in Pinterest’s connected-app settings. Revocation stops future access but does not automatically erase existing public Pins or local publication receipts. For access or deletion requests concerning locally stored Pinterest data, contact pergoyt@gmail.com. Requests are handled manually, subject to the retention and backup limitations described above.

This policy page

This page contains no advertising pixels, analytics scripts, forms or application cookies. Following an external link takes you to a third-party service. Hosting and network providers still process the technical information necessary to serve and secure the page.

Changes and contact

Changes to this policy will be posted here with an updated effective date. Privacy contact: Juan Cruz Pergolesi, via @pergoreviews.