This document is a DRAFT and is not in force. No part of this document has been drafted. It is published at a stable URL so that its version and content hash exist before counsel delivers the text. No agreement is formed by reading this page, and no section marked as awaiting counsel is a term,
a representation, or an offer.
RISE Reduce — Data Processing Addendum
Version 0.0.0-draft · effective not yet in force · 0 of 5 sections written
SHA-256 of this document's canonical text:
da4f6ebe6d5674c301e3ac898b8dfdd3de3e09f43ae9dbcfbe0541f3f52b209f
canonical text the hash covers
1. Roles of the parties
AWAITING COUNSEL · legally operative, not drafted
[AWAITING COUNSEL]
2. Scope of processing
AWAITING COUNSEL · legally operative, not drafted
[AWAITING COUNSEL]
3. Sub-processors
AWAITING COUNSEL · legally operative, not drafted
[AWAITING COUNSEL]
4. Security measures
AWAITING COUNSEL · legally operative, not drafted
[AWAITING COUNSEL]
5. International transfers
AWAITING COUNSEL · legally operative, not drafted
[AWAITING COUNSEL]
PRODUCT FACTS SUPPLIED TO COUNSEL — NOT TERMS
- Customer files are processed entirely on customer-controlled hardware. RISE HQ does not receive, store or process customer file content at any point.
- Data reaching HQ from an installation is not limited to metering records: privacy notice section 2 lists the metering fields in full and the other requests HQ accepts from an installation (activation, enrollment of a licence's public key and passphrase-wrapped private key, grant and lease downloads; the training seed, pack and shape-catalogue requests were closed on 2026-09-24 and answer 410 without reading the request), and section 3 records that HQ's request log keeps the IP address of every request. Which of those requests a shipped engine makes itself is engine behaviour and is not established in HQ's code.
