RISE Reduce — Data Processing Addendum
kind: dpa
version: 0.0.0-draft
effective: not yet in force
status: draft
sections: 5 (5 awaiting counsel)

1. Roles of the parties
[LEGALLY OPERATIVE — RISE does not draft this text.]
[AWAITING COUNSEL]

2. Scope of processing
[LEGALLY OPERATIVE — RISE does not draft this text.]
[AWAITING COUNSEL]

3. Sub-processors
[LEGALLY OPERATIVE — RISE does not draft this text.]
[AWAITING COUNSEL]

4. Security measures
[LEGALLY OPERATIVE — RISE does not draft this text.]
[AWAITING COUNSEL]

5. International transfers
[LEGALLY OPERATIVE — RISE does not draft this text.]
[AWAITING COUNSEL]

--- PRODUCT FACTS SUPPLIED TO COUNSEL (NOT TERMS, NOT BINDING) ---
- 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.