Account fraud

Stop free trial abuse and multi-account signups.

Free trial abuse is one actor opening account after account to keep getting what you give away: trials, credits, free tiers and promo codes. AI agents made it cheap. One prompt can sign up again and again, from a new email and a new IP each time. Heedeo recognises the browser behind each signup and counts how many identities it has already shown you, so the first signup is welcome and the fifth stands out.

Five signups, five emails, one browser. Past your threshold (3 by default), the count is a strong reason on its own.

What free trial abuse looks like now

The classic version is a person with a stack of email aliases. The new version is a script or an agent told to keep signing up. To most signup flows, each attempt is a new customer: fresh email, fresh IP, fresh cookies.

It is not rare. 1 in 6 AI signups tied to multi-account abuse, at some companies, according to Stripe's CEO via Fortune, May 2026.

  • Trial farming: a new account each time a trial ends.
  • Credit and free tier farming: many accounts drawing on a budget meant for one.
  • Promo and referral abuse: one actor collecting rewards meant for many.
  • Fake signups that pollute your funnel, your email sending reputation and your metrics.

Why IP blocks, CAPTCHAs and email checks miss it

Each of these checks one request on its own. Abuse is a pattern across requests. An IP block fails the moment the farm rotates proxies, and it hurts real customers who share an office or a phone network. A CAPTCHA costs a real customer a few seconds and costs a solver service a fraction of a cent. Disposable email lists only catch the lazy: a fresh Gmail address passes every one.

The question that matters is not "is this a bot". It is "have we seen this actor before, under another name".

How Heedeo catches it

  • Recognises each browser that reaches a signup or other action, from a script you serve on your own domain. A browser that clears its cookies is usually still recognised by its characteristics.
  • Counts the distinct emails and accounts each browser has shown you. Crossing your threshold (3 by default) is a strong reason on its own.
  • Checks each email: disposable domains, domains with no mail server, domains registered in the last 30 days, dot and plus aliases of an address already seen, and bursts of generated-looking addresses.
  • Reads the network: cloud datacenter ranges, VPN, proxy, Tor and hosting networks. A privacy network never flags anyone on its own, because many honest people browse that way.
  • Spots bursts: new accounts on one network well above its own norm, and a visitor taking an action far more often than your median visitor.
  • Adds the weights of every reason into a score, and flags the event when it reaches your threshold (100 by default). Every reason comes with one line of plain text.

You decide what happens

Your rules decide what each score gets, route by route: allow, restrict, challenge with a passkey or email link, or block. Real customers never see a puzzle.

Most teams start by logging what their rule would do for two weeks, then refuse only the strongest cases and add a phone or email step for the rest. When you refuse, show a generic message, never the reason, so a farm learns nothing.

On Heedeo's own test harness of synthetic honest users and farms, 1.3% of honest signups were flagged and 94.9% of farm signups were caught (2026-10-26). These are test numbers, not live traffic.

Real customers and their agents still get in

Blocking every agent is no longer safe. Agents now sign people up, compare plans and buy. Heedeo never flags an agent for being an agent: it verifies agents that sign their requests, and only an unsigned claim or a sudden crowd from one operator counts against a signup.

Questions

How do I prevent users from creating multiple accounts?
Recognise the browser behind each signup, not just the email or IP, and count how many distinct emails and accounts it has used. Add email and network checks, and let your rules decide what a repeat gets: a passkey or email step, a smaller share, or a block. Heedeo gives you those signals and a score on every signup.
What if someone clears their cookies or uses incognito?
Heedeo keeps the visitor in a first-party cookie and browser storage, and a browser that clears all of them is usually still recognised by its characteristics, at a confidence your code can read.
Will this block real customers?
Nothing is blocked unless your rule says so. A VPN, Tor or a privacy browser never flags a signup on its own. An agency that manages several clients' accounts from one laptop will show many identities, which is why the threshold is yours to set and an Allow label lets them through.
Does Heedeo work with Next.js?
Yes. You add one script tag served from your own domain, one identify() call in the browser at signup, and one server call with the result. Any server that can make an HTTPS request works.

Take heed. Let's set you up.

Heedeo is ready. Book a 30 minute demo, and we set it up for your site with you.