Link formats and privacy: public, private and hidden accounts

An order is a delivery to a URL. The panel takes the link, passes it to a supplier, and the supplier sends accounts or views to whatever the link resolves to. If the link does not resolve without a login, the delivery has nowhere to land. Many failed orders that look like panel problems are link problems, and many link problems are visible before payment.

This guide covers the link formats each order type needs, the difference between public, private and hidden content, and the privacy boundary a panel should never cross. It ends with a check you can run in a logged-out browser in five minutes.

The link is the delivery address

A supplier does not log in as you. It reads the public page the link points to and delivers against the identifier in that page. That is why a public profile URL is enough for a follower order and why a password is never needed. The link is the address; the order is the delivery; the panel is the courier.

The address has to be current. A link that redirects to a login page, a link that points to a deleted post, a link that opens a story which has already expired: each one gives the supplier nothing to deliver to. The order may sit in a queue, fail, or complete against a count that cannot move. The panel's order page is the place to see which one happened.

What each category needs

The category decides the link format. A follower order targets an account; a like order targets a post; a view order targets a video; a member order targets a channel or a group. Using the wrong format is another common link error.

Category	Link to send	What makes it fail
Followers, subscribers, members	The public profile, channel or group URL	A private account, a channel that requires approval, a group that requires an invite
Likes, comments, saves	The public post, reel or video URL	A deleted post, a private post, a post that is not published yet
Views	The public video or reel URL	A private video, a removed video, a live stream that has ended
Story views	The profile URL while the story is live	A story that expired, a close friends story, a private account
Live viewers	The live stream URL while the stream is running	A stream that ended, a scheduled stream, a private broadcast
Plays	The public track or playlist URL	A region-locked track, a removed release, a private playlist

A link-format checklist. It contains no market figures.

Story and live orders are time-bound in a way that other orders are not. A story expires, a stream ends, and the delivery window can outlast the target. If you order story views, place the order while the story is live and check the start estimate against the remaining time. A story that expires before the supplier starts is a link that failed, not a panel that failed.

Private accounts

A private account shows its profile and posts only to approved followers. A delivery service that needs to see the account cannot act on it, and an account cannot be followed without approval. The platform's mechanics are the constraint, not the panel's willingness. A panel that accepts a private-account order is either planning to refund it or planning to mark it complete without a delivery.

Make the account public before you order, and keep it public until the order is settled. If the account has to be private for privacy reasons, use a separate public account for the campaign, or accept that the order cannot be delivered. There is no setting that lets a supplier follow a private account without approval, and a panel that claims otherwise is describing a workaround that the platform can close.

Private posts have the same problem. A like or comment order on a private post cannot be delivered by a supplier that cannot see the post. The order may be accepted, then fail, then refund. The refund is the good outcome. The bad outcome is an order marked complete against a count that never moved.

Hidden, deleted and expired content

Content can disappear after the order starts. A post is deleted, a video is made private, a story expires, a live stream ends, an account is renamed. The supplier's queue still holds the order, but the target is gone. A fair panel refunds the undelivered share when the supplier reports the remains. A panel that marks the order complete after the target disappears is charging for units it could not have delivered.

The practical rule is to keep the target stable for the delivery window. Do not delete the post, do not change the account to private, do not rename the account, and do not end the live stream until the order is complete. If the target has to change, tell support before the change and ask for the order to be cancelled or paused. A message before the change is easier to settle than a ticket after it.

URL hygiene

A clean URL is the one the platform serves, with no decoration. Remove tracking parameters, share tokens and fragments. Resolve shorteners before you paste the link. Check that the URL opens the target in a private browser window with no session, because that is a close test of what the supplier sees.

Usernames change. A profile URL built from an old username may redirect or fail. If the platform exposes a numeric id, keep it in your record and use the current URL in the order. The id is what lets you find the account after a rename, and it is what makes a retry safe.

