How this shop is run, from the order to the refill
What happens to an order, what we keep, and what we cannot do. The numbers on this page are read from the live catalog and the code that runs the shop, not typed into it.
51
services on sale
12
networks covered
0
passwords requested
2
can be paced over time
The route an order takes
Five steps, and nothing waits in a queue
- 01
Pick a package step
One quantity on one service page. The price beside it is the price you pay.
- 02
Paste a public address
A link or the username it sits on. That is the whole input; there is no login.
- 03
Pay by card or coin
On the provider's own page. Nothing moves until the payment has confirmed.
- 04
Processing
The items go out the moment the payment clears. No batching, no line behind other orders.
- 05
Delivered
The order page turns to Delivered, and the refill window opens where the service carries one.
The check before you pay
Twelve networks, two levels of certainty
Resolved on screen
8The address is followed through and the profile, post, track or channel comes up before you pay, so you see what the order is about to go against.
- TikTok
- YouTube
- Telegram
- Spotify
- SoundCloud
Format and reach only
4These four block every public read a shop could honestly use. The address is checked for shape and reachability, and you confirm the target yourself.
- Twitch
- Kick
What is on file
What we keep, and what never reaches us
Kept, per order
- What you ordered, and the package step
- The public address each item went to
- The name and email the confirmation goes to
- A hashed IP and a shortened browser identifier, for fraud checks
- The order ID, its status and its payment state
Never on file
- A password, for any account, ever
- The card number: it is typed on the payment provider's page
- A wallet key or seed phrase: the coin transfer happens in your wallet
- A customer account: there is none to sign in to
- Your private messages, insights or analytics
The order page
Three readings, and nothing invented between them
The heading is your order ID. Below it sits one status with three possible readings, how the order was paid, whether that payment has confirmed, and a row for each item with the address it went to. There is no delivery clock on it, because we do not have one to show.
Order
MF-2K7Q-4A
Payment pending
The order exists and waits for the payment to confirm.
Processing
Confirmed and sent out. Counts are landing on the targets.
Delivered
Every item has landed. Refill window open where offered.
Numbers we publish
$1
minimum order
Smaller totals are topped up and itemised before you pay.
24h
support answers within
The only response figure we publish, and the one we keep.
30 days
refill window
Where a service carries a refill, a slipped count goes back up at no charge.
2
services with paced delivery
Spread over six hours to four days instead of landing at once.
In our own words
One public address is the whole input
Every service here is ordered the same way. You pick a package step on the product page, then paste in the public address itself: a link, or the username that link sits on. That is all we take. No sign-in on our side, nothing to approve in an app, no permission screen.
It is a decision about what we are willing to hold, not a feature we bolted on. An address is something you can hand to a stranger without losing anything, and it is all the work needs. Nothing here was built with a place to put a password.
The cost is that the address carries the order alone. We work against what you paste, so a mistyped handle that belongs to somebody else takes the count instead of you. Each page names the kind of address its service needs, and the full list of services holds all fifty-one.
What happens between the payment and the count
Payment is by card or in cryptocurrency, picked at checkout, and nothing moves before it confirms. Until it does, the order sits at Payment pending. How long it takes is the network's business rather than ours, and no clock for it appears anywhere here.
Once it confirms, the order turns to Processing and the items go out. Nothing waits in a line behind other orders and nothing is held for a batch window. The count you bought goes out in one run, and a line that has landed reads Delivered.
Two services can work differently, and only because their own pages offer it. On Instagram views you can set a window and have the count released across it. TikTok views carries the same control. It exists nowhere else: not on other product pages, not in the cart, not at checkout.
What the order page prints, and the fields we left off
Its heading is your order ID. Below it sits one status, and it has only three readings: Payment pending, Processing, Delivered. Then how the order was paid and whether that payment has confirmed, then the amount.
Each thing you bought gets a row underneath, carrying the service name, how many of it you ordered, the address it is going to, what that line cost, and a small label reading Processing until it reads Delivered.
There is no percentage on that page, no bar filling up, no stage counter and no finishing time. A progress figure is a number somebody chose to display; a countdown is a promise made before the work is done. We would rather the page said less and every line on it were true.
The check that runs before you pay, and its ceiling
Confirm your target and the shop looks at the address. Eight of the twelve networks are read properly: Instagram, TikTok, Twitter, YouTube, Reddit, Telegram, Spotify and SoundCloud. There the address is followed through and the profile, post, track or channel comes up on screen, so you see what your order is about to go against.
Facebook, LinkedIn, Twitch and Kick get less than that, and saying so beats letting a tick mark suggest otherwise. On those four the shape of the address is checked and the name is lifted out of the path. Nothing is fetched.
Either way the check ends at the address. Whether a profile is private, whether comments under a post are closed, whether the post is still up: none of those states reaches it. A failed check does not stop you either: the address stands as a manual entry. The last look belongs to you, so open the target yourself and confirm it is public, still up and still able to take what you are ordering.
What we keep on file
What you ordered, the address you ordered it against, and the name and email the confirmation goes to, plus a hashed form of your IP address and a shortened browser identifier that we keep for fraud checks.
No password of yours sits on file, because there is no customer account here to have one. The card charge and the coin transfer both happen on the payment page, so what reaches us is the outcome of a payment, not the details behind it.
The footer switches the display between US dollars, Canadian dollars, Australian dollars and pounds. Where a cart comes to less than a dollar, the top-up to that minimum appears as its own line in the summary while you can still see it, not after paying. Accepted payments takes the money side further.
When a count slides back down
Where a refill is offered on a service, a number that has fallen back within 30 days of delivery goes on again at no cost to you. Tell us the order ID and what the count reads now. The Money-Back Policy sets out which situations end in a refill and which in money returned.
Nobody tells us when a count moves, and we do not offer an account of why. None of us can see how a platform counts or reviews anything, so we do not describe it, and we never tell you a delivered number is beyond a platform's reach.
Nor can we take anything back off a public page. A count that has landed has landed, and no later order undoes it.
Reaching the people who run this
A live order, a target that looks wrong, a number that moved: all of it belongs in an email to support@mrfollows.com that carries the order ID. We answer within 24 hours, and that is the only response figure we publish.
If you would rather read first, the guides cover what each count does on its own network. The tools work out engagement rates, check a link, count characters, open a story and pull a video down, none of it costing anything.
The route an order takes is set out step by step on how it works. The United Arab Emirates is the governing law and the jurisdiction MrFollows answers in.
Something here not clear?
Ask us directly