[{"data":1,"prerenderedAt":309},["ShallowReactive",2],{"docsv3-nav":3,"\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-sharing":198},[4],{"title":5,"path":6,"stem":7,"children":8,"page":188},"V3","\u002Fdocs\u002Fv3","1.docs\u002Fv3",[9,13,17,21,38,87,189],{"title":10,"path":11,"stem":12},"Introduction","\u002Fdocs\u002Fv3\u002Fintroduction","1.docs\u002Fv3\u002F1.Introduction",{"title":14,"path":15,"stem":16},"Quick start","\u002Fdocs\u002Fv3\u002Fquick-start","1.docs\u002Fv3\u002F2.Quick start",{"title":18,"path":19,"stem":20},"Challenge flow","\u002Fdocs\u002Fv3\u002Fchallenge-flow","1.docs\u002Fv3\u002F3.Challenge flow",{"title":22,"path":23,"stem":24,"children":25},"Fundamentals","\u002Fdocs\u002Fv3\u002Ffundamentals","1.docs\u002Fv3\u002F4.fundamentals",[26,30,34],{"title":27,"path":28,"stem":29},"Signup protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Fsignup-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F00.Signup protection",{"title":31,"path":32,"stem":33},"Login protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Flogin-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F01.Login protection",{"title":35,"path":36,"stem":37},"Access protection","\u002Fdocs\u002Fv3\u002Ffundamentals\u002Faccess-protection","1.docs\u002Fv3\u002F4.fundamentals\u002F02.Access protection",{"title":39,"path":40,"stem":41,"children":42},"Guides","\u002Fdocs\u002Fv3\u002Fguides","1.docs\u002Fv3\u002F5.guides",[43,47,51,55,59,63,67,71,75,79,83],{"title":44,"path":45,"stem":46},"Account sharing prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Faccount-sharing-prevention","1.docs\u002Fv3\u002F5.guides\u002F1.Account sharing prevention",{"title":48,"path":49,"stem":50},"Web scraping prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fweb-scraping-prevention","1.docs\u002Fv3\u002F5.guides\u002F13.Web scraping prevention",{"title":52,"path":53,"stem":54},"Ban enforcement","\u002Fdocs\u002Fv3\u002Fguides\u002Fban-enforcement","1.docs\u002Fv3\u002F5.guides\u002F14.Ban enforcement",{"title":56,"path":57,"stem":58},"Chargeback dispute","\u002Fdocs\u002Fv3\u002Fguides\u002Fchargeback-dispute","1.docs\u002Fv3\u002F5.guides\u002F15.Chargeback dispute",{"title":60,"path":61,"stem":62},"Multi-accounting prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fmulti-accounting-prevention","1.docs\u002Fv3\u002F5.guides\u002F16.Multi-accounting prevention",{"title":64,"path":65,"stem":66},"Account takeover prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Faccount-takeover-prevention","1.docs\u002Fv3\u002F5.guides\u002F2.Account takeover prevention",{"title":68,"path":69,"stem":70},"Risky transaction prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Frisky-transaction-prevention","1.docs\u002Fv3\u002F5.guides\u002F20.Risky transaction prevention",{"title":72,"path":73,"stem":74},"Fake account detection","\u002Fdocs\u002Fv3\u002Fguides\u002Ffake-account-detection","1.docs\u002Fv3\u002F5.guides\u002F3.Fake account detection",{"title":76,"path":77,"stem":78},"Bot detection","\u002Fdocs\u002Fv3\u002Fguides\u002Fbot-detection","1.docs\u002Fv3\u002F5.guides\u002F4.Bot detection",{"title":80,"path":81,"stem":82},"Card testing prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fcard-testing-prevention","1.docs\u002Fv3\u002F5.guides\u002F5.Card testing prevention",{"title":84,"path":85,"stem":86},"Incentive abuse prevention","\u002Fdocs\u002Fv3\u002Fguides\u002Fincentive-abuse-prevention","1.docs\u002Fv3\u002F5.guides\u002F9.Incentive abuse prevention",{"title":88,"path":89,"stem":90,"children":91,"page":188},"Concepts","\u002Fdocs\u002Fv3\u002Fconcepts","1.docs\u002Fv3\u002F6.concepts",[92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184],{"title":93,"path":94,"stem":95},"Evaluations","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fevaluations","1.docs\u002Fv3\u002F6.concepts\u002F01.evaluations",{"title":97,"path":98,"stem":99},"Actions","\u002Fdocs\u002Fv3\u002Fconcepts\u002Factions","1.docs\u002Fv3\u002F6.concepts\u002F02.actions",{"title":101,"path":102,"stem":103},"Signals","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fsignals","1.docs\u002Fv3\u002F6.concepts\u002F03.signals",{"title":105,"path":106,"stem":107},"Checks","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchecks","1.docs\u002Fv3\u002F6.concepts\u002F04.checks",{"title":109,"path":110,"stem":111},"Risks","\u002Fdocs\u002Fv3\u002Fconcepts\u002Frisks","1.docs\u002Fv3\u002F6.concepts\u002F05.risks",{"title":113,"path":114,"stem":115},"Verdicts","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fverdicts","1.docs\u002Fv3\u002F6.concepts\u002F06.verdicts",{"title":117,"path":118,"stem":119},"Policies","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpolicies","1.docs\u002Fv3\u002F6.concepts\u002F07.policies",{"title":121,"path":122,"stem":123},"Challenges","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchallenges","1.docs\u002Fv3\u002F6.concepts\u002F08.challenges",{"title":125,"path":126,"stem":127},"Concurrency","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fconcurrency","1.docs\u002Fv3\u002F6.concepts\u002F09.concurrency",{"title":129,"path":130,"stem":131},"Impossible travel","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fimpossible-travel","1.docs\u002Fv3\u002F6.concepts\u002F10.impossible-travel",{"title":133,"path":134,"stem":135},"Bots","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fbots","1.docs\u002Fv3\u002F6.concepts\u002F11.bots",{"title":137,"path":138,"stem":139},"Devices","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fdevices","1.docs\u002Fv3\u002F6.concepts\u002F12.devices",{"title":141,"path":142,"stem":143},"Fingerprints","\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffingerprints","1.docs\u002Fv3\u002F6.concepts\u002F13.fingerprints",{"title":145,"path":146,"stem":147},"People","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpeople","1.docs\u002Fv3\u002F6.concepts\u002F14.people",{"title":149,"path":150,"stem":151},"Lists","\u002Fdocs\u002Fv3\u002Fconcepts\u002Flists","1.docs\u002Fv3\u002F6.concepts\u002F15.lists",{"title":153,"path":154,"stem":155},"Account takeover","\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-takeover","1.docs\u002Fv3\u002F6.concepts\u002F16.account-takeover",{"title":157,"path":158,"stem":159},"Account sharing","\u002Fdocs\u002Fv3\u002Fconcepts\u002Faccount-sharing","1.docs\u002Fv3\u002F6.concepts\u002F17.account-sharing",{"title":161,"path":162,"stem":163},"Fake account","\u002Fdocs\u002Fv3\u002Fconcepts\u002Ffake-account","1.docs\u002Fv3\u002F6.concepts\u002F18.fake-account",{"title":165,"path":166,"stem":167},"Scraping","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fscraping","1.docs\u002Fv3\u002F6.concepts\u002F19.scraping",{"title":169,"path":170,"stem":171},"Linked accounts","\u002Fdocs\u002Fv3\u002Fconcepts\u002Flinked-accounts","1.docs\u002Fv3\u002F6.concepts\u002F20.linked-accounts",{"title":173,"path":174,"stem":175},"New IP","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fip","1.docs\u002Fv3\u002F6.concepts\u002F21.ip",{"title":177,"path":178,"stem":179},"Anonymizing network","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fanonymizing-network","1.docs\u002Fv3\u002F6.concepts\u002F22.anonymizing-network",{"title":181,"path":182,"stem":183},"Email quality","\u002Fdocs\u002Fv3\u002Fconcepts\u002Femail","1.docs\u002Fv3\u002F6.concepts\u002F23.email",{"title":185,"path":186,"stem":187},"Velocity","\u002Fdocs\u002Fv3\u002Fconcepts\u002Fvelocity","1.docs\u002Fv3\u002F6.concepts\u002F24.velocity",false,{"title":190,"path":191,"stem":192,"children":193,"page":188},"Advanced","\u002Fdocs\u002Fv3\u002Fadvanced","1.docs\u002Fv3\u002F7.Advanced",[194],{"title":195,"path":196,"stem":197},"Proxy setup","\u002Fdocs\u002Fv3\u002Fadvanced\u002Fproxy-setup","1.docs\u002Fv3\u002F7.Advanced\u002F1.Proxy-setup",{"id":199,"title":157,"body":200,"description":300,"extension":301,"meta":302,"navigation":303,"path":158,"rawbody":304,"seo":305,"stem":159,"__hash__":308},"docsv3\u002F1.docs\u002Fv3\u002F6.concepts\u002F17.account-sharing.md",{"type":201,"value":202,"toc":294},"minimark",[203,207,211,228,233,268,272],[204,205,157],"h1",{"id":206},"account-sharing",[208,209,210],"p",{},"Account sharing is when one account is used by more than one person: a login passed around a household, a team seat split between coworkers, a subscription resold to strangers. The credentials are correct every time, so nothing looks wrong at the auth layer. The tell is the pattern of use over time: more devices and more locations than one person racks up, plus activity in two places at once.",[208,212,213,214,218,219,223,224,227],{},"This is the risk Rupt v2 was built around, and it's scored on the ",[215,216,217],"code",{},"access"," ",[220,221,222],"a",{"href":98},"action",". It also stays in play on ",[215,225,226],{},"login"," so you can act at sign-in rather than waiting for the next page view.",[229,230,232],"h2",{"id":231},"what-rupt-looks-for","What Rupt looks for",[234,235,236,246,254,261],"ul",{},[237,238,239,245],"li",{},[240,241,242],"strong",{},[220,243,244],{"href":138},"Device count",": how many distinct computers, tablets, and phones have touched the account. Counts are tracked per device type, since five phones on one account reads very differently from five shared computers.",[237,247,248,253],{},[240,249,250],{},[220,251,252],{"href":126},"Concurrent sessions",": the account is active from two places at the same time, which one person can't be.",[237,255,256,260],{},[240,257,258],{},[220,259,129],{"href":130},": back-to-back activity from locations too far apart to bridge in the time elapsed.",[237,262,263,267],{},[240,264,265],{},[220,266,185],{"href":186},": an unusual rate of activity for a single user.",[229,269,271],{"id":270},"severity-and-response","Severity and response",[208,273,274,275,218,278,281,282,285,286,289,290,293],{},"The checks aggregate into an ",[215,276,277],{},"account_sharing",[220,279,280],{"href":110},"risk"," severity. Sharing is rarely something you want to hard-block, since the account holder is often involved, so most teams ",[220,283,284],{"href":122},"challenge"," to re-verify the owner, or ",[220,287,288],{"href":150},"add them to a list"," for follow-up and treat repeat offenders as an upsell to a larger plan. Your ",[220,291,292],{"href":118},"policies"," decide which.",{"title":295,"searchDepth":296,"depth":296,"links":297},"",2,[298,299],{"id":231,"depth":296,"text":232},{"id":270,"depth":296,"text":271},"[object Object]","md",{},true,"---\ntitle: Account sharing\ndescription: Account sharing is one account used by several people who aren't the owner: a password passed around a household, team, or group. Rupt detects it from device counts, concurrent sessions, and impossible travel.\n---\n\n# Account sharing\n\nAccount sharing is when one account is used by more than one person: a login passed around a household, a team seat split between coworkers, a subscription resold to strangers. The credentials are correct every time, so nothing looks wrong at the auth layer. The tell is the pattern of use over time: more devices and more locations than one person racks up, plus activity in two places at once.\n\nThis is the risk Rupt v2 was built around, and it's scored on the `access` [action](\u002Fdocs\u002Fv3\u002Fconcepts\u002Factions). It also stays in play on `login` so you can act at sign-in rather than waiting for the next page view.\n\n## What Rupt looks for\n\n- **[Device count](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fdevices)**: how many distinct computers, tablets, and phones have touched the account. Counts are tracked per device type, since five phones on one account reads very differently from five shared computers.\n- **[Concurrent sessions](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fconcurrency)**: the account is active from two places at the same time, which one person can't be.\n- **[Impossible travel](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fimpossible-travel)**: back-to-back activity from locations too far apart to bridge in the time elapsed.\n- **[Velocity](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fvelocity)**: an unusual rate of activity for a single user.\n\n## Severity and response\n\nThe checks aggregate into an `account_sharing` [risk](\u002Fdocs\u002Fv3\u002Fconcepts\u002Frisks) severity. Sharing is rarely something you want to hard-block, since the account holder is often involved, so most teams [challenge](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fchallenges) to re-verify the owner, or [add them to a list](\u002Fdocs\u002Fv3\u002Fconcepts\u002Flists) for follow-up and treat repeat offenders as an upsell to a larger plan. Your [policies](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fpolicies) decide which.\n",{"title":157,"description":306},{"Account sharing is one account used by several people who aren't the owner":307},"a password passed around a household, team, or group. Rupt detects it from device counts, concurrent sessions, and impossible travel.","qhUYq8SLAbR8IUaEHXGcPe-Q2ZRNt9SnTZ-hVuXFqno",1780344893590]