Skip to content
Unforged DevelopersSecurityPricing
Sign in Get started
Sign in Get started

Legal

Data processing addendum

Last updated 26 October 2026 · Version 1.10

Contents
  1. 01Scope and roles
  2. 02The processing
  3. 03Your instructions
  4. 04Your responsibilities
  5. 05Our people
  6. 06Security measures
  7. 07Subprocessors
  8. 08Helping you meet your obligations
  9. 09Personal data breaches
  10. 10Deletion or return
  11. 11Audits
  12. 12International transfers
  13. 13No training
  14. 14Contact
01

Scope and roles

In short This addendum is part of the terms of service. You are the controller of customer data; we process it for you, on your instructions.

This addendum forms part of the terms of service between you and Unforged Ltd. It applies when we process personal data in the documents, reference signatures and other data you send to Unforged (customer data) on your behalf. For that data you are the controller and we are your processor, under the UK GDPR and, where it applies, the EU GDPR. If this addendum and the terms conflict on data protection, this addendum wins.

02

The processing

In short What we process, about whom, why, and for how long: the details Article 28 asks for.

  • Subject matter and purpose: checking signatures on documents against the reference signatures you enrol and returning verdicts with reasons (Nib); keeping, finding and accounting for the records you file (Folio); sending documents to be signed and recording how each person signed (Sig); and holding your clients, matters, documents and email (Desk).
  • Nature: receiving, storing, comparing, reading the text of, searching, retrieving, sending and deleting data, and delivering results by API, webhook, email and the web app.
  • Data subjects: the people whose signatures and documents you send us, the people you send documents to sign, your clients and contacts, the people who email you through Desk, and anyone named in those documents.
  • Types of data: documents, reference signatures, check results, the subject references you use to identify people, and your webhook settings; records and the text read from them, and the ledger of who did what to each; signers’ names, email addresses, devices, the times they opened and signed, and, where they allow it, a short camera video and where they were; and clients’ and contacts’ details, matters, notes and email. Signatures and their comparison, and a signer’s camera video, can be biometric data, a special category. Desk can hold other special category data when you put it there.
  • Duration: documents and results are kept for your organisation’s history-retention setting: 90 days by default, and you can choose from 30 minutes to 10 years, or indefinitely. Uploaded documents are kept with their results under the same setting. A document sent to Loupe is kept while its check waits for a decision, and one your team marks as altered is kept, with its check, while your account is open. Reference signatures are kept until you delete them; a check that a learned reference came from is kept while that reference exists. Folio records are kept for their retention class, and Locked records cannot be deleted before it ends. Sig packages, their evidence and Desk’s records are kept while your account is open, until you delete them. At the end of the service, see deletion or return.
03

Your instructions

In short We act only on your documented instructions: these terms, your settings and your API calls.

We process customer data only on your documented instructions: these terms, the settings you choose and the requests you make through the API and the dashboard. If we think an instruction breaks data protection law, we will tell you. If the law requires us to process customer data otherwise, we will tell you first unless the law forbids it.

04

Your responsibilities

In short Signatures can be biometric data. You need a lawful basis, and any consent the law requires, for what you send us.

You are responsible for having a lawful basis for the processing, including a condition for special category data where one is needed, for getting any consent the law requires from the people whose signatures you send, and for telling them how their data is used. Reference learning is off by default; if you switch it on, approved signatures are added to that same person’s references only, and you are responsible for having a basis for keeping them.

05

Our people

In short Everyone who can access customer data is bound to keep it confidential.

Only people who need access to run and support Unforged can reach customer data, and each of them is bound by a duty of confidentiality.

06

Security measures

In short We protect customer data with the technical and organisational measures described on our security page.

We apply appropriate technical and organisational measures to protect customer data, including encryption in transit, isolation between organisations, access control, and audit logging. The measures, and how they work, are described on our security page. We may improve them over time, but will not make them less protective overall.

07

Subprocessors

In short These vendors help us run Unforged. We tell you before we add or replace one, and you can object.

You authorise us to use the subprocessors below. Each is bound by written terms that protect customer data at least as well as this addendum, and we remain responsible for them.

Subprocessors, as of the date above
NamePurposeDataLocation
Amazon Web ServicesHosting: the servers, database, file storage, queues and keys that run UnforgedAll customer data, and account and usage recordsLondon, UK (eu-west-2), or the region your contract names
CloudflareDNS, the network in front of unforged.ai (the website and dashboard), and cookieless website analyticsTraffic to unforged.ai in transit, including documents uploaded in the dashboard, and anonymous page-view analytics (page, referrer, country, device). API traffic does not pass through it.See the vendor’s terms
PostHogProduct analytics: how people use our website and the signed-in appThe pages you visit and what you click in the app, your user and organisation identifiers, your organisation’s name, plan and region, your browser and device, and your IP address, used to find your country. Never the contents of documents, file names or signatures.European Union (Frankfurt, Germany)
WorkOSSign-in, single sign-on and directory syncUsers’ names, email addresses, organisation memberships and rolesSee the vendor’s terms
StripePayments, invoices and usage billingOrganisation name, billing email, payment details and counts of billable checksSee the vendor’s terms
ResendSending our transactional emailRecipients’ email addresses, and the messages we send, including signing invitations and the email Desk sends for youSee the vendor’s terms
MapboxThe small map of where each person signed, on Sig’s certificate of signingThe approximate coordinates a signer shared when signing. Never names, documents or signatures.See the vendor’s terms
Google WorkspaceOur own email, including [email protected]What you send us by email, and contact-form requestsSee the vendor’s terms
ChatlioThe chat on our websiteWhat you write to us in the chat, the page you were on, your browser and device, and your email address if you leave itSee the vendor’s terms
SlackWhere our team reads and answers the website chatWhat you write to us in the chat, and your email address if you leave itSee the vendor’s terms

