TALLWRIGHT - PRIVACY NOTICE
This notice says what we do with personal data as controller: when you visit our websites, request early access, sign in to the backoffice, conclude the contract for a business, pay, or write to us. It is information under Articles 13 and 14 GDPR. You do not accept it, and nothing in it asks for your consent.
Where a customer sends records to the Service, the customer is the controller of any personal data in them, and we process it on the customer's behalf under our Data Processing Agreement (https://app.tallwright.com/legal/dpa-1.3.txt). Please ask that customer about it.
1. WHO IS RESPONSIBLE
1.1 David Joebstl, entrepreneur, trading as Tallwright
Grazer Strasse 1/3, 8120 Peggau, Austria
E-mail: hello@tallwright.com
1.2 Write to the same address about anything in this notice. We have not appointed a data protection officer, because Article 37 GDPR does not require one for our processing.
2. WHAT WE PROCESS, WHY, AND FOR HOW LONG
2.1 Visiting our websites (tallwright.com and its subdomains, such as app.tallwright.com and verify.tallwright.com).
Data: your IP address, the date and time, the address requested, and what your browser says about itself, which every request carries.
Purpose: delivering the pages and keeping them secure.
Legal basis: Article 6(1)(f) GDPR; our interest is a working and secure website.
Retention: our hosting provider keeps request and function logs for a short period set by its service, at most thirty days. We run no web analytics, no tracking and no advertising. The browser verifier at verify.tallwright.com checks a file inside your browser; the file is not sent to us.
2.2 Requesting early access.
Data: what you enter on the website's form or in the backoffice - name, work e-mail address, company and what you tell us about your needs - when you asked, and who approved it and when.
Purpose: deciding on the request and writing to you about it.
Legal basis: Article 6(1)(b) GDPR where you ask for yourself; where you ask for a business, Article 6(1)(f) GDPR, our interest in answering it.
Retention: until the early access phase ends; requests that did not lead to an account are deleted then, and earlier if you ask. Requests made on the website are also kept in our CRM (clause 3).
2.3 Signing in and using the backoffice.
Data: your e-mail address and name, your role, invitations (the address invited and who invited it); per session how you signed in, your browser's description of itself and the times; per sign-in attempt the time, the method and, if it was refused, why; per passkey its identifier, public key and times; per account key its name, its first characters, its hash and who made it; and the account's log of changes to seats and settings, which names who made each change.
Purpose: providing the account to the business that uses it, keeping it secure, and being able to show who changed what.
Legal basis: Article 6(1)(b) GDPR where you are our contracting party yourself; otherwise Article 6(1)(f) GDPR, our interest in providing the account your organisation uses and in keeping it secure.
Source: where a colleague invites you, we receive your address from them.
Retention: a sign-in link is valid for 10 minutes, a session for 8 hours and an invitation for 7 days; their records, and the rest, are kept for as long as the account exists and three years after it ends (the limitation period for damages, Section 1489 ABGB), then deleted.
2.4 Protecting sign-in against abuse.
Data: for one day, the SHA-256 of an address a sign-in link was asked for, and a keyed hash of the network address that asked, under a secret only our deployment holds. The address hash is not salted, so an address can be confirmed by trying candidates; we treat both as personal data.
Purpose: limiting how often links can be requested. Legal basis: Article 6(1)(f) GDPR, our interest in preventing abuse. Retention: one day, deleted by the code.
2.5 Concluding the contract for a business.
Data: the business name and country you enter, the sentence you tick, your e-mail address, the time, your browser's description of itself, and the versions and SHA-256 of the documents you accepted. We keep no IP address and no location.
Purpose: concluding the contract, being able to prove what was agreed, and sending you the confirmation.
Legal basis: Article 6(1)(b) GDPR; for the proof, Article 6(1)(f) GDPR.
Retention: for as long as the contract lasts and three years after it ends; longer only while a dispute about it is pending.
2.6 Billing and payment.
Data: the business's name, register number or VAT identification number, billing address and country, whether the European Commission's VIES service refused the VAT number, our payment provider's customer identifier, the e-mail address of the person who receives invoices, and what was billed. Card data is entered on our payment provider's page and never reaches us.
Source: the person who concludes the contract or manages billing for the business.
Purpose: invoicing, collecting payment and meeting our tax duties.
Legal basis: Article 6(1)(b) and (c) GDPR (Section 132 BAO, Section 11 UStG).
Retention: seven years from the end of the year concerned (Section 132 BAO).
2.7 E-mail we send and e-mail you send us.
Data: your address, the subject and the text, which can carry a one-use link.
Purpose: sign-in links, invitations, confirmations and notices; answering you.
Legal basis: Article 6(1)(b) GDPR, and for messages that are not about a contract Article 6(1)(f) GDPR, our interest in answering them. Retention: our mailbox keeps your message for as long as we need it to answer and to document a contract, at most three years after the matter ends; Resend keeps the messages we send for the period its service sets.
2.8 Operating our servers.
Data: the web servers of our hosts note, per request to the Service's public addresses, the time, the request line and the network address it came from.
Purpose: security and fault finding. Legal basis: Article 6(1)(f) GDPR.
Retention: at most thirty days. The Witness keeps no request log; it holds a network address in memory only while the connection is open.
2.9 The Witness register.
Data: for a log enrolled with the Witness, the operator identifier, the organisation name, public keys, delegate and applicant domain given at enrolment, the signed application, the versions of our documents accepted, and the time each head is presented.
Source: the business that enrols the log.
Purpose: running the register, and being able to show who presented which log and when.
Legal basis: Article 6(1)(f) GDPR, our interest in a register that can be checked.
Retention: permanent; an entry is never edited. A conclusive refusal is published: origin strings, sizes and root hashes, never content, and no origin string we know to name a natural person.
2.10 Backups.
Purpose: restoring the Service after a failure. Legal basis: Article 6(1)(f) GDPR, our interest in not losing data.
Encrypted copies of the backoffice database are made every night and kept thirty-five days, without the data of 2.4; a deletion reaches them when they expire, and we re-apply it after any restore. Backups of our servers and of the Archives have no maximum age; they hold no account data beyond the fleet's own configuration.
2.11 Testing.
Data: a copy of the backoffice database as it stood on 18 September 2026, before the launch, with the test and pilot accounts of that day.
Purpose: testing changes on a separate staging system before they reach the live Service.
Legal basis: Article 6(1)(f) GDPR, our interest in a Service that works.
Retention: until we replace the copy with test data, at the latest three months after this notice comes into force. It is used for nothing else, and it holds no data of a customer under our documents in version 1.3.
3. WHO RECEIVES IT
3.1 Our processors, each bound by a data processing agreement:
Vercel Inc., USA - hosting of the websites and the backoffice (server code in Frankfurt, delivered through Vercel's global network);
Neon (Neon, Inc., a Databricks company, USA) - the backoffice database, stored in Amazon Web Services' data centre in Frankfurt;
Hetzner Online GmbH, Germany - our servers in Germany and Finland and our encrypted backups in the EU;
Resend, Inc., USA - sending our e-mail; Resend stores e-mail data in the USA;
HubSpot, Inc., USA - our CRM for early access requests made on the website, hosted in HubSpot's EU data centre in Germany;
World4You Internet Services GmbH, Austria - our mailbox and our DNS.
3.2 Stripe Payments Europe, Limited, Ireland, processes payment and invoicing data. For its own legal duties, such as fraud prevention and anti-money-laundering checks, Stripe is a controller in its own right; see stripe.com/privacy. Stripe checks VAT identification numbers with the European Commission's VIES service.
3.3 Where the law requires it: courts, authorities and our tax adviser. We sell no personal data and give none to advertisers.
3.4 Our alarm messages go to a public push service; they name a host and a failed service and carry no personal data.
4. TRANSFERS OUTSIDE THE EU
4.1 Vercel, Neon, Resend, HubSpot and Stripe are companies in the United States, or belong to one, and personal data can be processed there. For each of them the transfer rests on its certification under the EU-U.S. Data Privacy Framework (the European Commission's adequacy decision of 10 July 2023) and on the EU standard contractual clauses in its data processing agreement. You can ask us for a copy of the safeguards.
5. COOKIES
5.1 The website sets no cookies and stores nothing on your device.
5.2 The backoffice sets only cookies it needs to work: the session cookie that keeps you signed in (at most 8 hours), and short-lived cookies that bind a sign-in link to the browser that asked for it, carry a passkey challenge, or hand over a key or an Exhibit link once. None is used for analytics or advertising, so no consent is asked for (Section 165(3) TKG 2021).
6. YOUR RIGHTS
6.1 You may ask for access to your personal data, its correction or deletion, a restriction of its processing, and a copy in a portable format (Articles 15 to 20 GDPR). You may object at any time, on grounds relating to your situation, to processing based on Article 6(1)(f) GDPR (Article 21 GDPR). Write to hello@tallwright.com.
6.2 You may complain to a supervisory authority, in Austria the Datenschutzbehoerde, Barichgasse 40-42, 1030 Vienna, dsb@dsb.gv.at, https://www.dsb.gv.at.
7. WHAT YOU MUST PROVIDE
7.1 An e-mail address is needed to sign in. The business name and country are needed to conclude the contract, and billing data for a paid plan. Without them we cannot provide the account or the contract; nothing else is required.
8. NO AUTOMATED DECISIONS
8.1 We make no decisions based solely on automated processing, including profiling, that have legal or similarly significant effects on you. An early access request is decided by a person.
9. CHANGES
9.1 A new version of this notice is a new file at its own address. We tell the Owners and Admins of each account about a material change.