Privacy

PageBeeper is an invitation-only publishing service operated by Ryan McGreevy doing business as PRO Direct. Customers and teams use separate workspaces to manage their authorized social accounts.

Last updated October 27, 2026

Operator and customer workspaces

PRO Direct operates PageBeeper and the YouPager brand. A connected social account belongs to its account holder; connecting it does not make that account or business the owner of PageBeeper. This public website provides product and policy information and temporary delivery of selected publishing media.

Workspace membership is managed separately for each workspace. Access to one workspace does not automatically grant access to another. A person may belong to more than one workspace and have a different role in each. Select the intended workspace before connecting an account, uploading content, scheduling a post, or managing team access.

Information used by the workspace

PageBeeper uses sign-in identities, names and email addresses, login-provider identifiers, team memberships and roles, and invitation records. It also stores uploaded content, draft captions, schedules and time zones, queue records, and publishing results. Connecting a social account provides account identifiers, granted permissions, and access tokens needed to use the selected publishing features.

These details support access to the shared workspace, preparing content, connecting the intended accounts, scheduling posts, publishing selected content, and showing publishing status. Authorized teammates share the workspace’s content, calendar, queue, social connections, and publishing results. Drafts, uploads, and connection details are stored privately and are not listed on this public service.

Invitation requests

If you join the PageBeeper waitlist, Clerk stores the email address you submit so PRO Direct can manage your request for early access. Clerk may send a confirmation and, if your request is approved, an invitation email. Joining the waitlist does not create a PageBeeper account, add you to a workspace, subscribe you to a newsletter, or connect any social account. Contact ryan@youpager.com if you want your request removed.

Sign-in and team access

Each workspace’s owners control its invitations and membership. Clerk handles email and Google sign-in, account verification, and login sessions for invited users. Google also processes authentication information when someone chooses Google sign-in. The original operator’s private backend access may use ChatGPT sign-in. PageBeeper login is separate from authorization to a connected social account.

Connected platforms

When an authorized workspace member selects content for publishing to Facebook or Instagram, Meta receives that selected content and the information needed to create the post. Other connected publishing platforms, including LinkedIn when connected, receive the content selected for them. Published content is subject to that platform’s visibility settings and policies.

Facebook and Instagram post statistics

When an authorized workspace teammate opens Reporting or an individual statistics panel for a confirmed Facebook or Instagram post, PageBeeper uses that account’s existing Meta authorization to request available aggregate engagement counts. The app verifies the saved post and its connected Page or Instagram professional account. Basic likes and comment counts may be available with existing read access; Facebook Insights and Instagram media Insights need the appropriate approved read permissions and account consent. Metrics depend on post type, authorization and Meta’s availability. Missing or unsupported counts are shown as unavailable rather than zero.

Reporting automatically loads available counts for the visible page of posts, with a bounded number of requests at a time. Additional posts load when you show them, and refresh controls request a new reading subject to a short cooldown. These read-only statistics requests do not edit, republish or delete posts, and do not read individual viewers’ identities or comment text. Results remain in the current browser page’s memory while that page is open; PageBeeper does not retain statistics in a server cache or historical reporting database. Authorized teammates share access to their workspace’s available counts. You can disconnect an account or revoke its authorization as described below. Publishing integrations and permission grants remain separate from availability of reporting data.

YouTube connections

PageBeeper uses YouTube API Services when you connect a YouTube channel. With your permission, it identifies the selected channel, uploads videos with the title, description, audience and visibility you choose, and checks upload and processing results. YouTube receives the video and its selected settings. This authorization is separate from Google sign-in.

When you open Reporting or statistics for a published YouTube video, PageBeeper uses the connected channel’s existing read authorization to retrieve that video’s available lifetime view, like and comment counts. Reporting automatically reads the visible page of posts; additional pages and manual refreshes read further counts. These read-only counts are shared with authorized workspace teammates. Statistics do not edit or republish a video. Missing counts are shown as unavailable; shares require separate Analytics access and repost counts are not provided by this integration. Results remain in the current browser page’s memory while that page is open. PageBeeper does not retain these statistics in a server cache or historical reporting database.

