How to write a one account per person policy
Miss repeat accounts and you pay for them. Block a real customer and they leave. Sample wording, fair exceptions and how to enforce the policy.
How much runway do we actually have? Your bank balance on the morning of the 3rd is $61,400, and the spreadsheet open beside it says you spend $12,800 a month more than you earn, which gives you 4.8 months ($61,400 ÷ $12,800). You'd planned to bring on a contractor in January at $4,000 a month. With them, 4.8 months becomes 3.7 ($61,400 ÷ $16,800), and you've got a call at 10 a.m. to decide if you can afford that.
So you trace the money backwards, looking for something to cut. This is a scenario, so redo the arithmetic with your own numbers.
Your biggest bill is your model provider, at $9,300 last month. When you export usage by account, $6,510 of it came from 3,100 free accounts at $2.10 each. You sort that list by email, and the same names keep coming back with a dot moved or a plus and a number on the end. By 9:15 a.m. you've counted 640 accounts that seem to belong to about 40 people.
- 640 accounts × $2.10 = $1,344 a month
- $1,344 × 12 = $16,128 a year
- $1,344 ÷ $29 = 46.3, so 47 customers on your $29 plan are paying for those 40 people
Your terms do mention this, in one line from a launch template that says users may not create multiple accounts. So you open a new doc, type one account per person policy at the top and start to feel better. Then you open last month's cancellations.
One row is a design agency on your $149 plan, and the reason field is empty. Nineteen days before they left, a new hire tried to sign up from their office, and the one-account-per-IP limit you added last spring told them an account already existed on this network. Nobody wrote in. The first you've heard of it is this row.
That's $1,788 a year ($149 × 12). To make up for it, your limit would have to stop 71 repeat accounts for a full year (71 × $2.10 × 12 = $1,789). There are 11 more blank reasons on the list, and you'll never find out how many had the same story.
Add the two you can see and you get $1,493 a month ($1,344 + $149), or $17,916 a year. At $12,800 a month, that's 1.4 months of runway. It's 9:48 a.m. You can tighten the rules and risk losing the next agency, or loosen them and keep paying for 40 people, and all you have to go on is one line from a template.
Why "one account per person" is harder than it sounds
Your database stores accounts, and a person is something you have to work out. Real people have two accounts for good reasons, like a work login and a side project. Different people look alike, like 40 colleagues behind one office connection. Meanwhile one person with 16 accounts looks, row by row, like 16 strangers.
The obvious fix is to write the rule down and enforce it hard. Nobody reads the sentence in your terms, so writing it stops no one, and a hard rule gets wrong answers in both directions.
Run it with illustrative numbers. Say a strict rule blocks 200 accounts a month, saving $420 (200 × $2.10). Say 5 of those 200 were real people who'd have paid $29 a month. Each month you give up another $145 of monthly revenue (5 × $29). By month three that's $435 a month, already more than the rule saves. By month twelve it's $1,740 a month, before any churn. The saving shows up on an invoice, and the lost revenue shows up nowhere.
Strictness and support work tend to rise together. What breaks that link is writing down the exceptions, so the easy cases never reach your inbox.
How to write a one account per person policy
Put the limit on the benefit. You're paying for the second free trial. A second account with nothing free on it costs you almost nothing, so "one free plan per person" is the rule to enforce.
Say who counts as one person. Is it one human or one company? If a business with five employees gets one trial, say so, and decide where the limit sits.
List the exceptions, so support doesn't have to invent them.
- A work account and a personal account, if only one is on the free plan
- Colleagues at one company, each with their own login
- Families, offices and campuses sharing a connection
- Customers coming back after a long gap, after a set number of months
- Someone locked out of an old email address, who gets their account moved and no new benefit
Say what happens when someone goes over. Start with the smallest step: hold back the free benefit on the newer account and tell them why. Save closing a free account for repeated, deliberate cases. Leave paid access and the person's work alone unless you've warned them first.
Give people a way to tell you you're wrong. The agency never wrote in, so put the appeal one reply away from the refusal, promise a person will read it and name a time limit. How you word the refusal matters too.
You can adapt the wording below. It's written for customers to read, so have your own lawyer check it before you publish it or add any of it to your terms.
Sample policy
One free plan per person. Each person can use our free plan once and start one free trial. Please don't create extra accounts to get more free usage.
What's fine. You can have a separate work account and personal account, as long as only one is on the free plan. You can have as many paid accounts as you need.
If you go over. We'll hold back the free benefit on the newer account and tell you why. We won't delete your work without telling you first, and your paid plans won't change.
If we got it wrong. Reply to the message we sent you. A person will read it and answer within two working days, and if we made a mistake, we'll fix it.
How to enforce the policy without losing customers
Enforce at the moment the benefit is claimed, and let the account exist. A refused trial on a live account costs you one conversation. A refused signup costs you a customer who never tells you. Publish the policy first, apply it to new claims from a stated date, and deal with old duplicates separately.
Send every grant through one server function that writes down who got what and when. Once a month, count your appeals and how many you overturned. If you're overturning a lot of them, the rule is wrong.
The basic checks behind the policy, and how each one breaks
That chart leans on one box: "had it before, on your records?" Your records know accounts, so most teams add checks to answer it for people. Each one catches something real, and each one quietly rewrites your policy.
| Basic check | Catches | Misses | Wrongly blocks | Upkeep |
|---|---|---|---|---|
| Email verification | Mistyped and dead addresses | Anyone with a second inbox | People whose code goes to spam | Deliverability work |
| Unique emails | One address used twice | Every other address | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | Domains not on your list yet, and ordinary mailboxes | People who use privacy forwarding | A list that's never finished |
| CAPTCHA | Simple scripts | People signing up by hand | Screen reader users, people on privacy tools | Fees and lost signups |
| Phone or card requirement | Casual repeat accounts | Anyone with another number or card | Students, people without a steady mobile number | Text fees and fewer signups |
| One account per IP | Repeats on one connection | Any other network | Offices, campuses, households | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Addresses off your list | Privacy-minded people, staff on company VPNs | Another list to maintain |
| Rate limits | Bursts from one source | Slow, spread-out signups | Busy offices | Tuning by route |
| Usage caps | One account overrunning | The fresh cap on every new account | Heavy honest users | Deciding where your product stops |
| Shorter trials | Some cost per account | More accounts make it up | Every honest user | Fewer people reach paying |
| Manual review | What a person can spot | Nights, weekends, anything spread out | Whoever looks odd to a tired reviewer | Hours every month |
Gmail ignores dots in standard addresses, so jane.doe@gmail.com and janedoe@gmail.com reach one inbox. Mail to janedoe+notes@gmail.com lands there too. That's how email works.
Now read the table as policy. A one-per-IP limit says one account per office. A phone requirement says one per phone number. Neither is the sentence you published, and both will land on someone your exceptions list says is fine.
Reviewing by hand doesn't get you out of it. Those 640 accounts at three minutes each come to 1,920 minutes, or 32 hours, before next month's signups arrive. That's most of a working week spent reading email addresses.
Keeping the promise your policy makes
Your policy talks about people, and everything in that table talks about inboxes, numbers and IP addresses. AbuseZero exists to tell you whether a claim should go through, and it's very good at it. Before you grant a trial, a free plan or a batch of credits, your server makes one API call and gets back a clear allow or deny. You get multi-layer AI risk analysis that examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. AbuseZero uses a proprietary algorithm, with AI that checks the claim again.
The one-per-IP limit counted an office as one person, while AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Your email rules ran out at the next address. AbuseZero checks mailbox aliases, disposable domains and mail routing, and it recognizes repeat devices across new accounts, even when email addresses keep changing. Creating a fresh account isn't enough to erase previous activity.
You don't have to build your own abuse prevention system. The wording stays yours and so do the rules. Observe mode shows you what would be denied before anyone is blocked, so you can try a stricter rule without betting another $149 customer on it. The quickstart protects your first benefit.
Frequently asked questions
Can I ban multiple accounts in my terms?
That depends on where you and your customers are, so ask your own lawyer to check the wording. This post isn't legal advice.
Should a one account per person policy ban second accounts outright?
Usually not. Limit the free benefit and let people keep a second account that doesn't use one. Account sharing is a different problem with a different fix.
What about accounts that broke the rules before the policy existed?
Publish the policy and apply it from a stated date. For older accounts, stop the next free grant and leave their existing work alone.
Put your policy to work
Start with Builder
Pay as you go. Protect your first benefit today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.