Most product vendors are forced to use a full membership script or plug-in - even for simple products
Whilst membership systems have their place, they tend to be
Quite apart from all that, they are total overkill for a small product.....
They are designed for multi-tiered continuity sites rather than just protecting a single page with a download link on it.
That's it! All done in less than 30 seconds!
Also...think about this...
The vast majority of support tickets are "access related" issues.
Typical ones include...
"I can't remember my password"
"I can't remember which email address I used"
"I didn't get the log in details email"
Or...the IPN didn't fire and the system screwed up!
It's time to say "goodbye" to time sucking support tickets!
To get a fully fledged membership script or plug-in does cost a lot of moolah, though...
I should know. I have one that costs $167 and one that costs $297 a year!
But those are expensive because they handle all sorts of membership site stuff like membership levels, dripped content, inbuilt affilate systems, autoresponders and so on...
Total overkill for someone who just wants to protect a couple of download pages for a product, right?
Well, The GOOD NEWS is that you DON'T need to shell out $297 or even
$197 to stop the thieves!
To your success
Is there an OTO?
No. There is no OTO.
Will the link work with a cloaker?
I have only tested with the systems I use and it works great. It is not recommended, though, as it would not be as secure.
What are the terms for the developer license?
Basically, you are not allowed to sell the plug-in. You can install it on unlimited domains that you own and on sites you are building for or selling to someone else.
Is this totally 100% secure?
Nothing is 100%. Even if you have a full membership site, people can pass around log-ins or re-upload your product. This is no less secure than other methods and they all serve to discourage thieves who tend to go after the easy pickings.
What happens if people clear their cookies?
If they do and they click the bare link, they will be sent to the "Ooops" page. That is why it's important you give them instructions to access the site through the original link so they are re-cookied.
Are there any known conflicts?
Your hosting needs to be running at least php 5.6 (most are). It will not protect pages made with Thrive Landing Pages (other popular page builders like Instabuilder 2 work fine)