Hangar Data Processing Terms

Version 1.0. Effective date: 27 October 2026.

These terms are part of the Hangar Terms of Service. They set how TALOS Defence handles your Customer Content. Words defined in the Terms of Service have the same meaning here.

1. Roles#

1.1 You decide. You decide what Customer Content you upload or produce, why, and for how long it is kept. You are responsible for having a lawful basis, and any notice or consent needed, for the personal information in it.

1.2 We act for you. TALOS Defence processes Customer Content only to provide Hangar to you, on your instructions. In these terms, TALOS Defence acts as your service provider (a processor).

1.3 Your instructions. Your instructions are this agreement, your Account configuration (including your egress allowlist and retention choices), and the Workloads, uploads and downloads you start. We follow them unless they breach the law. If we believe an instruction breaches the law, we tell you, unless the law prevents it.

1.4 Service Data. These terms do not cover Service Data. We handle the personal information in Service Data under the Privacy Policy.

2. Our commitments#

2.1 We process Customer Content only on your instructions and as the law requires.

2.2 We do not sell Customer Content, use it for advertising, or use it to train, tune or evaluate any model.

2.3 TALOS Defence staff have no access to Customer Content (Terms of Service clause 6.7). Every person who operates Hangar is bound by a duty of confidentiality.

2.4 We handle any personal information in Customer Content in a way that is consistent with the Australian Privacy Principles, to the extent they apply to our role.

3. Where Customer Content is held#

3.1 We store and process Customer Content in Australia, in Amazon Web Services' Asia Pacific (Sydney) region and, for runs on a Trainium2 pool, its Asia Pacific (Melbourne) region.

3.2 We do not move Customer Content outside Australia. Your own actions can move it: a Workload that sends data to a destination on your egress allowlist, a download, or a share you make.

4. Sub-processors#

4.1 The list. We use these sub-processors:

These providers handle account and billing information only. They never receive Customer Content:

4.2 Changes. We give you at least 30 days' notice by email before we add or replace a sub-processor that will receive Customer Content. If you object on reasonable grounds about the protection of data, you may close your Account before the change takes effect, and we refund your unused Paid Credit and credit for confirmed bookings after that date.

4.3 Our responsibility. We impose data protection obligations on each sub-processor that are appropriate to its role. We remain responsible to you for each sub-processor's processing of Customer Content, within the limits in clause 15 of the Terms of Service.

5. Security measures#

5.1 We maintain the technical and organisational measures in Annex A. We may change them, provided that the change does not materially reduce the overall protection of Customer Content.

5.2 You are responsible for the security of your Account, credentials, keys, images and code, for your egress allowlist, and for any encryption of Customer Content that you apply before you upload it.

6. Security incidents#

6.1 Notice. We notify you without undue delay, and within 72 hours, after we confirm a Security Incident. A Security Incident is a breach of security that leads to the accidental or unlawful destruction, loss, alteration, or unauthorised disclosure of or access to, your Customer Content.

6.2 Content of the notice. The notice describes, as far as we then know: what happened; the Customer Content affected; what we have done and will do; and a contact. We give more information as we learn it.

6.3 Assistance. We give you reasonable help to assess the incident and to meet your own obligations, including under the Notifiable Data Breaches scheme in the Privacy Act 1988 (Cth). We coordinate with you before either of us notifies individuals about Customer Content, unless the law requires otherwise.

6.4 Not an admission. Our notice of a Security Incident is not an admission of fault or liability.

7. Requests from authorities and individuals#

7.1 Authorities. We disclose Customer Content to a government authority, law enforcement agency or court only when the law requires us to. Before we disclose, we tell you, unless the law prohibits it. We disclose only what the law requires.

7.2 Individuals. If a person asks us for access to, or correction of, their personal information in your Customer Content, we refer them to you. We give you reasonable help to respond.

8. Retention, return and deletion#

8.1 During the agreement. We keep and delete Customer Content according to the retention choices you make. The defaults are published in the documentation. You can download your Customer Content at any time.

8.2 Locked retention. If you choose a locked retention period (for example, 7 years), no one can shorten it, including us. We delete the content when the lock ends.

8.3 When the agreement ends. You may export your Customer Content for 30 days after the agreement ends. After that, we delete all Customer Content within a further 30 days, except:

1. content under a locked retention period you chose, which we keep until the lock ends and then delete;
2. content under a legal hold, which we keep until the hold ends;
3. content that the law requires us to keep.

8.4 Deletion records. Each deletion is a signed record. Certificates, data movement records and deletion records hold digests and metadata, not Customer Content. We keep them for at least 7 years.

8.5 If Hangar stops. If TALOS Defence stops operating Hangar, we give every customer with retained Customer Content a reasonable opportunity to export it before we delete it.

9. Information and audit#

9.1 We give you the information reasonably needed to show that we meet these terms. This includes your Certificates, the published documentation of how a run is isolated, and our written answers to a reasonable security questionnaire, once a year.

9.2 We do not allow on-site audits, except where the law requires one. If the law requires one, you give at least 30 days' notice, the audit happens in business hours, it does not access other customers' data, and you pay its reasonable cost.

10. Liability#

These terms are subject to clauses 14 and 15 of the Terms of Service.

Annex A. Security measures#

Isolation of runs

• Each booked slot runs on an instance launched for it from Hangar's signed image. The instance is terminated at the end, not reused for another customer. On an H100 pool, where a relaunch is not available in time, the working disk is discarded and the instance is rebooted, and the Certificate records it. On a Trainium2 pool, every slot runs on a fresh instance.
• Before a customer's code runs, the instance's boot is measured and checked, and the accelerator is checked and its free memory is cleared and read back. The result is a signed record on the Certificate.
• Customer data during a run is held on the instance's local disk, under encryption with a key held only in memory.
• Each slot has its own network security group with no inbound access. A Workload reaches only the destinations on your egress allowlist. Other connections are refused and recorded.
• Instances have no standing cloud credentials. Each slot receives short-lived credentials scoped to its own storage and image.

Storage and transmission

• Customer Content at rest in Hangar's storage is encrypted.
• Connections to Hangar's website and API use TLS.
• Locked retention uses storage object locks in compliance mode.

Access

• Customers sign in with passkeys.
• Access to production systems is limited to authorised TALOS Defence personnel.
• Sensitive operator actions, such as a legal hold, need the approval of two operators, and each is a signed record.
• Hangar's cloud accounts are restricted by policy to Australian regions for customer data.

Records

• Every booking, movement of data, reset, wipe, run and deletion is a signed record, chained to the record before it and entered in an append-only log whose head is published.

Payment data

• Card details are handled by Stripe. Hangar does not receive or store full card numbers.

© TALOS Group Pty Ltd, used under licence by TALOS Defence Pty Ltd.