Paywall and meter bypass
A cookie-based free-article meter resets in a private window or after cleared cookies. A meter keyed on the visitor ID does not.
Meter the content. Not the cookie.
Courses, streaming and news sites run on access: a trial, a free article count, a seat per subscription. Fingerly gives each visitor an ID that survives cleared cookies and private windows, so those limits follow the reader instead of their storage.
- A visitor IDSurvives private windows.
- Paywall metersCount per device, not cookie.
- Shared loginsCount devices per subscription.
- No cookiesNothing written to the browser.
[ 01 / 06 ]Abuse patterns
How abuse reaches education and subscription media.
Education platforms and subscription media share a business model, and so the same abuse: access taken without paying for it, or paid for once and spread across many people.
Account sharing and resale
One subscription used by a whole group, or a login sold on. The number of distinct devices behind one account shows it.
Free trial abuse
Trial after trial under new emails. The device behind them is what stays the same.
Content scraping
Bots that copy courses, articles or video catalogues. Driven browsers and declared scrapers are reported without a captcha.
Account takeover
Stolen logins resold or used to access paid content. A device the account has never used is worth a second check.
Promo and student-offer abuse
Discounted or free offers claimed again and again under new accounts. Repeat claims are visible per device.
[ 02 / 06 ]Pattern to decision
From pattern to decision.
Fingerly does not proctor exams or watch what a learner does inside a course. It describes the device and the network, so access limits can be enforced fairly.
01
Metered content
A meter that follows the reader.
Count free articles or lessons against the visitor ID instead of a cookie. Incognito is reported as the reason a reader looks new, and it is context rather than a verdict.
- Check at
- Article viewsLesson starts
- Reads
- Visitor IDIncognito modePrivacy settings
02
Shared subscriptions
Offer a plan, do not just block.
Count the distinct devices that use one subscription at login or when playback starts. Past the limit you set, offer a household or team plan. Location mismatch and VPN signals alongside many devices make a better reason to ask than any one alone.
- Check at
- LoginStarting playback or a session
- Reads
- Visitor IDLocation mismatchCommercial VPN
03
Repeat trials and offers
Connect the fifth trial to the first four.
Identify when a trial or discount is claimed and store the visitor ID with the account. A returning device asking again is worth a look before access is granted; asking for a card is gentler than refusing.
- Check at
- Trial startOffer redemption
- Reads
- Visitor IDNew or returningIncognito mode
04
Content scraping
Spot the script, welcome the learner.
Scrapers run on driven browsers and hosting networks. Read automation, declared scraper and hosting network signals together and slow or refuse the session, leaving real learners and readers untouched.
- Check at
- Catalogue and searchContent downloads
- Reads
- AutomationDeclared bot or scraperHosting network
[ 03 / 06 ]Integration
Integrate at the right moments.
Four habits keep a policy for education and subscription media effective without turning it against genuine customers. A production identification is billed per request, from $0.0025, so it is worth placing where it earns its cost.
- 01 Identify at the moment
Call identify at trial start, login, when a lesson or article is opened against a meter and at downloads, not on every page. Pass your own account reference as the tag so the result comes back with the action.
await fingerly.identify({ tag: "trial-start" }) - 02 Verify on your server
Send only the request ID from the browser or app to your backend, read the stored result with a secret key, and check that the tag matches the action. Never grant access on what the client reports.
- 03 Observe before you enforce
Run in monitoring mode first. Households, schools and libraries share devices and networks, so measure how many genuine users a rule would affect before enforcing it.
- 04 Act in proportion
Choose gentle responses: a prompt to subscribe at the meter, a household plan for a shared login, a card for a repeat trial. Keep refusal for clear automation.
[ 04 / 06 ]Moments
Where to check, what to do.
Where an education or media product usually places the check and what it reads there.
| Moment | Identify when | Read | Usual first decision |
|---|---|---|---|
| Article or lesson view | The meter is read | Visitor ID, incognito mode | Show the subscribe prompt at the limit |
| Trial start | Before access is granted | Visitor ID, new or returning | Ask for a card on repeat trials |
| Login | Credentials are submitted | Visitor ID, location mismatch | Offer a plan beyond your device limit |
| Content download | Before a file is served | Automation, hosting network | Slow or refuse scripted sessions |
| Student offer | Before the discount applies | Visitor ID, device farm | Review repeat claimants |
Every decision is yours. Fingerly returns the visitor ID, the signals and the suspect score, and never blocks a request by itself.
[ 05 / 06 ]Questions
Questions about education and subscription media.
How an education or subscription media product uses device fingerprinting for access control.
Talk to the teamHow do I stop paywall bypass with private browsing?
With Fingerly, you count free content against the visitor ID instead of a cookie. A private window or cleared cookies resets a cookie meter but not the device, and Fingerly can also report the session as incognito, which explains why a reader looks new.
Can device fingerprinting detect account sharing on a streaming or course platform?
It gives you the evidence. Count the distinct visitor IDs behind one subscription and read location mismatch and VPN signals beside them. What happens past your limit is your policy, and offering a household or team plan usually works better than a block.
Does Fingerly proctor exams or monitor learners?
No. Fingerly does not observe what a learner does inside a course and does not read page content, keystrokes or the camera. It describes the device and network behind a request so access limits can be enforced fairly.
Will it work without cookies or a consent banner?
The SDKs write no cookies and nothing to browser storage, and show no prompt. You decide the notice, the legal basis and any consent your visitors need, and the SDKs collect nothing until you tell them consent is granted.
Will screen readers or privacy tools be flagged as bots?
No. Accessibility services are never counted as a sign of automation, and privacy tools such as VPNs and private windows are reported as context with small default weights, never as a verdict on their own.
Less guessing. More knowing.
Make the next connection a trusted one.
Start with the signals, keep your own decisions, and pay as you go, only for what you identify. No credit card needed.