TALLWRIGHT - SUB-PROCESSOR LIST Version sub-processors-1.3. In force from 2026-11-12. Replaces: 0b5685cd2cc9eb64be8d4021b09b66b82fd17cc4c394dadb031f0c58f55aa4d1 The SHA-256 of this file, with CRLF normalised to LF, is listed in https://app.tallwright.com/legal/SHA256SUMS.txt and on https://app.tallwright.com/legal. What changed from 1.2: - the processor is David Joebstl, an individual entrepreneur in Austria; versions 1.0 to 1.2 named a company that does not operate the Service. - each provider's legal entity and the basis of any transfer are named here; Annex D of the agreement is folded into this list. - the mail provider stores e-mail data in the United States (1.3); the backoffice database is copied nightly to the backup storage (1.6); the push service for our alarms (3.3) and the CRM of the website's early access form (3.4) are listed. - the list is shortened: the dates of our own readings and machine details are given on request. Annex C to the Data Processing Agreement (dpa-1.3). Processor: David Joebstl, entrepreneur (Einzelunternehmer), trading as Tallwright, Grazer Strasse 1/3, 8120 Peggau, Austria. VAT identification number ATU80827045. hello@tallwright.com "We" is David Joebstl, who provides the Service under the name Tallwright, and "you" the customer; other terms mean what terms-1.3 and dpa-1.3 say. English is authoritative. 0. Status of this list 0.1 It names every company we engage that receives data of yours: what each does, which data reaches it, where it processes and the basis of any transfer outside the EU. Section 1 lists those that receive personal data of yours, section 3 those that receive none. A company reached only through another is named in that provider's entry. It is accurate at the date above. Each provider account is held by us, and each provider's data processing terms were accepted by us. On request we give each company's registered office and data protection contact. 0.2 Which version of this list is in force, and how a sub-processor is added or replaced, is governed by dpa-1.3 (clauses 0.4, 7.3 and 7.4): we write to every Owner and Admin at least thirty days before a new one begins processing, naming the date, and you may object. Publishing a new version of this list is not that notice. Where another page of ours names fewer providers or says less about one, this list prevails; nothing published here varies the agreement. 1. Processors of personal data 1.1 Backoffice hosting - Vercel Inc., United States. Hosts the backoffice and our websites. Everything the backoffice holds passes through it: the account data in Annex A.4 of dpa-1.3, Environments with their names, labels and customer references, the copy of the Witness's admissions register, and the credentials for your fleet, sealed under a key that is held in Vercel's deployment environment and not in the database, so Vercel holds both the sealed credentials and the key, and Neon neither. Server code runs in Frankfurt, Germany; pages are delivered through Vercel's global network, and builds and platform logs are not pinned to a region. Transfer: the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses in Vercel's data processing terms. 1.2 Backoffice database - Neon, Inc., a Databricks company, United States. Stores the data in 1.1 in Amazon Web Services' Europe Central 1 region in Frankfurt, so Amazon holds those bytes, with six hours of point-in-time history at Neon; a nightly encrypted copy goes to the storage in 1.6. Transfer, where Neon accesses the data from outside the EU: the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses in Neon's data processing terms. 1.3 Outbound product mail - Resend, Inc., United States. The recipient address, the subject and a plain-text body that can carry a one-use sign-in, invitation or account-creation link, an account name, an operator identifier, a register entry number, the confirmation of an acceptance and the sentence an Exhibit bears. No tracking. Resend stores e-mail data in the United States, whichever region a message is sent from. Transfer: the Standard Contractual Clauses in Resend's data processing terms and the EU-U.S. Data Privacy Framework. 1.4 Payments - Stripe Payments Europe, Limited, Ireland, with Stripe, Inc., United States. Payment processing, invoicing and VAT. It receives an account name or operator identifier, the e-mail address of the person who receives invoices, account metadata and a monthly quantity and, once the contracting company is on file in Settings, that company's name, billing address and country, and its VAT identification number where it is an EU VAT number, from which Stripe Tax works out the VAT on an invoice. A card is entered on Stripe's own page and never reaches us. For its own legal duties, such as fraud prevention and anti-money-laundering checks, Stripe is a controller in its own right. Transfer: the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses in Stripe's data processing terms. 1.5 Servers - Hetzner Online GmbH, Germany. The Witness host and the fleet host that carries hosted Archives, separate machines in one data centre in Falkenstein, Germany, and the Managed receiver in Helsinki, Finland; a fourth server is our staging host and carries no Archive of yours. Hetzner holds no credential to our services, but runs the machines, whose disks we do not encrypt (toms-1.3 clause 2.3). Processing in the EU. 1.6 Backup storage - Hetzner Online GmbH, the provider in 1.5: a storage service in one of its EU data centres. The fleet host sends every Archive on it, its configuration and, nightly, a copy of the backoffice database, which holds the data in 1.1; the receiver sends only its roster of boxes, never a report; the Witness host sends nothing. Everything is encrypted on the host before it leaves. No payload and no subject identifier of yours is there, because every Archive the product provisions holds hashes only. Its address and layout are given under clause 13.1 of dpa-1.3. Processing in the EU. 1.7 DNS and inbound mail - World4You Internet Services GmbH, Linz, Austria. DNS for tallwright.com and the mailbox for hello@tallwright.com, which also receives our early access notices: what you write to us, and the address, company and note of a person asking for early access. Processing in Austria. 1.8 Identity providers - none connected. Sign-in is a one-use link sent by e-mail or a passkey in your own browser. The code ships connectors for Google and GitHub sign-in; neither is connected in production, and any we connect appears on the sign-in screen and in this list. 1.9 Place of processing, and the law the infrastructure is subject to. Archives we host are stored in the EU, and the record metadata the backoffice shows passes through Vercel (1.1); on Self-Hosted and Managed the Archive is on your own machine and its place is yours. Vercel, Neon, Resend and Stripe are companies in the United States, or belong to one, and data of yours can be processed there; each transfer rests on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework of 10 July 2023, for each company certified under it, and on the EU Standard Contractual Clauses in its data processing terms. Hetzner and World4You process in the EU. Under Article 28 of Regulation (EU) 2023/2854: the hosts and the backups are run by a German company under EU law; the backoffice and its database by Vercel Inc. and Neon, Inc., companies in the United States, which may be subject to the law of the United States. Our measures against unlawful access by authorities outside the EU: we hold no record content, credentials are sealed under a key that Vercel also holds (1.1), and dpa-1.3 clauses 8.4 and 8.5 say how we answer a demand. 2. What each Edition reaches 2.1 Self-Hosted. Nothing in section 1, except 1.1 to 1.4 for account data if you hold an account. Nothing of ours runs in your estate, and nothing we ship calls out but to a Witness address and a time-stamping address you configure. 2.2 Witness. The Witness host (1.5), the time sources (3.2), and 1.1 to 1.4 for account data. It receives a log's head, a signature over it and hash-only proof material, the origin string and enrolment data, never a record, payload or subject identifier; it learns the network address of a request and records it nowhere. 2.3 Managed. As 2.2, plus the receiver (1.5) and the backup of its roster (1.6). Per box it receives a key hash, times, counts and status codes from a closed set, and keeps only the newest accepted report. Our reporter on your machine only reads and cannot open an Archive. The enrolment of customers' boxes is not in service yet. 2.4 Cloud Proof. As 2.2, plus the fleet host (1.5), the backup storage (1.6) and the certificate authorities (3.1). Each Record carries your record identifier, the address computed from your salt and content, and the action type, authority and stated time where you send them; the content and the salt stay with you. 2.5 In every Edition, no payload and no subject identifier reaches 1.1 to 1.4. The backoffice reads record metadata from your fleet host and shows it without keeping it. An origin string on a log you enrol is yours to compose and can identify a person; nothing here requires one that does. On Cloud Proof we compose the origin, and what you compose is an Environment's name, deployer label and customer reference, which the backoffice keeps. 3. Third parties that receive no personal data of yours 3.1 Certificate authorities - Let's Encrypt, operated by the Internet Security Research Group, United States, with ZeroSSL as the fallback, certify our hosts and receive their public hostnames, their addresses and an operations e-mail address; the backoffice is certified by the platform in 1.1. The Witness uses none, by design: you authenticate it by its public key. 3.2 Network time - Cloudflare (United States), Netnod (Sweden) and the Physikalisch-Technische Bundesanstalt (Germany) provide the authenticated time the Witness host's clock follows. 3.3 Push notifications for our alarms - ntfy.sh, a public push notification service. When a service on one of our hosts fails or recovers, and once a week as a test from the fleet and receiver hosts, the host sends the service's name and the host's name, and for the probe its last lines, which name only our own services. A service's name can include a book's identifier, which names an account's log and no person; no record, payload, account data or address of yours is sent. 3.4 The CRM of our website - HubSpot, Inc., United States, hosted in its EU data centre in Germany. It receives early access requests sent through the website's form by people who are not yet customers. That is our own processing as controller, described in our privacy notice; it receives no data of yours as our customer. 4. Build and supply chain These touch code, not your data, so an addition here is not a sub-processor change; one that ever receives personal data of yours moves to section 1, under dpa-1.3 clause 7.3. GitHub, Inc. (Microsoft, United States) holds our code, runs the build checks and holds the repository the public Cloud SDK is published from. Package sources: PyPI, the npm registry, Cloudsmith, the Debian and Ubuntu mirrors, and the PostgreSQL project's package repository. 5. Deliberately absent 5.1 We are not a qualified trust service provider, and no external time-stamping authority is in the anchoring path of any deployment we run. A Self-Hosted operator who configures a time-stamping address chooses that provider, which is theirs and not a sub-processor of ours. No transparency-log service, no blockchain. 5.2 No analytics, advertising tracker or error-reporting component in the backoffice or on the website, and no third-party asset loads while a page of ours is open. 5.3 No AI provider is a third party of ours: the AI services your agent calls are yours. 6. Versions 6.1 Every version of this list has its own name and address, which keep answering after it is superseded, and names the SHA-256 of its predecessor. Which version is in force is governed by dpa-1.3, not by this file.