Security
> riven/manifest/security
RIVEN holds two things worth protecting: a wallet balance, and the identity documents needed to pay it out. This page lists the controls that are actually in place around them, and is deliberately short — everything on it is something the product does today.
No password to steal
Signing up for RIVEN never creates a password. You get in with your Steam account or with a one-time code sent to your email address, so there is no RIVEN password for you to reuse from another site and none for us to lose.
Your email address is fixed to your account
The email on an account is read-only in the dashboard. Changing it is not a form field, so an attacker with a live session cannot quietly redirect your sign-in codes.
Sanctions block
RIVEN is not served to connections from Russia, Belarus, Iran, North Korea, Syria or Cuba: every page and API request from those countries is refused by IP address. Accounts are not opened for email addresses registered there, and card payments with a billing country among them are refused.
Card numbers are never stored
No card number reaches RIVEN's database. The billing address you type may be kept in your own browser to save re-typing it, and only if you allowed preference storage in the cookie banner — it is not sent anywhere else.
Charging is locked off in code, not just in config
This deployment cannot make a real card charge. That is a hardcoded refusal in the payment layer, not an environment variable that could be flipped by pasting the wrong key into a settings panel — and a top-up that reaches no payment provider credits nothing rather than quietly minting balance. Turning charging on takes a deliberate code change and review.
Every balance change is written as a ledger entry
A wallet debit, the order it paid for, and the ledger row that records it are written in one database transaction. Balance cannot move without a matching entry, and your own history is visible under dashboard → wallet.
Payouts are verified before they are released
Withdrawing money you earned from selling requires identity verification, and every request is reviewed and approved before a payout goes out. We can refuse, suspend or reverse a payout where verification is incomplete or fraud is suspected.
Identity documents are held for review, and deleted with your account
An ID photo submitted for verification is stored for the review it was submitted for. Deleting your account removes it — the stored document is destroyed along with the account record, not orphaned.
Export and deletion are self-serve
You can download everything RIVEN holds on you as JSON, and delete your account, from dashboard → account. Neither needs a support ticket. Your full rights are in the privacy policy.
Nothing optional is stored before you choose
RIVEN sets no third-party advertising or tracking cookie. The single piece of optional storage — remembering your billing address in your own browser so you do not retype it — stays off until you switch it on in the cookie banner, and you can withdraw it at any time with “Manage cookies” in the footer.
RIVEN has not been through an external security audit or a penetration test, holds no security certification, and runs no bug bounty programme. We would rather say so than print a badge. Skin delivery depends on Steam, and a trade hold or an outage on Steam's side is outside our control — what we guarantee there is that a failed trade is put in front of a person who completes it or returns the money, not that a trade always succeeds and not that anything is reversed automatically.
If you have found a vulnerability, send it through the contact form. That form reaches our operations channel directly, which is the fastest route to someone who can act on it. Please include what you did, what you saw, and the URL — and please do not test against another person's account or a live payout.