TALLWRIGHT - DATA PROCESSING AGREEMENT Version dpa-1.3. In force from 2026-11-12. Replaces: 59072eaa1b42e3380f4b8deff8e5b48d873133e9af5bb4252c645dccb5d67e00 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; 1.2 named a company that does not operate the Service. - the agreement is rewritten and shortened throughout, and Annex D is folded into Annex C, which now names each sub-processor's legal entity and the basis of any transfer. - an acceptance names the business and its country (0.3). - the sign-in log and the hosts' admin journals record instructions and acts too (3.2). - the mail provider stores e-mail data in the United States (Annex C). - a nightly copy of the backoffice database goes to the backup storage and is kept thirty-five days (10.3); the hosts' access logs are kept thirty days (A.9). - Annex A describes the data we process for you; what we hold as controller is described in our privacy notice and named in A.4. - an alarm reaches a person as a push message to a phone, and reading a report of a breach makes us aware of it as reading an alarm does (12.1). - account data is deleted three years after the account ends, as the privacy notice states (A.9). 0. The parties, this agreement and its form 0.1 The parties are you - the customer named in the account or in the signed application, as controller or, where clause 1.5 applies, as processor - and us: David Joebstl, entrepreneur (Einzelunternehmer), trading as Tallwright Grazer Strasse 1/3, 8120 Peggau, Austria VAT identification number ATU80827045, hello@tallwright.com "We" and "us" mean that person, who is the processor. hello@tallwright.com is also the contact for data protection. We have appointed no data protection officer, because Article 37(1) GDPR does not require one; if that changes, we name them here. 0.2 This agreement is attached to and governed by the Tallwright Terms of Service, version terms-1.3 (https://app.tallwright.com/legal/terms-1.3.txt). Capitalised terms mean what they mean there, and data protection terms what Article 4 GDPR says. 0.3 It is a contract in electronic form under Article 28(9) GDPR, concluded together with the Terms and recorded as terms-1.3 clause 3 describes: the acceptance screen shows both documents with their SHA-256, asks for the business and its country, and offers acceptance only through one sentence naming both documents and the business. Where you enrol a log with the Witness, the application your key signs names the version an Owner or Admin accepted and its digest; the application records that acceptance and is not itself one, and it is taken only once an acceptance is on file. We process no personal data of yours before this version is in force for you. On request we send you this agreement signed by us. 0.4 Annexes A, B and C form part of it. Annex A is below. Annex B is the technical and organisational measures, today toms-1.3, and Annex C the sub-processor list, today sub-processors-1.3, both at https://app.tallwright.com/legal/. They are incorporated by name and address, not by digest: the version in force is the most recent one notified under clause 6.3 for B or clause 7.3 for C and published there, and nothing either publishes varies this agreement. 0.5 These terms are unusual, and we point them out: the Witness's register entry for your admission, and any refusal, are permanent, and a conclusive refusal is published (14.5); we refuse to dispose of an Archive carrying a retention label, and a disposal waits thirty days after closure (14.3); we keep no register of legal holds, so you declare them in each request (10.2); silence for fourteen days after a sub-processor notice authorises that change (7.4); and the backups of the Archives have no maximum age (10.3). 1. Our role, per Edition 1.1 Accounts and Cloud Proof. In every Edition with an account we are controller of the account relationship: seats, sign-in, the sign-in log, the audit log of what was done to an account, the billing contact, and early access requests sent to us before an account exists. On Cloud Proof we are processor of the Archive metadata: the Record envelope, the operator identifier, the retention label and the hold flag, the fields you send in the clear - your record identifier, the action type, the authority and the stated time - and an Environment's name, deployer label and customer reference. Personal data appears there only where you put it. No Record content reaches us: every Archive the product provisions holds hashes only, and a line carrying a payload or a subject identifier is refused. 1.2 Managed. We are processor of operational metadata only: per box an operator and box identifier, the time the reporting machine wrote into its report, the schema version, a tenant label, a severity, the numbers of records and of anchored records, the age of the oldest unanchored head and codes from a closed set, and the times and counts the receiver keeps per box. No field can carry the text of a finding, and our reporter on your machine cannot open an Archive. 1.3 Witness. The Witness receives no Record content: a log's head, a signature over it and hash-only consistency material. It learns the origin string, which can carry personal data where you chose it - on Cloud Proof we compose the origin from identifiers of ours, naming nothing you chose - the tree size, and the time a request arrives and the network address it comes from; it records the address nowhere and holds it only while the connection is open. For the origin string we are processor. For the enrolment data, the register entry and the arrival time we are controller, on our legitimate interest in a register that shows who presented which log and when (Article 6(1)(f) GDPR), for as long as the register entry lasts (14.5), as our privacy notice describes. 1.4 Self-Hosted. Nothing of ours runs in your estate, and we process no personal data of your data subjects. If you anchor to our Witness, clause 1.3 applies to that traffic. 1.5 Where you are yourself a processor, we are your sub-processor. We follow your controller's instructions as you pass them to us, and yours must not conflict with them. You confirm that your mandate covers engaging us and the sub-processors in Annex C, and you forward to your controller every notice we owe you under clauses 4, 8.4 and 12. 2. Subject matter and duration 2.1 Annex A sets out the subject matter, nature and purpose of the processing, the types of personal data and the categories of data subjects. 2.2 The processing lasts for the term of terms-1.3, extended by clause 14 and by any retention in A.9. 3. Your instructions 3.1 We process your personal data only on your documented instructions, including with regard to transfers to a third country. 3.2 These count as documented instructions: the signed application or the account, and its settings, including the Edition; the product's settings, commands and API parameters you use, documented by the record you keep of what you sent; a written instruction from an Owner or Admin to hello@tallwright.com; and a signed Order Form. On our side, the account audit log keeps a seat's actions, an Archive's access log a search or a query, the sign-in log every sign-in attempt, and each host's admin journal an administrative act of ours on that host. 3.3 What you record is your decision. On Cloud Proof no Payload reaches us (1.1). Nothing of ours detects personal data in what you send; the redaction our recorder applies is described in Annex B. 3.4 We process for the purposes in A.1 and no others. Your Records, Payloads, metadata and telemetry are not used to train, benchmark, evaluate or improve any product, model or service. We open a Payload only on your written instruction, for a support purpose you describe. 3.5 The one exception is processing required of us by Union or Member State law, and we tell you first unless that law forbids it. Where the law requires it, or a court or an authority orders it, we may make an identified record inaccessible; we tell you what we did and why, and every proof over that record stays intact. 3.6 You must not put special categories of personal data, or personal data about criminal convictions and offences, into a Payload without a separate written agreement recording the restrictions and safeguards that then apply. 3.7 You supply the personal data and its lawful basis, tell data subjects what you must, declare what is under hold (10.2), keep your own copy, and satisfy yourself under clause 13 that our measures fit. 4. An instruction we believe is unlawful 4.1 If in our opinion an instruction infringes the GDPR or other Union or Member State data protection law, we tell you immediately and say why. 4.2 We suspend that instruction, and only that one, until you confirm, amend or withdraw it in writing; no suspension stops a recording, an anchor or an export. 4.3 If you then confirm it, we may terminate this agreement and the affected Service on written notice; your export rights under clause 14 survive. 5. Confidentiality 5.1 Access is limited to those who need it for a task, by who holds a host credential and by nothing else; Annex B states what is not enforced. Today one natural person processes personal data for you: the processor named in clause 0.1 (Annex B 9.1). Before we authorise any further person, that person signs a written undertaking of confidentiality covering all personal data processed for you and surviving the engagement. 5.2 Under Section 6 DSG we, and anybody working for us, keep entrusted data secret, transmit it only on an express order, and stay bound after the engagement ends. A right of yours to refuse testimony may not be got around by coming to us instead (Section 6(5) DSG); a demand made to us is governed by clause 8.4. 6. Security 6.1 We take the measures in Annex B under Article 32 GDPR. Annex B also states, in the words "Not in place", what is missing or limited. 6.2 A measure not stated in Annex B, as it stands or as changed under clause 6.3, is not claimed. 6.3 We review the measures at least yearly and whenever the processing or the risk changes materially. We do not lower the protection of a measure without your agreement in writing. Where a provider's change, a security need or the law forces a lowering, we tell Owners and Admins thirty days in advance, naming the measure, its old and new state and the reason; you may object within fourteen days on data protection grounds, and if we cannot keep the level you may terminate the affected Service without penalty, and nothing is billed for the time after it. A notified change is part of Annex B from the day it takes effect. 6.4 No third party has audited or tested the Service's security; our reviews are internal. 7. Sub-processors 7.1 You give us a general written authorisation to engage the sub-processors in Annex C as it stands, and those added or replaced under clause 7.3. 7.2 Annex C names each sub-processor: who it is, what it does for us, what data reaches it, where it processes, and the basis of any transfer outside the EU. 7.3 Before we add or replace a sub-processor we give Owners and Admins at least thirty days' written notice, stating its name, its role, the data that would reach it, where it would process, the basis of any transfer and the date it would begin. Publishing the change is not the notice. Where a provider fails, or must be replaced to avert a material risk to your data, we may replace it sooner and write the same day, naming the reason; your rights under clause 7.4 run from that letter. 7.4 You may object in writing within fourteen days of receiving the notice, on data protection grounds; the period does not start while no address we must write to has received it. We answer within fourteen days. Where we cannot keep your personal data from that sub-processor, you may terminate the affected Service without penalty before it processes your data, or at once after a replacement under the last sentence of clause 7.3, by writing to hello@tallwright.com, effective on receipt; recording does not stop, nothing is billed for the time after it, and your Records, Exhibits and usage basis stay exportable at no charge. Silence for fourteen days authorises that change and nothing else. 7.5 Each sub-processor processes under a data processing agreement with us that imposes on it the data protection obligations Article 28(4) GDPR requires, including the security of processing and the deletion or return of data. We remain fully responsible for its performance, whatever its own terms say, and tell you without undue delay when one fails such an obligation in a way that affects your data. 7.6 On request you receive a copy of a sub-processor agreement and its amendments, redacted only as far as business secrets require. 7.7 If we cease the business or become insolvent, you may require us to instruct each sub-processor to return or delete your personal data, and we give you what you need to deal with that provider directly. Verifying your Exhibits never depends on us or on a sub-processor (terms-1.3 clause 4.4). 8. Transfers outside the EU and the EEA 8.1 We transfer your personal data to a third country or an international organisation only on your documented instruction or where Union or Member State law requires it of us. Engaging the sub-processors in Annex C, as it stands, is such an instruction. 8.2 Annex C states for each sub-processor where it processes and on what basis. Vercel, Neon, Resend and Stripe are companies in the United States, or belong to one, and your personal data can be processed there: the 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. 8.3 This agreement does not by itself make a transfer lawful under Chapter V GDPR. 8.4 If an authority outside the EU demands data we hold for you, or access to it, we tell you before we answer unless the law binding on us forbids it, and then as soon as it permits; we assess whether the demand is lawful and binding on us, and challenge it on reasonable grounds; we disclose the minimum it permits; we record that assessment for you; and where you are yourself a processor, you forward this to your controller. 8.5 Under Article 32 of Regulation (EU) 2023/2854 we do not transfer data held in the EU, or give access to it, where that would conflict with Union or Member State law. 9. Helping you answer a data subject 9.1 A request that reaches us directly is passed to you without undue delay, and we do not answer it unless you authorise us in writing. 9.2 We assist without undue delay and early enough for you to meet your own time limit under Chapter III GDPR; you decide whether a request is admissible and answer it. 9.3 What we can provide: the Records of an Archive, a court export of one Record, a one-use Exhibit link and the usage basis, and from the Archive metadata what it holds for an identifier you give us. Where clause 1.1 makes us controller, we answer ourselves. 9.4 What we cannot do: in an Archive holding hashes only we hold no Payload, no key and no subject identifier, and we have no index that would find a person. Such a request is answered in your own estate, from the content you hold, and you supply any identifier we are to look for. 9.5 A sealed Record cannot be corrected, because any later change to it is detectable; a correction is a new Record that supersedes the earlier one, which stays. 9.6 On your instruction we stop new recording into an Archive, close it, remove or replace a retention label, and revoke a credential we hold for you. You can also close an Environment yourself in the backoffice. 10. Erasure, legal holds and backups 10.1 An Archive holding hashes only holds no Payload, key or salt to erase, so an erasure is done in your own estate, by deleting the content and the salt you hold. Fields you sent in the clear are part of the sealed Records and are removed only by disposing of the book (14.3). The product provisions no Archive holding content; where we hold one nonetheless, an erasure destroys the subject's key and the salts of their records in one act, every proof stays valid, the erasure record names content addresses and never the subject, and we re-apply it after any restore. 10.2 An erasure or a disposal is refused while any record it would touch is under a hold you declare in that request. We keep no register of holds: the obligation behind a hold is yours to know. Each request states the records under hold; one that does not is refused rather than assumed clear, and a conflict is raised to a person. 10.3 Backups. The fleet host backs up every Archive on it and its own configuration, and every night a copy of the backoffice database, which holds the account data in A.4 and the sealed credentials for your fleet; the receiver backs up only the Managed roster - per box the hash of its key and the silence interval - and never a report. All of it is encrypted on the host before it leaves, and is neither searched nor edited. Copies of the backoffice database are kept thirty-five days and leave out the one-day counters of sign-in link requests. Nothing of ours removes the backups of the Archives and of the roster, so they have no maximum age: treat that retention as unbounded in your own records. A deletion reaches a backup only when it expires; backups are used only to recover from a failure, and we re-apply your deletions after any restore. The Witness host has no backup. 11. Helping you with Articles 32 to 36 GDPR 11.1 We assist with your security, breach-notification, impact-assessment and prior-consultation duties, as far as the processing and the information available to us allow: with Annex B and the evidence in clause 13.1, the data flows for your Edition, and clause 12. 11.2 An impact assessment remains yours: we do not run it, and nothing here moves that duty. 12. A personal data breach 12.1 We notify you of a personal data breach affecting personal data we process for you without undue delay after becoming aware of it, and in any event within 48 hours. We become aware when a person of ours reads an alarm or a report of the breach. Alarms reach one person, by a push message, the backoffice watcher's mail or a host's journal, with no on-call rotation, so one raised out of hours may be read only on the next working day; the 48 hours run from that reading, which we note in our notice. That figure is our commitment, not a period the law fixes for a processor. 12.2 We do not first assess whether the breach is likely to result in a risk; that is yours. 12.3 The notice states the nature of the breach, including where possible the categories and approximate number of data subjects and of records concerned; a contact point; the likely consequences; and the measures taken or proposed. What is not yet known follows as soon as we know it. 12.4 We do not notify a supervisory authority or a data subject on your behalf unless you authorise us in writing for that incident; if we do, we give you a copy. 12.5 A separate duty of ours, not about your data: the Witness is a trust service that is not qualified. Under Article 19a eIDAS we notify the supervisory body - the Telekom-Control-Kommission, with RTR-GmbH, under Section 12(1) SVG - within 24 hours of becoming aware of a security breach or disruption with a significant impact on the trust service or on the personal data maintained in it, and the persons that Article names, among them you where you are affected (terms-1.3 clause 6.4). 13. Information and inspection 13.1 On request, once in any twelve months and after an incident affecting you, we give you at no charge, under the confidentiality in clause 13.2: a completed security questionnaire; Annex B with, for each measure, the file that implements it and the tests that hold it and their latest results, redacted only as far as another customer's data or a business secret requires, with the reason; Annex C; the data flows for your Edition; the backup storage's address and layout; the record of the latest restore drill; and the part of our record of processing activities that concerns you. 13.2 You, or an auditor you mandate, may inspect remotely or on site once in any twelve months, on thirty days' written notice, in business hours and under confidentiality, and more often after a material failure or where a supervisory authority requires it. For a hosted Edition the inspection may cover the hosts carrying your Archives: our own access, configuration and records in full, and physical access to the data centre as far as the infrastructure provider permits, otherwise remote inspection and that provider's assurances. The decision and the method are yours, and you may contest the results. 13.3 An inspection is at your cost unless it finds a material failure to meet this agreement or Annex B, when it is at ours. No fee may make these rights impractical, and there is none for the information in clause 13.1 or for our assistance under clauses 9, 11 and 12. 13.4 You may require remedial measures for a shortcoming found; we agree a plan and a date in writing and report completion. We obtain the same rights from a sub-processor where its terms allow. 13.5 A supervisory authority is not restricted by this agreement in any way: no notice period, cost, frequency cap, escort or confidentiality condition applies to it, and we give it inspection results on request. 14. The end of the processing 14.1 When the Service ends, an Owner or Admin chooses in writing between deletion and return of the personal data we process for you. Return means the Records of each Archive and its Exhibits by the paths in clause 9.3, the Archive metadata, and the account's seats, invitations and audit events as files, within fourteen days and at no charge. 14.2 On closure, recording stops, and Records and Exhibits stay exportable at no charge for as long as they are kept (terms-1.3 clauses 9.3 and 16), and at least thirty days, or for any longer period a mandatory provision requires, in particular Article 25 of Regulation (EU) 2023/2854 where it applies. If you ask for nothing, we dispose of nothing. 14.3 Deletion means disposal of a book - every Archive of your account and their Payloads at once - as a supervised act by a person; nothing in the product schedules it. It is refused while any of those Archives is open, within thirty days of closure, while any carries a retention label, or under a hold you declared (10.2). An Owner or Admin removes or replaces a label by written instruction under clause 3.2; we do it by hand, nothing in the product records the change, and we do not assess the obligation behind your decision. We confirm a disposal in writing, naming the Archives, the act and the date. A disposal does not reach backups taken before it (10.3). 14.4 What we keep: invoicing data for seven years, because Section 132 BAO requires it; and the account audit log and the sign-in log, the only records of who changed a seat and who signed in, for as long as the account exists and three years after it ends, on our legitimate interest in answering a later dispute or an authority (Article 6(1)(f) GDPR). Such a row is removed by a deliberate administrative act at the end of that period, never by the application. 14.5 What we never delete: the Witness's register entry for your admission, and any refusal. We do not edit them, and a refusal is answered only by a later dated statement. An entry names your organisation, your operator identifier and your keys, and no data subject. Where a refusal is conclusive we publish it, telling you first, and we publish no origin string we know to name a natural person. The Witness pushes its register to the backoffice, which holds a copy it can neither edit nor invent but could withhold. The Witness host has no backup, so permanence is a rule we keep, not a guarantee against losing that machine. 14.6 Until deletion or return is complete, every clause here keeps applying. 15. Records, liability, precedence and changes 15.1 We keep the record of processing activities that Article 30(2) GDPR requires, and give you the part that concerns you on request. 15.2 Each of us answers for its own compliance. Liability between us is governed by terms-1.3 clause 13; nothing here limits a data subject's rights or Article 82 GDPR. 15.3 For personal data this agreement prevails over terms-1.3, and a signed Order Form prevails over both. Austrian law governs, and terms-1.3 clause 22 fixes the venue. English is authoritative. "In writing" and "written" here mean text form, such as e-mail (terms-1.3 clause 19.1). 15.4 We do not change this agreement by publishing a change. A new version is a new file at its own address naming the SHA-256 of this one, notified to Owners and Admins at least thirty days in advance; the version you accepted governs until an Owner or Admin accepts another, as terms-1.3 clause 18 says, and the Terms and this agreement change together. You may end this agreement and the affected Service at any time by writing to hello@tallwright.com (terms-1.3 clause 15.2). Either of us may terminate for a material breach left unremedied thirty days after written notice. ANNEX A - DESCRIPTION OF THE PROCESSING A.1 Subject matter and purposes. The processing of the personal data in what you send us (listed in A.4) to operate the Edition you use: to provision and operate Archives; to receive and seal Records; to present heads to the Witness and keep its cosignatures; to produce Exhibits and exports; to show your Archives in the backoffice and report a fault; and to meter usage for invoicing. No others. A.2 Nature. Collection, recording, organisation, storage, encryption, hashing, transmission of hashes and signatures, retrieval for display and export, backup, and disposal of an Archive. A.3 Categories of data subjects. - Your personnel and contractors who hold a seat or act through one, as far as the data below names them. - Anyone identifiable from a field you send in the clear on Cloud Proof - a record identifier, an action type, an authority, or an Environment's name, deployer label or customer reference - or from an origin string you compose. A.4 Categories of personal data. - Archive metadata: record identifier, previous record hash, payload hash, time, agent system identifier and version, deployer label, operator identifier, event type, action type, actor authority, retention label, hold flag, gap manifest. A Record carries no content, and personal data appears here only in a field you control. - Environments: the name, deployer label and customer reference you give each, who asked for it and when, and when it was closed. - The origin string of a log you enrol with the Witness (1.3). - Managed telemetry: the fields in clause 1.2 and nothing else. - Mail we send about your Archives and Environments: the recipient address, the subject and a plain-text body that can carry an account name, an operator identifier, a register entry number and the sentence an Exhibit bears. - What we hold as controller (1.1, 1.3) is described in our privacy notice and is not processed on your instructions: the account, its seats, invitations, sessions, passkeys, account keys and audit log; sign-ins; acceptance records; billing data; the mail we send about the account, with its sign-in, invitation and account-creation links and acceptance confirmations; early access requests; the Witness's enrolment data and register, and the copy of it in the backoffice; the one-day counters of sign-in link requests; and the access logs of the fleet and receiver hosts, which note per request the time, the request line, with a one-use Exhibit link cut to its first segment, and the network address it came from, kept for at most thirty days. A.5 Special categories. None is asserted and none is intended; clause 3.6 governs. Nothing in the product detects such data. A.6 Frequency. Continuous for recording. Anchoring about every fifteen minutes per Archive, which is not a service level, and with no bound on how long a Record stays unanchored while the Witness is unreachable. On each event for account actions; every fifteen minutes for the watcher that reads your Archives' state; daily for metering and monthly for invoicing; nightly for backups; on request for exports and disposals. A.7 Duration. As clause 2.2 states. A.8 Locations. The Witness host and the fleet host are separate machines in one data centre in Falkenstein, Germany; the Managed receiver is in Helsinki, Finland; the backup storage is in an EU data centre of Hetzner (Annex C 1.6). The backoffice database is in Amazon Web Services' Frankfurt region, and the backoffice's server code runs in Frankfurt. No test environment holds a copy of your data. Archives we host are stored in the EU, and the record metadata the backoffice shows passes through Vercel (Annex C 1.1); on Self-Hosted and Managed the Archive is on your machine and its place is yours. A.9 Retention, for the data in A.4 and, so that it is in one place, for what we hold as controller. - Records: while the Archive is open, then as clauses 14.2 and 14.3 say. - Enforced by our code: a session 8 hours; a sign-in link 10 minutes, single-use; an invitation 7 days; a provisioning claim 5 minutes; an Exhibit link 15 minutes, single-use; the link that approves an early access request 7 days, and the link that then creates the account 72 hours; an entry counting sign-in link requests one day; the Managed receiver keeps only the newest accepted report per box. - Set in each host's configuration: access logs on the hosts, thirty days. - Set at the provider, not by our code: the backoffice database's point-in-time history, six hours. - Copies of the backoffice database in the backup storage: thirty-five days, removed by the nightly run, without the counters of sign-in link requests. - Users, memberships, invitations, audit events, sign-in attempts, acceptances and account keys: deleted by no code path; we delete them by a deliberate act three years after the account ends, as our privacy notice states, and clause 14.4 governs the account audit log and the sign-in log. Removing a member sets a removal time and revokes their sessions. - Environments: deleted by no code path; at the end of the processing as clause 14.1 says. - Usage days and billing periods: as invoicing data. - The admissions copy in the backoffice: as the register it copies (14.5). - Early access requests: until the early access phase ends; those that did not lead to an account are deleted then. - Invoicing data: seven years (Section 132 BAO). - The Witness's register entry and any refusal: permanent (14.5). - Backups of the fleet host's Archives and configuration and of the receiver's roster: no maximum age (10.3). ANNEX B - TECHNICAL AND ORGANISATIONAL MEASURES The technical and organisational measures, today toms-1.3 at https://app.tallwright.com/legal/toms-1.3.txt, incorporated by name and address under clause 0.4. ANNEX C - SUB-PROCESSORS The sub-processor list, today sub-processors-1.3 at https://app.tallwright.com/legal/sub-processors-1.3.txt, incorporated by name and address under clause 0.4. It names each sub-processor's legal entity, role, data, place of processing and basis of transfer, and the third parties that receive no personal data of yours.