Subprocessors
Last updated November 15, 2026
Ravensight is operated by Reality Software Entertainment, LLC, doing business as Ravensight. These are the service providers that process customer data for us, what each kind does, the kinds of data it receives and where it runs.
"Player data" means what a game's Ravensight SDK sends: event names and times, a random device identifier the SDK generates, a session identifier, platform, game version and whatever event data the developer chose to attach. It also covers player feedback text and player report messages and images. "Account data" means data about developers who use the dashboard.
This page lists the kinds of provider we use, what each does and the data it receives. The named list of subprocessors is available on request from support@realityse.com.
Ravensight processes data 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.
How we treat player data is set out in the Data Processing Addendum, how long each kind is kept in the retention and deletion policy, and the controls around it on the security page.
Infrastructure and storage
Cloud hosting provider
- Purpose
- Runs the Ravensight API, serves the website and the dashboard, and stores player report images and Playtest files in private storage.
- Data
- Player data and account data in transit through the API. At rest: player report images, and Playtest reports, screenshots and opt-in session recordings.
- Location
- United States.
Database provider
- Purpose
- The operational database: accounts, studios and memberships, games, hashed keys and tokens, billing records, studio context, Playtest records, player feedback and report records, daily and monthly aggregates, and the per-game device registry. It also holds a map of how players move between levels and how the studio's evidence connects, as references and counts.
- Data
- Account data; player feedback text and player report messages; device identifiers in the device registry; keyed hashes and masked forms of connecting network addresses (never the full address); level names and aggregate counts.
- Location
- United States.
Analytics storage provider
- Purpose
- The event store. Every gameplay event is written here and every analytics query reads from here.
- Data
- Raw player events: event name, time, device identifier, session identifier, level, platform, game version and the event data the developer attached.
- Location
- United States.
AI providers
AI model providers
- Purpose
- Language models power Huginn, the AI analyst, the design studio and the Brainstorm partner, feedback analysis, digests, source scans and Ravensight Playtest.
- Data
- The questions a developer asks and the query results the analyst reads to answer them, design conversations and the documents they cite, player feedback text in an analysis batch, source files a developer submits to a scan, and, for Playtest, the brief, the screenshots and game state a persona observes, and the source files a game profile or fix attempt reads. Requests carry minimized content and never account credentials.
- Location
- United States.
Embedding provider
- Purpose
- Text embeddings, so feedback search, studio memory and reference documents can be searched by meaning rather than exact words.
- Data
- Player feedback text, studio memory facts, passages of uploaded reference documents, Playtest findings and Brainstorm cards.
- Location
- United States.
AI classification provider
- Purpose
- Narrow structured judgments inside some features, such as classifying an evidence excerpt by topic and relevance, or whether a Playtest finding reads as a bug or as design intent. It never decides access, billing or a state change on its own.
- Data
- Short excerpts of the evidence being judged, capped in size.
- Location
- United States.
Research model provider
- Purpose
- Used only where it is configured, and it is not configured in production today. When configured, it is a second, independent research provider for market intelligence (quick look and deep research) and an optional model route for Playtest runs.
- Data
- For research, the research question about public games and markets. For Playtest, the same run content described under AI model providers, sent with the provider's own storage of the request switched off.
- Location
- United States.
Payments, email and messaging
Payment processor
- Purpose
- Takes card payments for prepaid balance top-ups.
- Data
- Account data needed for a payment: the payer's card details, which the processor collects directly and Ravensight never stores, and the amount and account the payment is for. No player data.
- Location
- United States.
Email delivery provider
- Purpose
- Sends Ravensight email: usage and anomaly alerts, team invitations, digests and scheduled reports.
- Data
- The recipient's email address and the message, which can include usage figures and summaries of a game's analytics.
- Location
- United States.
Text message provider
- Purpose
- Sends text messages to an account holder who adds an alert phone number: the verification code that confirms the number, and usage alerts after that.
- Data
- The phone number and the message, which is either a verification code or a short usage alert. No player data.
- Location
- United States.
Product analytics and sign-in
Product analytics provider
- Purpose
- Product analytics on the dashboard and on this website (ravensight.io, including the docs and the blog), and product and cost telemetry sent from the Ravensight API. In a browser that sends Do Not Track or Global Privacy Control, neither the dashboard nor this website loads it.
- Data
- On the dashboard: feature usage and pages viewed, tied to your Ravensight account identifier and plan, with campaign parameters from the link you arrived by. It never receives your email, name, keys, tokens, or the content of analyst questions. On ravensight.io: page views, page exits, the referring site, campaign parameters and a few named actions such as following a link to the dashboard, with no account identifier until you sign in to the dashboard from the same browser. Neither has session recording or automatic capture of clicks or typing. From the API: named events about account activity, such as an account created, a game created or deleted, an analyst or design question asked, a scan completed, a top-up, an alert sent or a Playtest job settled. Each is keyed to a Ravensight account identifier, or a studio or game identifier for events that belong to no one person, and carries identifiers (game, studio, Playtest job and run, and the repository name for a scan triggered by a push), counts, durations, amounts in cents, plan and status labels. Never email addresses, names, keys, tokens, event payloads, prompts or analyst questions and answers. No player data.
- Location
- United States.
RealitySE
- Purpose
- Our company identity service, operated by Reality Software Entertainment, LLC itself rather than a third party. It handles developer sign-in, including email and password and single sign-on.
- Data
- Account data: the account identifier, email address where available, and sign-in sessions. Ravensight never sees or stores a password. No player data.
- Location
- United States.
Services you connect
Some features read from services a studio connects on its own account: a GitHub repository for source scans, Steamworks for sales and wishlists, and YouTube, Reddit and Bluesky for Pulse. Ravensight reads from them at the studio's request with the access the studio grants; they do not process data on Ravensight's behalf. Data exports go to a bucket the studio owns and configures, and Ravensight never deletes from it.
Changes to this list
When we add or replace a subprocessor we email customers before it takes effect, as set out in the Data Processing Addendum, and update this page and its date where the change affects it.