How to stop browser extension free trial resets
Browser extension free trial abuse takes the capacity paying customers rely on. Move trial state to your server and see which basic fixes break.
You've pressed Rewrite on your own extension five times now, hoping the next one comes back. The congratulations are still sitting in another tab, because yesterday's newsletter feature brought 3,000 installs of your AI writing extension, your best day by a distance, and every one of those people started your 7-day free trial. Then the working day started, and at 8:00 your Rewrite button stopped coming back.
Take this as a scenario, and swap in your own numbers. Your model provider allows 1,000 requests a minute, and each new install sends about 10 rewrites an hour, which adds 500 requests a minute. At 8:00:
900 paying seats 400 requests a minute
3,000 new trials 500 requests a minute
Older trials 300 requests a minute
Total demand 1,200 requests a minute
Provider limit 1,000 requests a minutePaying customers are standing in that same line, and it grows by 200 requests every minute. By 8:30 that's 6,000 waiting, a 6-minute delay. By 9:00 it's 12,000 and 12 minutes. By 10:00 it's 24 minutes.
At 9:02 a message arrives from your biggest account, an agency with 40 seats at $12: "Rewrite has been spinning for 9 minutes for my whole team. Are you down?" You aren't down. Your capacity is being spent on people who haven't paid you, and the customers who fund all of it are getting the slowest service you've ever given them.
So you run a query you've never had a reason to run: trial IDs that first reached your server more than 7 days ago. The trial lasts 7 days, so the answer should be zero. It comes back with 1,500, each sending about 12 rewrites an hour, which is the 300 requests a minute above (1,500 × 12 ÷ 60). The oldest first appeared in June. It's November. Its extension says it's on day 3, because the extension is where you keep the date.
This is what browser extension free trial abuse looks like from the inside. Take those 1,500 out and the launch fits: 400 + 500 = 900 requests a minute, with 100 to spare, and nobody sees a spinner. They've been costing you on quiet days too. At $0.0005 a request, across a 10-hour busy day, 300 requests a minute is $0.15 a minute. That's $90 a day (600 minutes × $0.15) and $2,700 over 30 days.
Your 900 seats bring in $10,800 a month (900 × $12), so a quarter of your revenue has been serving trials that should've ended months ago. Over a year that's $32,400, or about 1.6 months of runway if you spend $20,000 a month.
By 11:00 you've refunded a month for 60 seats ($720), and the agency, worth $5,760 a year ($480 × 12), wants a promise this won't happen again. Yesterday's 3,000 new people met your product through a 12-minute spinner. Say 3% would normally have paid. That's 90 seats and $1,080 a month, and most of them won't give you a second look.
You could ask your provider for a higher limit, and then you'd be paying more so the 1,500 can carry on. By lunchtime there's a draft open on your screen that begins "We're ending our free trial." That trial brought in nearly all of your 900 seats.
Why browser extension trials don't hold
A web app keeps its trial logic on your server. An extension gets delivered to the customer: your code, its storage and the clock it reads all sit on a machine you don't control. A 7-day limit enforced in there is really a request, and most people will honor it. Your capacity depends on the ones who won't.
It's tempting to hide the trial date better by encrypting it or obfuscating the code. That adds effort for a while, but the key ships in the same package as the code that reads it, so you're keeping a secret from the person you handed it to. Tracking the trial on your server against a random install ID gets closer. The ID still comes from the extension, though, so all your server learns is that it hasn't seen this one before.
The fix is to move the decision somewhere the extension can't reach.
How to move trial state to your server
Ask people to sign in before the trial starts. Anyone can install and look around. The trial begins at sign-in, because your server needs an identity it issued itself and can revoke.
Create one trial record per account. With the account as the primary key, a second trial on that account can't exist.
create table extension_trials (
account_id uuid primary key,
ends_at timestamptz not null,
allowance integer not null,
used integer not null default 0
);
update extension_trials
set used = used + 1
where account_id = :account_id
and now() < ends_at
and used < allowance
returning allowance - used as remaining;Decide on every request that costs you money. The extension sends its token and nothing else about the trial. Run that update before you call your model, and if no row comes back, don't make the call. The test and the count are one statement, so two requests at once can't both take the last rewrite.
Keep a local copy for display only. The extension can cache "4 days left" to draw a badge. If that's ever wrong, the worst outcome is a wrong badge.
Reserve capacity for paying customers. Split your provider limit into two queues, say 600 requests a minute for paid accounts and 400 for trials. A surge of trials can now only slow down trials. Put a hard spending cap on free users next to it.
Cut over the old versions. Pick a date, show a sign-in prompt in the current version, tell paying customers first, and then refuse any request without a token.
Run that morning again with this in place and demand is 900 requests a minute, against a limit of 1,000.
The basics that guard a new account, and how they break
Your server now knows whether an account is still on its trial. It can't know whether the person behind a new account has already had one, because a new account has no record and the insert goes through. At 7 days a trial, a free month takes five accounts (30 ÷ 7 = 4.3, rounded up), so those 1,500 people would need 7,500 accounts a month. Attention moves to the sign-in form, and most teams add these basics.
Start with email, because it looks solved. A unique-email rule compares strings, and one mailbox can have many of them. Gmail ignores dots in personal addresses, and it delivers name+anything@gmail.com to the name@gmail.com inbox. That's how email aliases work.
| Basic fix | Catches | Misses | Wrongly blocks | Cost to keep working |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any second real inbox | People whose code lands in spam | Deliverability work |
| Unique emails | The exact address twice | Any address written differently | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains, ordinary mailboxes | People using privacy forwarding | A list someone updates forever |
| CAPTCHA | Simple scripts | People signing up by hand | Screen reader and privacy tool users | Fees and lost signups |
| Phone requirement | Casual second accounts | Anyone with another number | People without a reliable mobile | A charge for every text |
| Card requirement | Casual second accounts | Anyone with another card | Students, people who want to try first | Fewer installs becoming trials |
| One per IP address | Repeats on one connection | Any other network | Whole offices, where extensions often live | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Anything off your list | Staff on company VPNs | Another list to maintain |
Rate limits and usage caps belong on your server whatever else you do, and they'll catch one account running hot. They count per account, though, so five accounts each under the limit look fine (what each one stops). Set them low and they hit a real customer mid-task, and someone has to keep tuning them.
Shorter trials cut what each account costs you. But a 3-day trial just means a free month takes 10 accounts (30 ÷ 3), and every honest user loses 4 days they may have needed before paying.
Manual review catches what a person can spot. At a minute per account, 7,500 accounts is 125 hours a month, about three working weeks, and the reviewer will still turn away someone real who just looks odd on a tired afternoon.
Put all of it on the form and someone who just clicked Install has to confirm an email, solve a puzzle, type a phone number and add a card. The lists go stale, the exceptions pile up, and the question you needed answered is still open: has this person had this trial before?
One answer before the trial starts
Your trial record now knows everything about an account and can't say whether this claim looks like a repeat. AbuseZero is built for exactly that, and you don't have to build your own abuse prevention system to get it. Where your email rule compares strings, AbuseZero checks mailbox aliases, disposable domains and mail routing. Where your IP limit sees one address, it sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. You get multi-layer AI risk analysis that examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and every row in that table is a single check. Signals are read together, never one at a time. There's also a proprietary algorithm, with AI that checks the claim again. AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing, and creating a fresh account isn't enough to erase previous activity.
You keep the server-side trial you just built. Before it starts a trial, your server makes one API call and gets a clear allow or deny, under rules you control, such as once per user or once per rolling number of days. Observe mode shows you what would be denied before anyone is blocked, and the quickstart protects your first benefit.
Frequently asked questions
Can I keep trial state in the extension if I encrypt it?
Not safely. The key ships with the code, so encryption only adds effort. Use local state to draw the interface, and let your server decide.
Does an extension with no server costs need this?
Less urgently. If every feature runs on the user's machine, a repeat trial costs you a sale and no capacity, and you might accept that. Once a feature calls something you pay for, move the decision to your server.
How do I turn someone away fairly?
Say the trial has been used, and offer a paid plan and a way to reach you, because some of those people will be real. Here's wording you can use.
Give your capacity back to the people who pay
Start with Builder
Pay as you go. Evaluate your first claim today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.