Do not send a screenshot of a link. A screenshot is not a URL, and support cannot pass it to a supplier's API. Do not send a link that only works on your phone because of an app session. The test is a logged-out browser on a desktop, with the link pasted as text.

Time-bound links

A story and a live stream are links with an expiry. The delivery window can outlast the target, and when it does, the order has nothing to deliver to. Place a story order while the story is live, and check the start estimate against the time the story has left. Place a live order while the stream is running, and keep the stream running until the order completes. A scheduled stream is not a live target.

If the target expires before the order starts, the order should be cancelled or refunded. The panel's policy decides which. The practical step is to tell support before the expiry, not after. A message that says "the story expires soon, please cancel or start now" gives the panel a choice it can act on. A message after the expiry gives it a dispute.

When a link changes after payment

A link can change for reasons that have nothing to do with the order: a username is edited, a post is re-uploaded, a video is replaced, an account is renamed. The supplier's queue still holds the old identifier. The order may follow the redirect, fail, or deliver to the new target if the platform keeps the same id.

Tell support as soon as the change is known. Send the order id, the old link and the new link. Ask whether the order can be re-pointed or should be cancelled. A panel that can answer with the supplier's own rule is a panel that can see the order. A panel that says "it will be fine" is guessing, and the guess is yours to carry.

Keep the old and the new link in the manifest. The pair is the record if the delivery is disputed, and it is the reason the identifier column exists. A URL can change; an id usually does not.

What a panel should never ask for

A panel needs four things to place an order: the public link, the service, the quantity and the payment. It does not need your password, your two-factor code, your recovery email, your session cookie, or access to your account. A request for any of those is a request for control of the account, not for a delivery address.

The same boundary applies to support. A support agent who asks you to install a remote-control tool, to read a code from your authenticator, or to sign in on a page they sent is asking for something no delivery requires. Decline, and move the order to a panel that works from public URLs. If you have already shared a credential, change the password, revoke the sessions and enable two-factor authentication before you do anything else.

Privacy is also a data question. A panel stores the links you order against, the quantities and the payment records. That is normal for an order. It should not store a password it never needed. Read the privacy page before you deposit, and keep the order history in your own manifest so a panel closure does not erase your record.

Platform	Services	Categories	With refill	Avg start
Instagram	790	165	29138	3 min
Other	655	243	6430	3 min
Facebook	625	185	15088	4 min
YouTube	570	154	42804	3 min
X	454	164	4576	3 min
TikTok	346	44	33900	3 min
Spotify	235	7	23965	4 min
Telegram	208	44	3669	3 min
Reddit	130	116	1030	3 min
LinkedIn	109	85	90	2 min

Read from the Talon catalogue when the page is rendered. Average start is the mean of the start estimates on active services, in minutes. It is a catalogue figure, not a promise for a specific order.

The catalogue has 4,571 active services across 20 platforms and 1502 platform and category pairs. 1 of those services carry a refill flag. The size of the catalogue is not a reason to trust a link format. It is a reason to check the format before you assume the panel will catch it.

A five-minute check before you pay

1. Open the link in a private window. No session, no app, no login. If it asks for a login, the link is not public.
2. Match the link to the category. Profile for followers, post for likes, video for views, channel for members. A profile link on a like order is the wrong target.
3. Remove the decoration. No tracking parameters, no fragments, no shorteners, no trailing slash.
4. Check the target is live. The post is published, the story has not expired, the stream is running.
5. Keep the target stable. No delete, no rename, no private switch until the order is settled.
6. Send the public link only. No password, no code, no session, no recovery email.
7. Record the link and the order id. The pair is the record you need if the delivery stops short.

The check is shorter than a support ticket and it catches the failures that look like panel problems. A public link, the right format, a live target and a stable window: that is the whole delivery address.

For the account-safety side of the same boundary, read keeping the account you are growing safe while you buy. The privacy policy describes the data an order leaves behind. To see the categories and their link types, open the full catalogue or the guided order flow.