[{"data":1,"prerenderedAt":358},["ShallowReactive",2],{"docsv3-nav":3,"\u002Fdocs\u002Fv3\u002Fguides\u002Faccount-sharing-prevention":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":44,"body":200,"description":351,"extension":352,"meta":353,"navigation":354,"path":45,"rawbody":355,"seo":356,"stem":46,"__hash__":357},"docsv3\u002F1.docs\u002Fv3\u002F5.guides\u002F1.Account sharing prevention.md",{"type":201,"value":202,"toc":344},"minimark",[203,207,215,220,231,235,245,321,324,328],[204,205,44],"h1",{"id":206},"account-sharing-prevention",[208,209,210,211,214],"p",{},"Account sharing is one subscription used by several people, and it's the use-case framing of the ",[212,213,35],"a",{"href":36}," fundamental.",[216,217,219],"h2",{"id":218},"step-1-set-up-access-protection","Step 1: Set up access protection",[208,221,222,223,225,226,230],{},"Set up ",[212,224,35],{"href":36}," first. It's self-managed: you call ",[227,228,229],"code",{},"evaluate.access"," on the client and Rupt handles detection, the challenge, owner verification, and device capping client-side. There's no server step. With that in place, the policies below are what actually catch sharing.",[216,232,234],{"id":233},"step-2-add-the-policies","Step 2: Add the policies",[208,236,237,238,244],{},"A policy has a trigger (the event it runs on) and a verdict. Add these in your ",[212,239,243],{"href":240,"rel":241},"https:\u002F\u002Fapp.rupt.dev\u002Fpolicies",[242],"nofollow","policies dashboard",":",[246,247,248,267],"table",{},[249,250,251],"thead",{},[252,253,254,258,261,264],"tr",{},[255,256,257],"th",{},"Policy",[255,259,260],{},"Trigger",[255,262,263],{},"Conditions",[255,265,266],{},"Verdict",[268,269,270,293],"tbody",{},[252,271,272,276,281,290],{},[273,274,275],"td",{},"Verify the owner",[273,277,278],{},[227,279,280],{},"access",[273,282,283,286,287],{},[227,284,285],{},"concurrent_sessions",", or ",[227,288,289],{},"impossible_travel",[273,291,292],{},"Challenge",[252,294,295,298,302,319],{},[273,296,297],{},"Cap devices",[273,299,300],{},[227,301,280],{},[273,303,304,307,308,311,312,311,315,318],{},[227,305,306],{},"device_count"," over your limit (or per-type ",[227,309,310],{},"computer_device_count"," \u002F ",[227,313,314],{},"tablet_device_count",[227,316,317],{},"mobile_device_count",")",[273,320,292],{},[208,322,323],{},"Account sharing leans on devices, not fingerprints, and the goal is to convert the extra user, so point the challenge Success URL at signup. The device-cap challenge logs the extra devices out. Tune conservatively: a false sharing accusation is costly, so start loose and tighten only if you need to.",[216,325,327],{"id":326},"related","Related",[329,330,331,336,340],"ul",{},[332,333,334],"li",{},[212,335,35],{"href":36},[332,337,338],{},[212,339,125],{"href":126},[332,341,342],{},[212,343,137],{"href":138},{"title":345,"searchDepth":346,"depth":346,"links":347},"",2,[348,349,350],{"id":218,"depth":346,"text":219},{"id":233,"depth":346,"text":234},{"id":326,"depth":346,"text":327},"Account sharing is one subscription used by several people, and it's the use-case framing of the Access protection fundamental.","md",{},true,"---\ntitle: Account sharing prevention\n---\n\n# Account sharing prevention\n\nAccount sharing is one subscription used by several people, and it's the use-case framing of the [Access protection](\u002Fdocs\u002Fv3\u002Ffundamentals\u002Faccess-protection) fundamental.\n\n## Step 1: Set up access protection\n\nSet up [Access protection](\u002Fdocs\u002Fv3\u002Ffundamentals\u002Faccess-protection) first. It's self-managed: you call `evaluate.access` on the client and Rupt handles detection, the challenge, owner verification, and device capping client-side. There's no server step. With that in place, the policies below are what actually catch sharing.\n\n## Step 2: Add the policies\n\nA policy has a trigger (the event it runs on) and a verdict. Add these in your [policies dashboard](https:\u002F\u002Fapp.rupt.dev\u002Fpolicies):\n\n| Policy           | Trigger  | Conditions                                                                                                | Verdict    |\n| ---------------- | -------- | --------------------------------------------------------------------------------------------------------- | --------- |\n| Verify the owner | `access` | `concurrent_sessions`, or `impossible_travel`                                                             | Challenge |\n| Cap devices      | `access` | `device_count` over your limit (or per-type `computer_device_count` \u002F `tablet_device_count` \u002F `mobile_device_count`) | Challenge |\n\nAccount sharing leans on devices, not fingerprints, and the goal is to convert the extra user, so point the challenge Success URL at signup. The device-cap challenge logs the extra devices out. Tune conservatively: a false sharing accusation is costly, so start loose and tighten only if you need to.\n\n## Related\n\n- [Access protection](\u002Fdocs\u002Fv3\u002Ffundamentals\u002Faccess-protection)\n- [Concurrency](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fconcurrency)\n- [Devices](\u002Fdocs\u002Fv3\u002Fconcepts\u002Fdevices)\n",{"title":44,"description":351},"xNUOsLPg28k7xIluY3Wv386GtZdvGTjCI5mXuu2NVB0",1780344892900]