FREE TRIAL AND CREDIT ABUSE
One trial per person, not per inbox. Recognize the device behind each new trial, whatever email it arrives with.
Free credits attract repeat sign-ups and scripts that farm them. LR Defender recognizes a returning device through cleared storage and new IP addresses, flags the automation, and tells your sign-up handler before credits are granted.
- 01Sign-upChecked here
- 02Credit use
- 03Referral credits
What runs there
- Device ID
- Automation
- Datacenter
Your sign-up handler gets
The playbook
How the abuse works.
Throwaway email.
A new address for every trial.Wiped browser.
Cookies and storage cleared between sign-ups.Sign-ups at volume.
A script repeats the flow with rotating addresses.
What we check
What LR Defender checks at each step.
New email
What we check
The device behind it.
What you get back
The device ID, how many times it has visited, and when it was first seen.
Wiped browser
What we check
Recognized from signals.
What you get back
The same device ID, how the visit was matched, and how closely.
Volume
What we check
Automation signals and datacenter or VPN networks.
What you get back
Whether the checks found a bot, whether the address is a VPN or in a datacenter, and the recommended action.
Try it
Try the clean-slate step on yourself.
Step 1: Scan
Collect signals in this browser and derive a device ID from them.
Wiping really clears local storage for this site in your browser, so sign-in state on this site may be affected. Cookies are not touched.
Step 2: Wipe
Clear this site's local and session storage, for real.
Step 3: Re-scan
Derive the ID again, from signals alone, with storage empty.
Run the scan to list the real keys stored here.
This demo derives the ID from measured signals in your browser, so you can watch it happen. Production matching runs on our servers, with fuzzy matching over the collected signals rather than a single exact hash.
Where to call it
Check before you grant credits.
- 01
Your server
Mint a session token when you render the sign-up page.
- 02
The browser
Call identify() at sign-up and send requestId with the form.
- 03
Your server
Fetch the verdict, and grant credits only after it.
One script tag and two calls from your server.
Policy starting point
A starting point. Tune it on your own traffic.
| Situation | Suggested action |
|---|---|
| Device already claimed a trial in the last 30 days | No new credits, offer the paid plan |
| Hard automation signal | Block |
| Datacenter address or Tor | Challenge |
| Residential proxy unknown | Decide on the device evidence |
Give each person one trial.
After a demo call, we set up your account and email you a link to set your password. It starts with a 90-day free trial on the Pro plan's limits, with no card.