SCRYCompliance
Scry is a companion, not a client
The single most important thing to understand about Scry: it never connects to the game, never reads it, and never plays it for you. It floats over Old School RuneScape the way a wiki tab sits open beside you — separate, passive, and entirely under your control.
Below is a plain-English summary of Jagex's own rules on third-party software, set next to exactly how Scry behaves. Nothing here is legal advice or an official Jagex position — it's our honest account of how the app is built, which we've also disclosed to Jagex in full.
What Jagex's rules are actually about
Jagex maintains an Approved Client List — RuneLite, HDOS and the official clients — for software that connects to and renders the game. Their separate "macro and client features not permitted" rules describe the behaviours that make any third-party tool a problem: talking to the game servers, sending inputs, tampering with the game, and so on.
Scry does none of those things because Scry is not a client. It doesn't log in, doesn't draw the game, and doesn't sit between you and Jagex. It's an Android overlay that shows you reference information while you play the official app. That distinction is the whole design.
Rule by rule
Here you will find what Jagex prohibit, in our own words and what Scry does instead.
Communicating directly with the game worlds.
Scry never connects to any OSRS game server. The only data it fetches comes from public community sources — the OSRS Wiki and Wise Old Man — and only when you tap to request it.
Generating input to the game — automatically moving the pointer or producing clicks and key presses.
Zero input automation. Scry never injects a tap, click, swipe or keypress into OSRS. Its buttons only ever respond to your finger. There is no auto-clicker, no gesture dispatch, nothing that acts for you.
Modifying, replacing or reverse-engineering the game client.
Scry doesn't read, hook, modify or reverse the OSRS app. It runs in its own separate window, floating on top — it can't see inside the game and doesn't try. No memory reading, no inspection of the game process, and no live screen capture: Scry never uses Android's screen-recording API. The one related feature — screenshot sharing — never uses a screen-capture API and never requests broad photo access. When you tap Share, Scry opens Android's built-in photo picker, which lets you choose one image; Scry never sees the rest of your gallery, and the picker itself needs no permission at all.
Making repeated or bandwidth-heavy automated requests — each request should follow a direct user action.
Every network call Scry makes is a direct response to something you did — a search, a lookup, a calculator. There are no background scraping loops or automated polling against Jagex's servers.
Hiding the adverts on Jagex's website, or shrinking the game pane to conceal them.
Not applicable by design. Scry doesn't embed, reframe or alter the OSRS website or the game view, so there's nothing of Jagex's for it to resize or hide.
Making it easier to enter or monitor busy worlds than it would be without the software.
Scry's world tool is a read-only latency display. It doesn't log in, doesn't hop worlds, and does nothing to ease or automate entry into any world.
An integrated chat that could be mistaken for official, Jagex-moderated game chat.
Scry has no chat feature of any kind — no messaging, no channels, nothing that could be confused with in-game chat.
We audited our own build
Before submitting to Jagex we went through Scry line by line and stripped anything non-essential — removing components and permissions that weren't needed for a feature to work, and documenting what was left. We'd rather over-disclose than leave a question unanswered.
Full disclosure on request
We've shared a complete technical breakdown of Scry's permissions, services and behaviour with Jagex directly. If you're from Jagex and want that detail, reach us at scryosrs@protonmail.com.
Jagex's rules referenced here are summarised in our own words from their public Legal Portal. For the authoritative wording, see Jagex's Macro and client features not permitted and their Third-Party Client Guidelines.