Use casesSaaS, communities and consumer apps
Keep sign-ups, offers and votes for people
Check for a person at sign-up, at offer claims and when content is posted, without a puzzle in the way.
Request
Free trial claimed
A new account claims promo credits
When scripts sign up, your numbers stop meaning demand.
Automated sign-ups claim free credits, flood reviews and inflate engagement. Puzzles slow down everyone. HEIP checks the action quietly and lets your app add a step only when it's needed.
Why now
200 automated trial accounts × 10,000 free credits = 2,000,000 credits given away.
What you get
- Free tiers and offers that go to people
- Because HEIP checkswhether a person was in control when the sign-up or claim happened
- Cleaner sign-up and engagement numbers
- Because HEIP checkseach protected action, with a decision you can record
- No puzzle for real users
- Because HEIP checksquietly, in the background
- A CAPTCHA only when it's needed, if you keep one
- Because HEIP checksand answers step up so you can show it to that session only
Actions to protect
| Action | Suggested policy | On step up, you usually |
|---|---|---|
| Sign-up | Standard | Verify email, or show the CAPTCHA you already have |
| Claiming a trial or promo | Standard | Verify email or card |
| Posting, messaging, reviewing, voting | Standard | Hold for review, or ask to try again |
| Reading and browsing | Observe | Nothing: observe only, never blocks |
Policies are named presets you set per action. Critical asks for the most evidence. Fast suits frequent actions that still matter. Standard fits everyday actions. Observe never blocks.
Where it fits
HEIP's step-up can decide when to show the checks you already have, so most people never see them.
Works alongside
- Your sign-up flow
- Email and card verification
- Any CAPTCHA you keep
- Moderation and review queues
Roll it out on sign-ups and trial claims
Baseline
Pick sign-ups and trial claims. Note how they're protected today.
Observe
HEIP decides on real traffic but blocks no one.
Compare
Review its decisions against what you already know.
Enforce
Turn it on for sign-ups and trial claims only if it earns it.
Most teams go from observe to enforce in 6 to 8 weeks. Observe mode blocks no one while you compare. How onboarding works
Questions
Do we still need a CAPTCHA?
Not necessarily. If you keep one, show it only when HEIP answers step up, so most people never see it.
Does HEIP stop abuse across many accounts?
HEIP checks each protected action, like a sign-up or a claim. It doesn't analyse accounts, usage or billing data.
Will real users notice anything?
No. There is no badge, pop-up or delay. Your app only adds a step when HEIP isn't sure.
Should we protect reading and browsing?
Use the Observe policy there. It records what HEIP sees and never blocks, so browsing stays untouched.
Trust has to move with the action.
When digital actions can be automated, trust must move with them.