The workspace stores the channel identifier, name and handle, encrypted access and refresh credentials, and upload and publishing results. Channel identity and publishing results support your requested features and are visible to your authorized workspace teammates. Stored access and refresh credentials are not shown to teammates. Google API information is not sold, used for advertising, or used to train AI models. PageBeeper’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

You can disconnect a channel in Settings → Connected accounts, or revoke PageBeeper’s YouTube access through Google’s security settings. Connection and publishing records obtained from YouTube are refreshed or removed as required for continued authorization. Removing PageBeeper’s stored data does not delete videos held by YouTube. Read the Google Privacy Policy and the data deletion instructions.

Who receives Google user data

PRO Direct operates PageBeeper and processes Google account and YouTube API information only to provide the features you request. Cloudflare and OpenAI Sites provide PageBeeper's hosting, private application processing, database and media-storage infrastructure, and may process the Google API information stored or handled by the service for those purposes. Clerk provides PageBeeper login and session management and processes the Google sign-in identity information used when you choose Google sign-in; PageBeeper does not send YouTube publishing tokens or video statistics to Clerk for login. Google and YouTube receive the requests, selected videos and settings required to connect your channel and perform the uploads and status/statistics checks you request. Authorized members of your selected workspace can see that workspace's connected-channel identity, publishing results and available aggregate statistics; members cannot view the stored OAuth credentials.

PageBeeper does not sell Google user data or share it for advertising, data brokerage or AI model training. It does not send Google OAuth tokens or retrieved YouTube statistics to Zernio, Meta, LinkedIn or TikTok for its YouTube feature. If you separately select the same user-provided content for another publishing destination, that destination receives the content and settings you explicitly select under its own authorization. Disclosure may also occur where required by applicable law; any response follows PRO Direct's government-data-request procedure and is limited to what is required.

How Google user data is protected

PageBeeper uses HTTPS for data transmitted between your browser, its public gateway and private backend, and Google API services. Google access and refresh tokens and resumable YouTube upload-session details are encrypted with AES-256-GCM before storage. Encryption keys and application secrets stay in restricted server-side runtime secret stores; they are not included in browser code or returned to workspace members. Server-side authentication and workspace-membership checks restrict access to channel connections, publishing records, media and available statistics. Workspace owners manage invitations and remove team access. OAuth state is single-use, short-lived and bound to the initiating browser, signed-in member and workspace. Private application responses and uploaded-media responses use no-store cache controls; temporary publishing-media links are signed and expire within one hour. Aggregate statistics remain in the current browser page's memory and are not kept in a historical reporting database. No service can guarantee absolute security. Disconnection, revocation and deletion controls are described in the YouTube and storage/deletion sections.

TikTok connections through Zernio

PageBeeper currently uses Zernio as its TikTok publishing service. Connecting TikTok authorizes the selected account’s profile and video publishing features through Zernio. PageBeeper stores the connected account identifier, profile details, granted capabilities and publishing results; its restricted Zernio publishing key stays on the server. Authorized teammates can use this shared connection.

When you select TikTok and confirm a post, Zernio and TikTok receive that video, caption and the publishing settings you selected. Zernio may store copies needed to process and manage publishing. This first integration supports public video posting, and does not silently send a post to a manual TikTok inbox workflow. Read Zernio’s privacy policy and TikTok’s privacy policy for their separate handling of information.

Disconnect in Settings → Connected accounts to block new PageBeeper publishing and request removal of the Zernio connection. This does not promise immediate revocation of TikTok’s separate authorization or erase media already received by Zernio or TikTok. You can also manage the Zernio or Late app’s permissions in TikTok’s connected-app settings. Contact the workspace owner for provider-held data requests.

