MUModel Uplink
LEGAL · LAST UPDATED 6 SEPTEMBER 2026

Subprocessors

Amazon Web Services

Purpose: relay and control-plane hosting, managed database and backups, encrypted operational logs, transactional email, DNS and domain registration, secrets storage, and delivery of the website, downloads, and package repository.
Data: account and endpoint records, endpoint hostnames and DNS records, operational metadata, encrypted inference traffic in transit, support correspondence, and infrastructure logs.
Processing locations: Germany (Frankfurt) for the control plane, database, backups, email, and the European relay. United States (Northern Virginia) for the US relay, which carries encrypted model traffic only and holds no database or billing data. Content-delivery edge locations worldwide for the public website and downloads. Limited international access may occur for support and service operation.
Transfer safeguard: AWS data-processing terms and the European Commission’s Standard Contractual Clauses where required.

Stripe

Purpose: checkout, subscriptions, payments, invoices, tax calculation, and fraud prevention.
Data: customer email, billing address and tax information, subscription and transaction records, and payment-method information supplied directly to Stripe. Model Uplink does not store complete card details.
Processing locations: European Union and global locations described by Stripe.
Role and safeguard: Stripe may act as an independent controller or processor depending on the activity; its services are governed by its data-processing terms and lawful transfer mechanisms.

Plausible Analytics

Purpose: aggregate statistics for the public website pages.
Data: page addresses, referrer, browser and device category, and an approximate country derived from the visitor’s IP address, which is hashed with a daily key and never stored in readable form. No cookies or persistent identifiers. Signed-in dashboard activity and Customer inference data are not measured.
Processing locations: European Union (Germany).
Transfer safeguard: Plausible data-processing terms; no transfer outside the EEA.

Let’s Encrypt (Internet Security Research Group)

Purpose: issues the TLS certificate for each endpoint hostname. The Model Uplink app on the Customer’s computer requests the certificate; the private key never leaves that computer.
Data: endpoint hostnames, which become part of public Certificate Transparency logs as is standard for every publicly trusted certificate. Choose an endpoint name accordingly.
Processing locations: United States.
Safeguard: Let’s Encrypt subscriber agreement; no account or inference data is shared.

Changes and objections

Business customers authorise these providers under the DPA. We will notify the account email at least 30 days before a new or replacement subprocessor begins processing Customer Personal Data. A customer may object during that period on reasonable data-protection grounds by emailing contact@modeluplink.com.