Data Processing Agreement
Version 2026-11
This Data Processing Agreement ("DPA") is between Family Labs Pty Ltd (ACN 688 034 988), 470 St Kilda Road, Melbourne VIC 3004, Australia ("Family Labs", "we", "us"), and the organisation for which it is accepted ("you").
It is accepted when an owner or admin of your organisation selects "Accept" in the Universal Goods console. The person accepting confirms they have authority to bind the organisation. We record who accepted, when, and which version.
It forms part of our Terms and Conditions (the "Terms"). If the Terms and this DPA differ on data protection, this DPA prevails. If your organisation has signed a data processing agreement with us, that agreement applies instead of this one.
1. Definitions
Words defined in the GDPR, such as "controller", "processor", "personal data", "processing", "data subject", "personal data breach" and "supervisory authority", have their GDPR meanings.
- Data protection law means the EU General Data Protection Regulation (GDPR), the UK GDPR, the Swiss Federal Act on Data Protection, the Australian Privacy Act 1988 (Cth), and any other data protection law that applies to the processing.
- Customer personal data means personal data in the categories in Annex 1 that we process for you in providing the Services.
- Services and public network have the meanings in the Terms.
- Standard contractual clauses means the clauses in Commission Implementing Decision (EU) 2021/914.
2. Who is responsible for what
2.1 We are your processor for customer personal data: passport content, uploaded documents and the text read from them, supplier requests and answers, passport access requests and decisions, and Scout conversations about your products. You are the controller, or act for the controller.
2.2 We are a separate controller for our own data: user accounts and sign-in records, organisation membership, billing, security and audit logs, our administration of customer accounts, and measuring use of the Services (for example Scout use against your plan). Our Privacy Policy covers that data. This DPA does not.
2.3 You are responsible for the lawfulness of the processing you instruct. That includes having a lawful basis, giving people the information they are entitled to (for example your supplier contacts and people who ask for passport access), and getting any consent the law requires before customers' personal data is stored in a passport.
2.4 Consumer ownership records. If you transfer items to consumers through the Services, the record that a consumer's account address holds your item is written to the public network and shown to you. We process that record for you under this DPA. We do not show you the consumer's name or email address unless the consumer holds the item through a business account.
3. Our obligations as processor
3.1 Instructions. We process customer personal data only on your documented instructions, including on transfers to other countries, unless the law requires otherwise; if so, we will tell you first unless the law forbids it. Your instructions are the Terms, this DPA, and how you and your users use and configure the Services. We will tell you if we think an instruction breaks data protection law.
3.2 Confidentiality. People we authorise to process customer personal data are bound to keep it confidential and get only the access they need.
3.3 Security. We take the technical and organisational measures in Annex 2. We may change them, but not in a way that materially lowers the overall protection.
3.4 No other use. We do not sell customer personal data, and we do not use it for our own purposes except as section 2.2 describes.
3.5 Public network. We do not write names, email addresses, phone numbers or other details that directly identify a person to the public network. Account addresses, item identifiers, ownership and transfer records, and cryptographic fingerprints of passport content are written there by design and cannot be deleted by anyone.
3.6 AI provider. We send customer personal data to an AI model provider only when you or your suppliers use Scout, only as needed for that use, and only to the provider listed in Annex 3 (Anthropic). Scout tells your users it is an AI before anything is sent, and you can switch Scout off for your organisation at any time (Settings, General). Anthropic's Commercial Terms of Service say Anthropic may not train models on customer content from its services. Anthropic's published retention policy says it deletes API inputs and outputs within 30 days, with exceptions it lists (including data kept longer under the customer's own control, usage-policy enforcement and legal requirements). When a Scout task ends, we delete its working session at Anthropic.
4. Sub-processors
4.1 You authorise us to use the sub-processors listed in Annex 3.
4.2 We will tell your organisation's owners by email at least 30 days before we add or replace a sub-processor, and update Annex 3. If you object on reasonable data protection grounds, we will discuss it with you in good faith. If we cannot resolve it, you may stop using the affected Services or close your organisation's account before the change takes effect, and we will refund prepaid fees for the unused period.
4.3 In an emergency affecting the security or availability of the Services, we may replace a sub-processor with shorter notice and will tell you as soon as we can. Section 4.2 then applies.
4.4 We bind each sub-processor by written contract to data protection obligations that give at least the same protection as this DPA, and we remain responsible to you for its performance.
5. Helping you
5.1 Requests from people. We will help you, as far as we reasonably can given the nature of the processing, to answer requests from people exercising their rights. Much of this you can do yourself in the Services: edit or delete records, decide access requests, and export everything (Settings, Export everything). For the rest, contact us and we will help by hand.
5.2 If we receive a request directly from a person about customer personal data, we will pass it to you within 5 working days and will not answer it ourselves except to acknowledge it and refer the person to you, unless you ask us to.
5.3 If a request concerns a record on the public network, we will help by deleting or restricting the data we hold that links that record to the person.
5.4 Other help. We will help you, taking into account the nature of the processing and the information we have, with your obligations on security, personal data breaches, data protection impact assessments and consultation with supervisory authorities.
6. Personal data breaches
6.1 We will tell you without undue delay after we become aware of a personal data breach affecting customer personal data.
6.2 We will tell you, as far as we then know: what happened, the kinds and approximate numbers of people and records affected, the likely consequences, what we have done or plan to do about it, and who to contact. If we do not know everything at once, we will tell you more as we learn it.
6.3 We will not notify a supervisory authority or the people affected on your behalf without your instruction, unless the law requires us to.
6.4 We will keep a record of personal data breaches affecting customer personal data and show it to you on request.
7. At the end
7.1 You can export your data at any time while your account is open (Settings, Export everything). That is how you take a copy before leaving; we also give it to you on request.
7.2 When your organisation closes its account, we will delete customer personal data within 90 days, unless the law requires us to keep it, except:
- (a) records on the public network, which cannot be deleted by anyone;
- (b) passport content that you have asked us to keep available after you leave, or that must stay available under product law (for example a battery passport after the operator stops trading); such content should contain personal data only where the law requires it;
- (c) backups, which expire within 35 days and are restored only to recover from an incident; after a restore we re-apply, by hand, any deletion done after the backup was taken; and
- (d) uploaded files you deleted, which remain recoverable by us for 14 days after deletion.
7.3 On request, we will confirm the deletion in writing.
8. Information and audits
8.1 We will give you the information reasonably needed to show that we meet this DPA and GDPR Art. 28, including answers to a reasonable security questionnaire. We do not hold any third-party security certification or audit report today.
8.2 If that information is not enough, or a supervisory authority requires it, you (or an independent auditor bound by confidentiality who is not our competitor) may audit our compliance with this DPA. You must give at least 30 days' written notice, audit no more than once in any 12 months (except after a personal data breach or at a supervisory authority's request), during business hours and without unreasonable disruption. You pay your own costs, and ours unless the audit finds a material breach by us.
9. Transfers outside the EU
9.1 Customer personal data is stored in the European Union (Microsoft Azure, Sweden). Family Labs staff access it from Australia to run and support the Services, and Anthropic processes Scout data in the United States (Annex 3).
9.2 Where a transfer needs a safeguard under data protection law, the mechanism in Annex 4 applies. Annex 4 forms part of this DPA.
9.3 We will not otherwise transfer customer personal data outside the European Union without your prior written consent.
10. Liability
Each party's liability under this DPA is subject to the limits in the Terms, except that nothing limits either party's liability to people under GDPR Art. 82 or limits the standard contractual clauses in Annex 4 in a way that contradicts them.
11. EU representative
We will name our EU representative here once appointed.
12. Changes, term and law
12.1 This DPA applies while we process customer personal data for you, and then until we have deleted or returned it under section 7.
12.2 When we publish a new version, an owner or admin of your organisation must accept it before document uploads and supplier requests continue. Until then, the version you accepted applies to processing already done.
12.3 This DPA is governed by the law of Victoria, Australia, except that the standard contractual clauses in Annex 4 are governed by the law named in them.
Annex 1: Description of the processing
| Controller | The organisation that accepted this DPA |
| Processor | Family Labs Pty Ltd, ACN 688 034 988, 470 St Kilda Road, Melbourne VIC 3004, Australia. Privacy contact: privacy@universalgoods.org. EU representative: section 11 |
| People whose data is processed | (a) your users, as they appear in your records (for example as the person who changed a passport); (b) your suppliers' contact people; (c) people who ask for access to restricted passport data (for example repairers, recyclers and staff of authorities); (d) people named in passport content where product law requires it (for example a signatory or a facility contact); (e) consumers, if you transfer items to them |
| Kinds of personal data | Names, business email addresses and phone numbers, job titles and organisation names; supplier answers and uploaded documents, which may contain personal data; Scout conversations about your products; access request details (name, email, organisation, role, stated reason) and decisions; records of who changed or read restricted passport data; account addresses linked to the above |
| Special categories | None intended. You must not upload special categories of personal data unless the law requires it |
| How often | Continuously, while you use the Services |
| What we do with it | Host, store, organise, retrieve, display and send it (including by email); read text from scanned documents; AI-assisted extraction and checking (Scout); control and log access; keep passport version history; back it up; delete it |
| Why | To provide the Services under the Terms: create and maintain passports, collect supplier data, handle access requests, and support you |
| How long | While you use the Services, unless you delete it sooner, and then as section 7 says |
| Sub-processors | Annex 3 |
| Transfers | Annex 4 |
Annex 2: Security measures
As at 28 October 2026. These are the measures in place. We do not claim certification against any standard.
Access control
- Role-based access control inside the Services; each organisation's data is separated by permission checks on every request, and a regression suite checks that separation on every route.
- People sign in with passkeys or email and password; passwords are stored only in scrambled (hashed) form.
- Signing keys for accounts are created on users' own devices and kept there in encrypted form; we do not receive their private part.
- Separate sign-in systems for consumer accounts and business accounts.
- Reads of restricted passport data need a verified requester and are recorded in a tamper-evident log.
- Access-link tokens and one-time codes are stored only as cryptographic hashes.
- Our administrators' changes to, and views of, customer accounts are recorded in an append-only activity log. Library features that would let an administrator act as a user without a record are switched off.
- An owner or admin can withdraw Scout's authority to act for the organisation at any time; every change is recorded in the audit log.
Encryption and network
- Data is encrypted in transit (HTTPS) on the Services' public addresses.
- Data is encrypted at rest by our hosting provider, Microsoft Azure.
- Databases are not reachable from the public internet, and so is the authorisation service.
Change and development
- Code changes go through pull requests with required automated checks before release.
- Infrastructure is defined as code; deployments use short-lived credentials.
Availability and recovery
- Database point-in-time backups are kept for 35 days, with a copy in a second Azure region in Sweden.
- Uploaded files are protected against accidental permanent deletion for 14 days, and overwritten files keep their previous version.
- Availability and failure alerts are sent to us by email. A restore drill is documented.
- You can export all your organisation's data at any time.
Logging and minimisation
- Server logs are kept for 90 days; values in web addresses and email addresses are masked in them.
- Our administrators' dashboard shows counts and one owner contact per organisation, not passport contents, IP addresses or other members' details.
- Fonts and assets are served from our own servers, so viewing a page does not send visitor details to a font provider.
Incident handling
- A published security contact (security@universalgoods.org, and /.well-known/security.txt on every host) and a written incident response plan.
Annex 3: Sub-processors
As at 28 October 2026.
| Sub-processor | What it does | Customer personal data it may receive | Where |
|---|---|---|---|
| Microsoft Corporation and its affiliates (Microsoft Azure) | Hosting: application servers, database, file storage, key storage, logs and monitoring | All customer personal data stored in the Services | Azure Sweden Central (EU); database backups also in the paired region, Azure Sweden South (EU) |
| Microsoft Corporation (Azure AI Document Intelligence) | Reads text from scanned documents you or your suppliers upload | Content of uploaded documents | Same region as above |
| Microsoft Corporation (Azure Communication Services) | Sends service emails (for example access codes, supplier requests and access decisions) | Recipient name and email address, message content and links | European Union |
| Anthropic PBC | Runs the AI models behind Scout, and hosted Scout agent sessions | What your users and suppliers send to Scout; documents and data Scout is asked to read | United States |
Family Labs staff access the Services from Australia to run and support them.
Not sub-processors: the public network (no contract with its operators is possible); Google, for users who choose to sign in with Google (an independent controller); Stripe, which processes our billing data as our provider, not customer personal data; Cloudflare, which provides domain name service and certificate automation only.
Annex 4: Transfers
4.1 From you to us (EU or EEA controller to Australian processor). The standard contractual clauses, Module Two (controller to processor), are incorporated into this DPA by reference, with you as data exporter and Family Labs as data importer, and with these elections:
- Clause 7 (docking clause): included.
- Clause 9 (sub-processors): option 2, general written authorisation, with 30 days' notice as in section 4.2 of this DPA.
- Clause 11 (redress): the optional wording is not included.
- Clause 13 (supervision): the supervisory authority of the Member State where you are established, or where your representative is established, or where the data subjects are, as the clause provides.
- Clause 17 (governing law): the law of Ireland.
- Clause 18 (forum): the courts of Ireland.
- Annexes I, II and III of the clauses are Annexes 1, 2 and 3 of this DPA.
By accepting this DPA you also sign the clauses as data exporter, and we sign them as data importer.
4.2 From us to sub-processors outside the EU. For Anthropic (United States): the transfer safeguards in Anthropic's data processing terms, which we have accepted. For Microsoft: Microsoft's Product Terms and Data Protection Addendum, which incorporate the standard contractual clauses.
4.3 United Kingdom. If you export from the UK, the UK International Data Transfer Addendum to the clauses applies, with the same elections.
4.4 Switzerland. If you export from Switzerland, the clauses apply with the amendments the Swiss Federal Data Protection and Information Commissioner requires.
Family Labs Pty Ltd. Data Processing Agreement for self-serve organisations, version 2026-11.