LinkedIn Page connections through Zernio

PageBeeper uses Zernio to publish to an authorized LinkedIn company Page. With your permission, Zernio receives the profile identity, email address, organization access and publishing permissions required by its connection flow. PageBeeper requests the publishing permission set without advertising access. The workspace stores the selected Page’s identifier and name, its Zernio connection identifier, granted publishing capabilities, and publishing results. Authorized teammates can use this shared Page connection.

When you select LinkedIn for a post, Zernio and LinkedIn receive its caption, selected image or video, and destination Page information. Zernio may retain copies needed to process publishing. The LinkedIn destination is the company Page selected in PageBeeper; connecting that Page does not make it the owner of PageBeeper. Read Zernio’s privacy policy and LinkedIn’s privacy policy.

Disconnect in Settings → Connected accounts to block new PageBeeper publishing and request removal of the Zernio connection. You can separately revoke the Social Media Connector app in LinkedIn’s permitted-services settings. Disconnecting does not delete a published post or erase information already held by Zernio or LinkedIn. Contact the workspace owner for provider-held data requests.

AI videos processed by HeyGen

HeyGen customer generation is disabled. In a separately approved private owner test, saving a video plan keeps it within PageBeeper. Only the later generation confirmation sends the reviewed first-frame image and video and sound directions to HeyGen. PageBeeper does not automatically send social-account credentials, reporting statistics or Google API account information to HeyGen. The API key remains on our backend.

We store the request’s workspace, resource identifiers, status and review record so we can deliver its result, avoid duplicate paid requests and manage deletion. A completed video is imported into the requesting workspace’s private media storage. Authorized workspace members can access that workspace’s saved content; other workspaces cannot.

HeyGen processes these inputs and outputs under its terms, privacy policy and applicable data processing addendum. Its standard terms permit model improvement and training unless an opt-out applies. As of October 27, 2026, we have requested a workspace-wide training opt-out and are awaiting confirmation of its scope and effective date. We do not claim that it is active or that this self-serve account has zero data retention. Customer generation remains disabled during these checks.

HeyGen files do not automatically expire on this account. PageBeeper keeps local media until it is deleted. Provider deletion is tracked separately: an unconfirmed response stays pending and missing resource details need support review. HeyGen support states that deleted data can remain in disaster-recovery backups for up to 60 days. Service, security and legally required transaction records may be handled separately. Read the HeyGen deletion instructions before assuming that deleting a draft has erased every copy.

Temporary media links

This relay retrieves an authorized media file from the private app and streams it to the requester. It does not maintain its own content database or upload library. The relay is designed to prevent caching, and it does not intentionally record access tokens or signed link values in application logs. Hosting infrastructure may process request and security logs.

Storage and deletion

The owner can use Settings → Advanced connection setup → Delete workspace data to remove uploads, drafts, scheduled posts, weekly slots, social connections, publishing history, and processing jobs. Team identities, memberships, invitations, and login access records are managed separately and remain after this content deletion. Removing a teammate revokes their workspace access; shared content, social connections, schedules, and publishing history remain. No fixed data retention period is promised here.

A completed disconnect removes PageBeeper’s stored active connection details; provider-specific cleanup may remain pending until confirmed. Deleting data or disconnecting an account does not remove published posts or cancel publishing already requested from a platform. Those posts must be managed on the relevant platform. Read the data deletion instructions.

Questions and control

For questions or requests about PageBeeper’s privacy practices, contact PRO Direct at ryan@youpager.com. Your workspace owner can also help with that workspace’s membership, shared content and connections.

PageBeeper currently offers an invitation-only pilot; public self-service signup is not available. Login-provider records and social-platform records are managed separately from PageBeeper content. Workspace owners manage their workspace’s access and data through the private dashboard. Contact PRO Direct for help with identity records or requests that a workspace owner cannot resolve.