When Loupe checks a document, we look up the VAT, company and firm numbers and the web addresses on it with the public registers that hold them: HMRC, the European Commission, Companies House, the Financial Conduct Authority and each web address’s registry. They answer as public bodies, not as our subprocessors, and we send them only the number or the address, never the document. If you run Loupe on your own servers with the lookups switched on, it sends us those numbers and addresses, and we look them up the same way.

For each document Loupe checks, we keep a few measurements of how it’s laid out, such as the size of its text and where the issuer’s name sits, along with the name of the issuer it shows. They hold no personal data and none of the document’s other text, and they’re deleted with the check. When someone in your organisation decides a check was genuine, we use those measurements, together with other customers’ decisions, to learn how that issuer lays out its documents, so that a document claiming to come from them on someone else’s layout stands out. Other customers never see which organisation a decision came from.

Before we add or replace a subprocessor, we update this page and email your account owners. If you object on reasonable data protection grounds, tell us at [email protected]; we will work with you on it, and if we cannot resolve it you may stop using the affected service.

08

Helping you meet your obligations

In short We help you answer data subject requests and with impact assessments and regulator enquiries.

We help you answer requests from data subjects. You can find a person’s data by the subject reference you gave them, and delete a subject, with their references and files, through the API. If a data subject contacts us directly, we pass the request to you and do not answer it ourselves unless you ask us to.

We also give you reasonable help with data protection impact assessments, consultations with regulators, and your security obligations, taking into account the information we have.

09

Personal data breaches

In short If a breach affects customer data, we tell you without undue delay and help you respond.

If we become aware of a personal data breach affecting customer data, we will tell you without undue delay. We will give you the information you need to meet your own obligations, as it becomes available: what happened, the data and people likely to be affected, the likely consequences, and what we are doing about it.

10

Deletion or return

In short While the service runs, customer data is deleted on your retention settings. At the end, you export what you need, and we delete other customer data when you ask, apart from Locked records still inside their retention.

While the service runs, customer data is deleted on your retention setting, and you can delete subjects and references at any time through the API.

At the end of the service, return is by exporting your results, records and signed copies through the API or the web app; other customer data is deleted when you ask us to, unless law requires us to keep it. Locked records in Folio stay until their retention ends. When your account closes we delete your organisation’s records (settings, keys and check history). Stored files — documents, reference images and result files — are deleted when you ask us to (email [email protected]), unless law requires us to keep them. Billing and audit records are kept, as the terms describe. Database backups are kept for 35 days, so data deleted from the database leaves them within 35 days.

11

Audits

In short We give you the information you need to check we comply, and allow a reasonable audit at most once a year.

We will make available the information you reasonably need to show that we meet this addendum. On request, we will allow a reasonable audit or inspection by you or an independent auditor you choose, bound by confidentiality, with reasonable notice and at a time agreed with us. Audits are limited to once a year, unless a regulator requires more or a breach makes one necessary.

12

International transfers

In short Customer data is stored in London, UK, unless your contract names another region, and stays there. Where a subprocessor handles it outside the UK or EU, safeguards apply.

Customer data is stored with Amazon Web Services in London, UK (eu-west-2), unless your contract names another region. It stays in that region unless you ask us to move it. If your contract names a region outside the UK, your customer data is stored there on your instruction.

Our website and dashboard run in London, so what you upload or view in the dashboard passes through London on its way to and from your region, without being stored there. We also keep the list of which organisation is in which region in London; it holds identifiers only, none of your customer data.

Where a subprocessor may process customer data outside the UK or the EU, we rely on an adequacy decision or appropriate safeguards where applicable, such as the UK International Data Transfer Agreement or Addendum and the EU Standard Contractual Clauses.

13

No training

In short Customer data is never used to train anything.

We never use customer data to train anything, and we never sell it. The one opt-in, reference learning, adds approved signatures to that same person’s references in your organisation and nowhere else.

14

Contact

In short Questions about this addendum go to [email protected].

Email [email protected], or write to Unforged Ltd, 3F1 Third Floor, 3 Hill Street, Edinburgh, Scotland, EH2 3JP.

Unforged is run by Unforged Ltd, registered in Scotland, company no. SC905483, ICO registration ZC275012. Registered office: 3F1 Third Floor, 3 Hill Street, Edinburgh, Scotland, EH2 3JP. Email [email protected].

On this page

  1. 01Scope and roles
  2. 02The processing
  3. 03Your instructions
  4. 04Your responsibilities
  5. 05Our people
  6. 06Security measures
  7. 07Subprocessors
  8. 08Helping you meet your obligations
  9. 09Personal data breaches
  10. 10Deletion or return
  11. 11Audits
  12. 12International transfers
  13. 13No training
  14. 14Contact
Unforged
Theme
Products
  • Nib
  • Folio
  • Sig
  • Desk
  • Loupe
  • Assay
  • Timbre
Nib
  • Unforged Nib
  • Use cases
  • Developers
  • Changelog
  • AI assistants
  • Security
  • Responsible disclosure
  • Our testing protocol
  • Compare
  • Guides
  • Glossary
  • Pricing
  • About
Company
  • About
  • Articles
  • Help centre
  • Talk to us
  • Regions
  • Status
  • Sign in
Legal
  • Terms
  • Privacy
  • DPA & subprocessors
  • Cookies

Cyber Essentials certified

© 2026 Unforged Ltd Registered in Scotland, company no. SC905483 ICO registration ZC275012 3F1 Third Floor, 3 Hill Street, Edinburgh EH2 3JP [email protected]