Privacy Policy

Message Automation and Messenger

Message Automation connects to the Prairie Creek Puppies Facebook Page to evaluate receiving customer inquiries and identifying which advertisement an inquiry relates to. The current evaluation captures incoming events for staff review; it does not send automated replies.

When supplied by Meta, these events may include:

• Message text and attachment information or links.
• Page-scoped sender identifiers, the receiving Page identifier, message identifiers, and timestamps.
• Button interactions and referral information, including an ad identifier or other context indicating how a conversation began. This information is not available with every message.

We use this information to review inquiries, test message delivery and ad attribution, and troubleshoot the connection. Customer messages are treated as customer content and do not authorize changes to our internal business systems. The Messenger receiver is separate from our staff Telegram management bot.

Messenger storage and service providers

Captured Messenger events are stored on an operator-controlled computer with access limited to authorized operators. Connection credentials are stored separately from event records and are not published in source code or public reports.

Meta delivers the events, and Cloudflare transports them to our receiver. Authorized staff may use OpenAI's Codex to inspect captured events, which means message content and associated metadata may be processed by OpenAI during that review. We do not sell or rent Messenger data. These providers process information under their applicable terms and privacy policies: Meta, Cloudflare, and OpenAI.

Messenger data retention and deletion requests

We retain captured Messenger records only as needed to evaluate the connection, review inquiries, and resolve delivery issues. You can request access to or deletion of the Messenger data held by these tools by emailing hello@prairiecreekpuppies.com with the subject “Message Automation data deletion” or “Message Automation privacy request.”

Include the Facebook name used to contact our Page and the approximate date of the conversation so we can locate the records. Do not send passwords or access tokens. We may ask you to confirm the request through the original conversation to verify that it concerns your information. We will respond with the outcome after reviewing the request. Deleting our captured records does not delete messages or other records retained by Meta; those are managed through Facebook and Messenger.

YouTube API Services

Puppy Workflow Desktop uses YouTube API Services. By authorizing or using the tool, users are also agreeing to the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.

YouTube information we access and store

The tool accesses or stores only the information needed to publish:

• Google OAuth authorization credentials, including a refresh token, that permit uploads to an authorized YouTube channel.
• The identifier of the authorized destination channel.
• User-selected video files, thumbnails, titles, descriptions, and upload settings supplied for publication.
• Limited upload results, such as the resulting YouTube video ID, URL, status, and processing receipt.

The tool does not request Google passwords, contacts, viewing history, search history, or advertising-profile information.

How YouTube information is used

Authorized data is used only to authenticate the selected channel, upload the requested video and thumbnail, apply the approved video details and visibility setting, verify the result, and maintain a local record of the publishing job. It is not used for advertising, tracking, profiling, or any unrelated purpose.

YouTube storage and security

OAuth credentials and workflow records are stored locally on an operator-controlled computer. Credentials are kept in a private environment file and are not included in public source code or public workflow reports. Reasonable access controls are used to limit this information to authorized operators.

YouTube data sharing

Video content, thumbnails, metadata, and authorization requests are transmitted to Google and YouTube as necessary to perform an authorized upload. Google user data is not sold, rented, shared with advertisers, or disclosed to unrelated third parties.

YouTube retention, deletion, and revoking access

Local authorization data is retained only while the channel remains connected. A user can revoke access at any time from the Google Account third-party permissions page. A user may also request deletion by emailing the address below. After revocation or a verified deletion request, locally stored Google authorized data for that user will be deleted as soon as possible and no later than seven calendar days.

Revoking the tool does not automatically delete videos already published to YouTube. Those videos remain under the channel owner's control and can be managed or deleted in YouTube Studio.

Policy changes

This policy may be updated if the tool's data practices change. The current version and its effective date will remain available on this page.

Contact

For privacy questions, authorization revocation assistance, or a deletion request, email hello@prairiecreekpuppies.com.