Data Processing Addendum
Last updated November 15, 2026
This is Ravensight's standard Data Processing Addendum. It sets out how Ravensight processes personal data about the players of your games. It takes effect when both parties sign it, and then supplements the Terms of Service. To request a countersigned copy, email support@realityse.com with your studio's legal name and address.
1. Parties and roles
"Customer" is the studio or person that holds the Ravensight account and integrates a Ravensight SDK into its games. "Ravensight" is Reality Software Entertainment, LLC, an Ohio limited liability company doing business as Ravensight.
For player data, the customer is the controller and Ravensight is the processor. The customer decides what its games send; Ravensight processes it to provide the service. For data about the customer's own developers, such as sign-in and billing details, Ravensight acts as a controller under the Privacy Policy, and this addendum does not apply to it.
2. Scope of processing
- Subject matter and purpose
- Collecting gameplay events from the customer's games, storing them, computing analytics over them, running the AI features the customer uses, and protecting the service from abuse.
- Duration
- For as long as the customer uses Ravensight, and then until deletion as described in section 9.
- Data subjects
- Players of the customer's games, including players who send feedback or a player report.
- Categories of personal data
- A random device identifier generated by the SDK, a session identifier, event names and times, level, platform and game version, the event data the customer chooses to attach, player feedback text, player report messages and images, and a keyed hash and masked form of the connecting network address. The SDKs collect no names, emails or contact details.
- Special categories
- None are intended. The customer will not send special category data, or data about children that the law does not allow it to collect, in event data or any other field.
3. Instructions
Ravensight processes player data only on the customer's documented instructions. Those instructions are the Terms of Service, this addendum, and the customer's own configuration and use of the service, such as the games it creates, the retention it selects and the features it runs. If Ravensight believes an instruction breaks data protection law, it will tell the customer.
4. Confidentiality
Access to player data is limited to the service itself and to the people who operate it, and each of them is bound to keep it confidential.
5. Security measures
Ravensight maintains the measures below. The security page describes each one in more detail.
- Tenancy. Every request for a game's data loads the game through the requester's current studio membership; the game used in a query never comes from request input; a game outside the requester's studios answers as if it did not exist; every event query binds the game as a parameter.
- Encryption in transit. The API accepts TLS 1.2 and 1.3 only, and reaches its data stores over TLS or HTTPS.
- Network addresses. A player's full network address is never stored. Only a keyed hash and a masked form are kept, for 30 days or while the customer keeps that address blocked.
- Retention. Raw events expire automatically after the period the customer selects (90 days by default, or 180 or 400), and other records expire as the retention and deletion policy lists.
- Access control. Studio roles (owner, admin, member) are enforced from one permission table on every request. Keys and tokens are stored only as hashes.
- Audit log. Every change made through the dashboard is recorded with the person who made it and kept for 180 days, readable by the studio's owners and admins.
- AI tools. The analyst's SQL tool runs behind a parse-and-rewrite guard that limits it to the current game and to read-only queries with row and time limits.
6. Subprocessors
The customer authorizes Ravensight to use subprocessors of the kinds described on the subprocessors page, which says what each kind receives and the country where it processes data. The named list of subprocessors is available on request from support@realityse.com. Ravensight requires each of them to protect the data it receives and to use it only to provide its service to Ravensight.
Before a new or replacement subprocessor begins processing player data, Ravensight will email the customer's account owner at the address on the account, and will update the subprocessors page where the change affects it. The customer may object on reasonable data protection grounds by replying to that email. If the objection cannot be resolved, the customer may stop using the service, and Ravensight will refund the unused prepaid balance as the Terms of Service describe.
7. International transfers
Ravensight processes data in the United States. If the customer needs its data processed in another region, the customer may write to support@realityse.com and Ravensight will work with the customer on it. Where the law requires a transfer mechanism for data leaving another country, the parties will agree one in the countersigned copy.
8. Helping with players' requests
The customer can act on a player's request with the tools the retention and deletion policy describes: erasing one device's events, deleting a game, and offering the SDK's reset and opt-out switches. For anything those tools do not cover, Ravensight will help on request to support@realityse.com. If a player contacts Ravensight directly, Ravensight will refer them to the customer.
9. Deletion at the end of the service
The customer can delete each game from the dashboard at any time, which deletes its player data as the retention and deletion policy describes. When the customer stops using Ravensight, Ravensight will delete the remaining player data on written request, except where the law requires it to be kept. Billing records, which hold no player data, are kept as that policy explains. Data in provider backups is deleted as those backups age out.
10. Personal data breaches
Ravensight will notify the customer without undue delay after becoming aware of a personal data breach affecting the customer's player data. The notice will describe what is known about the breach, the data and players likely affected, and the steps taken, and Ravensight will add to it as more becomes known.
11. Information and audits
Ravensight will answer the customer's reasonable written questions about its processing, including security questionnaires, so the customer can show it meets its own obligations. Ravensight does not yet hold a third-party security certification.
12. Contact
Questions about this addendum, and requests for a countersigned copy, go to support@realityse.com, or to Reality Software Entertainment, LLC, Mount Vernon, Ohio. Security reports go to the same address.