Your account details stay yours.
Every order runs under end-to-end credential isolation. Workers, staff, admins — even the server owner — never see, never touch, never store your login. Including Jagex accounts.
What it means
Most account services treat your login as a piece of data their staff has to handle. The credential gets pasted into a worker ticket, copy-pasted into a launcher, sometimes saved "just in case" — and from that moment, an unknown number of people inside the shop can read it.
We don't do that. Your login arrives encrypted, lives encrypted, and is only ever decrypted inside the isolated worker process that needs it for the duration of the order. Then it's gone.
Who can never see your login
The worker
The person playing your account sees an opaque session, not the password.
Support / staff
Tickets and chat logs are scrubbed of any auth field before staff ever read them.
Admins
Admin tooling intentionally has no decrypt path — the keys aren't in the admin's environment.
The server owner
Even the owner cannot decrypt credentials from order history. It is not retained in a recoverable form.
How we guarantee it
Encrypted at rest
Credentials are stored only as ciphertext, keyed so the staff database has no path to decrypt them.
Decrypt only in the worker
Only the isolated worker process for your order holds the decryption key, and only while the order is live.
Scrubbed logs
Every audit / debug log filter strips auth fields. There is no realistic forensic recovery path.
What we actually keep
For order fulfillment and dispute history we keep the minimum:
- Order ID, status, and timestamps
- Service requested and price
- Encrypted credential payload (cannot be decrypted by anyone)
- Order-scoped chat history (auth fields stripped)
That's it. No plaintext passwords. No backup files containing decrypted credentials. No "just in case" secondary storage.
Common questions
What if Jagex emails me asking about the login?
The worker logged in from your IP (if you chose Seal I routing) using a single session. There is no persistent stored credential to leak.
What if there's a data breach?
An attacker who got everything we store would have order metadata and ciphertext blobs they cannot decrypt. The decrypt key never lives on the server or in the database.
Do you ever ask for my full password in chat?
No. Credentials enter through an encrypted form, not the ticket text. If anyone ever asks you to type it into chat, that's not us.
Ready to start?
Browse the service hall — every order runs under this seal by default. No opt-in required.