Your content. A clear view of your data.

The service operator.

The operator’s public service details are still being configured. Paid checkout remains unavailable until the required details and service checks are complete. The support inbox is available after sign-in.

A workspace tied to your sign-in.

Queuefern uses native Sign in with ChatGPT. The application receives your account identifier, email address, and name when available, and uses them to identify your workspace. Your ChatGPT password is not entered into Queuefern.

Workspace requests are scoped to the signed-in account. The site operator and hosting providers have administrative responsibilities for the service and can have administrative access to stored data. Public access to the service does not make your workspace records public.

The information you bring with you.

Queuefern stores your workspace details, brands, channel identifiers, bundles, posting times, captions, channel-specific versions, goals, and uploaded media on its hosted database and file storage. It also keeps delivery identifiers, statuses, errors, published links, available metric snapshots, manually entered results, and in-app notifications so you can follow a post’s progress. Support conversations and replies are stored with your workspace. Subscription identifiers, status, and the version of terms accepted are stored for billing access; payment details are handled by Stripe.

Your captions, source uploads, and other records you create remain available until removed through the product. YouTube API data follows the separate retention rules below. Removing a draft also attempts to remove its unused media. A file shared by another post is kept for that post. Eligible source media can be removed in Account & plan while its metadata, delivery history, and results remain. The service does not currently offer a configurable retention period or an automatic archive policy.

Authorize directly with the social network.

Queuefern connects directly to supported social networks through their authorization screens. Your social-network password is entered on the network’s own site, not in this workspace. For Bluesky, a handle helps find the account’s authorization server; an app password is not requested.

The service stores the access and refresh credentials needed for authorized publishing in encrypted server storage. Social-network tokens and developer-app secrets are not placed in browser storage or included in your data export. The site operator configures the service’s developer apps; customers grant access to their own accounts. Account permissions, network app approval, and token expiry can affect which actions remain available.

When you confirm a post, Queuefern sends the necessary content, media, destination information, visibility choices, and scheduling information directly to the selected network. Its own terms and privacy practices apply. YouTube users can read the YouTube Terms of Service and Google Privacy Policy. Use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

You can revoke permission in the network’s connected-app settings; Google connections can be managed in Google account permissions. Revocation can stop future deliveries. Reconnect only when you want to grant access again. Removing a brand stops publishing through it here and requests Google revocation for its YouTube connection. If Google cannot confirm revocation, cleanup is retried and shown as pending. Connections made through the previous publishing service remain labelled for direct reconnection; historical delivery records remain readable.

Background checks refresh YouTube channel details and confirm authorization and stored video availability. YouTube API data is removed if authorization or availability cannot be confirmed within 30 days, and sooner when revocation or a removed video is detected. On a requested YouTube disconnect, stored credentials and API-derived identifiers, channel names, avatars, links, and metrics are removed within seven days. Your own captions, uploaded sources, and publication history are separate from that API data.

A few remembered choices.

Your browser remembers the selected channels, usual scheduling mode and time zone for a batch, and whether you enabled browser alerts. Uploaded files are held locally while they are being sent; keep the page open until uploading finishes. Draft content itself is saved to the server as you work.

In-app delivery notifications remain in your workspace. Optional browser alerts need your permission and are checked while you are using the page. They are not a background push service. This release does not send automatic email digests.

Take a copy. Remove a workspace.

Open the account menu in your workspace and choose Export your data to download a JSON copy of your records, including media metadata. The export does not bundle the original image or video files. Export before deletion if you want to keep those records.

Delete workspace in the same menu requires you to type DELETE. When deliveries are pending or unconfirmed, you can request deletion: new work is paused while existing deliveries are checked. Scheduled or processing posts may still publish during that wait. Deletion removes the workspace’s stored records and uploaded files, and removes its stored channel credentials. Cleanup first tries to resolve already-submitted network operations. At the seven-day deletion deadline, unconfirmed operations may be forgotten without confirming cancellation. Already-submitted posts may still appear on the network. YouTube API data is removed within seven days of a deletion request. Other workspace records can remain while billing cancellation is retried. The app reports cleanup or cancellation failures rather than claiming completion; contact support if they remain unresolved.

Posts already published on social networks remain on those networks. Native drafts already handed to a social network may remain and can still be completed there. Deleting Queuefern data does not delete your ChatGPT account, your social accounts, or copies that third parties hold under their own policies. Remove published content directly on the relevant network when needed.

A question or a rough edge?

Use the support inbox to send a question and read replies. Include the affected post’s title and visible error. Keep passwords, access tokens, and private customer details out of your message.