Security
Last updated November 15, 2026
This page describes the security measures Ravensight has in place today. Each one is a property of the running service, not a plan. Where something is not yet done, the last section says so.
Where Ravensight runs
Ravensight runs with a major cloud provider in the United States. If you need your data processed in another region, email support@realityse.com and we will work with you on it. The API, the website and the dashboard are served over HTTPS. Account and operational data and gameplay events are kept by managed database providers in the United States and reached only over encrypted connections. The kinds of provider we use, and what each receives, are on the subprocessors page.
Encryption
- The API accepts TLS 1.2 and TLS 1.3 only, and sends a Strict-Transport-Security header so browsers keep to HTTPS.
- The API reaches every data store over an encrypted connection.
- Data is stored with providers that encrypt it at rest.
- A credential a studio gives us so we can call a service on its behalf, such as a Steamworks key, is encrypted in our database with AES-256-GCM under a key held only in the server's environment. It is never returned to the dashboard, logged or sent to a browser.
Tenancy
- Every request for a game's data loads the game through the signed-in person's current studio membership. The game used in a data query comes from that lookup, never from a value the request supplied.
- A game you are not a member of answers 404, exactly like a game that does not exist, so its existence is not revealed. A game you can see but whose action your role does not allow answers 403.
- Every event store query passes the game as a bound parameter. No request value is ever written into query text.
- The AI analyst can write its own SQL, so that tool sits behind a guard that parses and rewrites the query before the event store sees it: it refuses comments, multiple statements and every table except the events table, replaces each reference to that table with a subquery limited to the current game by a bound parameter, and runs read-only with a row cap and a time limit.
- A deleted game's identifier is retired permanently, so no other studio can register it and inherit anything addressed to it.
Accounts and access
- Developers sign in through RealitySE, our company identity service. Ravensight never sees or stores a password. Every sign-in is checked with RealitySE itself, so signing out there is honored here.
- Ravensight then issues its own session cookie, signed with its own secret, marked HttpOnly, Secure and SameSite=Lax.
- Studio roles are owner, admin and member, decided by one permission table. Only an owner manages billing, members, data exports, retention and sharing. Owners and admins can delete a game, rotate its keys and read the audit log.
Keys and tokens
- Ingest keys, MCP tokens and Playtest CLI tokens are stored only as SHA-256 hashes. A database copy does not contain a usable key.
- An ingest key ships inside a game build, so it is treated as public: it can open play sessions, send events, feedback and player reports, and fetch the game's SDK settings and remote configuration. It cannot read player data or analytics.
- Rotating a game's key stops the previous key at once, together with the play sessions it opened.
- An MCP token reads only what its holder's role allows. Writing through MCP needs both a token an owner has enabled for writes and a role that may write, and nothing about money, tokens, members, games or projects is writable over MCP.
Player privacy by design
- A player's full network address is never stored. For abuse protection Ravensight keeps a keyed hash and a masked form (the first three parts of an IPv4 address, or the first 48 bits of an IPv6 address) for 30 days, or for as long as a developer keeps that address blocked.
- The SDKs identify a device with a random identifier they generate. They collect no names, emails or contact details, and they give developers a reset call and an opt-out call to offer their players.
- Raw events expire on a fixed schedule. The retention and deletion policy lists every period.
Audit log
Every change made through the dashboard API is recorded in the studio's audit log: who acted, in which studio, on which game and what the action was, with small display-safe details and never keys, tokens or email addresses. Entries are kept for 180 days, and owners and admins can read them in the dashboard.
AI and your code
- Playtest model calls go through our own proxy, which rebuilds each request from a fixed allowlist of fields rather than forwarding what the client sent. It keeps a metering row for each call and no prompt or completion text.
- Files a Playtest run uploads must match a fixed allowlist, and a file that trips our secret scan is quarantined rather than stored with your reports.
- The Ravensight GitHub App has read-only access to repository contents. The Ravensight server never writes to a repository; a Labs fix runs on the developer's own machine.
Abuse controls
Session creation, event ingest, sign-in, administrative routes, Playtest routes, the data API and the OAuth endpoints are rate limited. Each game has a traffic view of its connecting addresses (in hashed and masked form) and a block list a developer controls.
What is not in place yet
Ravensight does not yet hold a third-party security certification and does not offer an uptime commitment. The status page shows daily uptime for the API, the dashboard and the website over the last 90 days, measured by Ravensight's own checks, and any incident we post. We will update this page as that changes.
Reporting a vulnerability
Email support@realityse.com. Our security.txt lists the contacts and the scope: ravensight.io, app.ravensight.io, api.ravensight.io, the SDKs and the Playtest CLI. We answer every report, tell you what we are doing about it, and will not pursue anyone who reports in good faith.
Please do not run automated scanners against api.ravensight.io. It is a metered ingest endpoint and the traffic is billed to customers. Ask first and we will set you up with a test account.