RISE Reduce — Sub-processors
kind: sub_processors
version: 0.3.2-disclosure
effective: not yet in force
status: disclosure
sections: 2 (1 awaiting counsel)
statements of fact last checked against the code: 2026-09-24

Current sub-processors
[STATEMENT OF FACT — authored by RISE engineering, verifiable against the shipped code. Not a term.]
Stripe, Inc. — payment processing and money-of-record. Receives the buyer's billing contact details and payment instrument directly from the buyer, on a page Stripe hosts, and receives from RISE HQ the buyer's confirmed e-mail address, the checkout and subscription details a sale needs (the plan choice, an order id, and the version and SHA-256 of the terms and privacy documents) and any tax exemption decision with its certificate or registration number (src/http/checkout.ts, src/stripe/customerTaxExempt.ts). RISE HQ never handles a card or bank account number; the billing contact details come back to HQ in Stripe's events (privacy notice, section 3).

The outbound mail transport configured in SMTP_URL — receives customer e-mail addresses and the contents of the messages HQ sends: download links, licence grants, activation codes, the 6-digit codes that confirm a buyer's or an organisation contact's e-mail address, the notice that an order is on hold, statements and invoices, and low-balance notices for a customer's prepaid Reserve balance. Where SMTP_URL is unset the messages go to a local directory instead and no third party is involved (src/config/env.ts).

No object-storage provider, and no other party. Whether one ever becomes a sub-processor turns on BRIDGE_TRANSPORT; src/bridge/transport.ts exports exactly one transport, a local directory, so that path today reaches nobody outside the customer's own deployment.

Change notification
[LEGALLY OPERATIVE — RISE does not draft this text.]
[AWAITING COUNSEL]

--- PRODUCT FACTS SUPPLIED TO COUNSEL (NOT TERMS, NOT BINDING) ---
- THE CONSTRAINT ON THE NOTICE SECTION: adding a sub-processor is a change to this repository or to its deployed configuration — there is no runtime mechanism by which a new third party can begin receiving customer data. So a notice period is enforceable by release discipline, not by code, and HQ has no mechanism today for delivering the notice: no subscriber list for this document, no feed, no alert. Whatever period is drafted has to be built.
- The roster above is published FACT, re-verified against src/bridge/transport.ts and src/config/env.ts on the measurement date carried in this document's canonical text.