See which seats carry five people.

TrustSig Pro profiles the device population behind every account, scores what one person cannot physically produce, and hands you the breakdown.

Talk to an expertSee how it works
Score and confidence per accountFull device breakdownNo extra call to make
Concurrent sessions on one seatu_2274SharedtodayTeam plan, 1 seat4 countries28-day window
78/100Sharing score, high confidence
Device population
Berlin, DEdesktop214
Hamburg, DElaptop96
Lisbon, PTlaptop88
Kraków, PLdesktop61
Manila, PHlaptop44
Too far apart to be one person

One paid seat, five devices using it.

Already in production

Publishing platforms, fintech and national charities across Europe already run TrustSig on their forms.

PublitPrint-on-demand and digital book distribution for publishers.Publishing · SwedenLEI SystemOfficial Legal Entity Identifier registration agent.Fintech · EstoniaDisability Sport WalesNational charity for inclusive and disability sport.Charity · Wales
And many more across Europe
Case studyHow LEI System eliminated API abuse & form spamRead the case studyAPI abuse, eliminatedZero false positivesLive in five minutes
01The signal

Owning three devices is not sharing

Device count alone flags your best customers. TrustSig Pro scores the shape of the device population instead, and whether two live sessions are physically possible.

01Impossible concurrencyTwo sessions minutes apart, from cities too far apart to travel between. It is the one signal a customer cannot explain away.
02Population shapeDevice count weighed against your own user base rather than an arbitrary threshold, so a normal number for your product stays normal.
03RotationHardware appearing and disappearing on a rhythm that reads like a credential being passed around, not a person upgrading a laptop.
04ConfidenceEvery score is reported with the confidence behind it, so you can act on the unambiguous cases and leave the rest alone.
02Policy

The report is the product

Sharing is report-only until you turn enforcement on. Cutting off a paying account is a commercial call, not a detection one.

  • Scores ride along on the logins and actions you already send, with no extra call.
  • Pull the full device breakdown for one account whenever you need the evidence in front of you.
  • Enforcement, when you enable it, routes those sessions to a step-up you control.
  • Thresholds are per project, so a family plan and a per-seat contract are judged differently.
server.tsreport
// Rides along on the events you already send.const e = await pro.submitEvent({  kind: "login",  user_id: user.id,  request_id: v.request_id,});
e.sharing;   // { score, confidence, devices, reasons }
// Or ask for one account on demand, with the full breakdown.const report = await pro.getSharing(user.id);
03What to do with it

Turn sharers into seats

Most shared accounts are demand you have not priced yet.

  • Every account carries its device history, so a claim can be checked rather than asserted.
  • Scores carry their confidence, so only the clear cases need a human at all.
ent_9a71c204
Mar 04First seen
May 19Second account
Jul 02Fingerprint rewritten
Aug 11Humanizer detected
Trust
84 → 21
Sessions
412
Accounts on this deviceyour user IDs
u_4821signed up 04 Maru_990719 Mayu_1105802 Julu_30474banned 11 Augu_4829114 Aug2 more, joined this month
Upgrade promptsRoute the heaviest sharers to a team-plan offer instead of a lockout, and measure how many convert.
Seat conversationsWalk into a renewal with device counts and countries rather than a suspicion about headcount.
Quiet re-authSend only the unambiguous cases to a second factor, so the household with three laptops never notices.
Licensing proofReport shared viewing to the partners whose contracts depend on it, with the evidence attached.

See how much of your base is sharing one seat.

Talk to an expert
04 Questions

Account sharing, answered

The sharing engine profiles each account's device population: how many devices, how fast they rotate and how far apart they sit. It also looks at sessions overlapping in ways one person cannot produce. You get a score, a confidence and the device breakdown behind it.

No. Sharing is report-only unless you enable enforcement in policy, and even then it maps to REVIEW rather than a block. What you do with the report, an upgrade prompt, a seat conversation or a re-authentication, is your call.

Owning several devices is ordinary and scores low. The score moves on concurrency geography rules out, device counts unusual for your population, and rotation that looks like a shared password. Confidence comes with it, so you can act only on the clear cases.

Sharing scores ride along on the login and action events you already send. A per-account report is there on demand when you want the full device breakdown.

The detection is the same either way. B2B teams take the report into renewal conversations with real device counts. Consumer products route heavy sharers to a step-up or an upgrade prompt.

05More of the platform

Ask the same platform a different question

Every page below runs on the same telemetry, the same device identity and the same detection catalog.

01Spoofed devices & ban evasionA new fingerprint is not a new device.Anti-detect browsers02Multi-account & alt detectionName the account it is an alt of.Linked accounts03Account takeover protectionScore the login against the account's own history.Login risk04Scams & social engineeringCatch the session the real owner did not start.Coached approvals05Signup & trial-abuse protectionMatch a new signup back to the machine behind it.Serial signups06Bots, scrapers & AI agentsSort the crawler from the scraper from the human.Automation evidence07Privacy & data architectureNo cookies. Not one.Cookie-free
06Get started

Measure the sharing in your own base

Tell us how your plans are priced and where sharing hurts. We will reply by email to set up access for your team.

  • EU-hosted and GDPR-native
  • Cookie-free device identity
  • Training mode before anything enforces