Legal

Data processing addendum

Version 1.0 · Effective 8 November 2026

The short version

When a business puts its people in a Corewire space, the business decides what happens to their data and we process it for them. This addendum is the contract the GDPR requires for that. It applies automatically to business customers as part of the terms of service — nothing to sign.

We never receive your prompts, files or sessions, so the data in scope is small: the members of your spaces, their devices, and the records that run the network.

1 · Scope

This data processing addendum (“DPA”) is between Gooey Technologies Limited (“Corewire”) and the customer that accepted the terms for a business or organisation (“Customer”). It applies when Corewire processes Customer Personal Data in providing the service, and forms part of the terms. If you need a countersigned copy, write to legal@corewire.ai.

Words defined in the GDPR — controller, processor, personal data, processing, data subject, personal data breach, supervisory authority — have the same meaning here. “Data Protection Law” means the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, New Zealand’s Privacy Act 2020 and the California Consumer Privacy Act, each where it applies. “Customer Personal Data” means personal data in a space the Customer controls that Corewire processes on its behalf, as Annex I describes.

2 · Roles

The Customer is the controller, or a processor acting for its own controller, of Customer Personal Data, and Corewire is its processor or subprocessor. Corewire is a controller of the data it needs to run its own business — accounts, billing, security logs, usage statistics — as the privacy policy describes; this DPA does not cover that data.

The Customer is responsible for having a lawful basis for the processing and for giving its members the information Data Protection Law requires.

3 · Instructions

Corewire processes Customer Personal Data only on the Customer’s documented instructions: these terms, this DPA, and what the Customer configures in the service. Further instructions must be in writing and consistent with the terms. Corewire tells the Customer if it believes an instruction infringes Data Protection Law, or if the law requires processing the instructions do not cover, unless that law forbids telling.

4 · Confidentiality

Everyone at Corewire authorised to process Customer Personal Data is bound by confidentiality, and has access only as far as their work requires.

5 · Security

Corewire maintains the technical and organisational measures in Annex II, and may improve them over time provided the overall level of protection does not go down.

6 · Subprocessors

The Customer gives Corewire general authorisation to use the subprocessors listed in Annex III. Corewire imposes on each, by written contract, data protection obligations no less protective than this DPA, and remains responsible to the Customer for their performance.

Corewire gives at least 30 days’ notice of a new subprocessor by updating the subprocessors page and emailing customers who asked for notices. The Customer may object on reasonable data protection grounds within that period. The parties will then discuss it in good faith; if no solution is found, the Customer may end the affected service and receive a pro rata refund of prepaid fees for it.

7 · Helping the Customer

  • Data subject requests. The panel lets the Customer see, export, correct and remove its members and devices. Where that is not enough, Corewire helps with reasonable measures, and passes on any request it receives directly instead of answering it.
  • Impact assessments. Corewire provides the information it reasonably can for the Customer’s data protection impact assessments and consultations with supervisory authorities.
  • Breaches. Corewire notifies the Customer of a personal data breach affecting Customer Personal Data without undue delay, and within 48 hours of becoming aware of it, with what is known — its nature, the data and people affected, likely consequences, and the measures taken — and adds detail as it learns more. Notifying is not an admission of fault.

8 · Deletion and return

The Customer can export its data from the panel at any time. A space or account the Customer deletes in the panel is erased at once. When the service ends otherwise, Corewire deletes Customer Personal Data within 30 days; and it leaves backups within a further 30 days, unless the law requires keeping it — in which case it stays protected by this DPA and is used for nothing else.

9 · Audits

Corewire makes available the information necessary to show compliance with this DPA and Article 28 of the GDPR, including answering a reasonable security questionnaire once a year. If that is not enough — or a supervisory authority requires it, or after a personal data breach — the Customer may audit Corewire, by itself or through an independent auditor bound by confidentiality, on 30 days’ written notice, during business hours, without disrupting the service and at the Customer’s cost.

10 · International transfers

Corewire is established in New Zealand, which has an adequacy decision from the European Commission (2013/65/EU) and is recognised by the United Kingdom, so Customer Personal Data may be transferred to Corewire without further safeguards. To the extent a transfer of Customer Personal Data from the Customer to Corewire is nonetheless a restricted transfer, or adequacy ceases to cover it:

  • EU. The standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 are incorporated by reference — Module 2 where the Customer is a controller, Module 3 where it is a processor — with the Customer as data exporter and Corewire as data importer. Clause 7 (docking) applies; under Clause 9(a), Option 2 applies with the 30-day notice in section 6; the optional wording in Clause 11 does not apply; under Clause 13, the supervisory authority is the one competent for the Customer; Clauses 17 and 18 choose the law and courts of Ireland. Annexes I to III of this DPA complete the clauses’ annexes.
  • UK. The International Data Transfer Addendum issued by the Information Commissioner (version B1.0) is incorporated and amends the clauses above; its tables are completed by this DPA, and either party may end it as its Section 19 allows.
  • Switzerland. The clauses above apply with references to the GDPR read as the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner as the competent authority where it is.

For onward transfers to subprocessors in countries without adequacy, Corewire relies on the standard contractual clauses (Module 3) or the EU-U.S. Data Privacy Framework, as Annex III shows. If a public authority asks Corewire for Customer Personal Data, Corewire tells the Customer unless forbidden, and challenges the request where there are grounds to.

11 · California

For Customer Personal Data subject to the CCPA, Corewire is a service provider: it does not sell or share it, retain, use or disclose it outside the direct business relationship with the Customer or for any purpose other than providing the service, or combine it with personal information from other sources except as the CCPA permits.

12 · Liability, precedence and term

Each party’s liability under this DPA is subject to the limits in the terms, except where the standard contractual clauses or Data Protection Law do not allow it. If this DPA and the terms conflict, this DPA wins; if the standard contractual clauses and anything else conflict, the clauses win. This DPA lasts as long as Corewire processes Customer Personal Data.

Annex I · Description of the processing

Data exporter: the Customer, as identified by its account and space; contact: the space’s owner. Role: controller (Module 2) or processor (Module 3).

Data importer: Gooey Technologies Limited, 579d New North Road, Kingsland, Auckland 1021, New Zealand; contact: privacy@corewire.ai. Role: processor or subprocessor.

Data subjects: the Customer’s members and invitees in its spaces — typically employees and contractors.

Categories of data: email addresses and names; roles and invitations; device names, operating systems, network keys, private network addresses, IP addresses and endpoints; relay byte counts and monthly usage counts per device; subscription status of the space; problem reports sent from the space’s devices.

Sensitive data: none intended. Prompts, files, sessions and generated content stay on the Customer’s devices and are not processed by Corewire; traffic relayed between devices is end-to-end encrypted and cannot be read by Corewire.

Frequency: continuous, for as long as the Customer uses the service.

Nature and purpose: hosting accounts and spaces; coordinating the Customer’s devices into a private network; relaying encrypted traffic where devices cannot connect directly; metering the plan; showing the panel; support and fixing problems.

Retention: for the life of the space or account, then deleted as section 8 says; problem reports are kept 24 months after the problem was last seen.

Subprocessors: as Annex III lists, for the purposes stated there.

Annex II · Technical and organisational measures

  • Encryption. Device-to-device traffic, direct or relayed, is end-to-end encrypted with WireGuard; connections to Corewire’s services use TLS 1.2 or later; databases and object storage are encrypted at rest by their providers.
  • Minimisation by design. Content never leaves the Customer’s devices; problem reports are scrubbed of paths, addresses, hostnames, emails and credential-shaped strings before they leave a device and again before anything is filed.
  • Access control. Production access is limited to named operators, with multi-factor authentication on administrative consoles; administrative interfaces are not exposed to the public internet; operator actions on customer accounts are recorded in an audit log.
  • Tenant separation. Every request to the panel is checked against the requester’s space membership and role; devices in different spaces cannot reach each other.
  • Software security. Code review for every change; automated dependency, secret and static analysis scanning; signed release artifacts and update manifests.
  • Availability and resilience. Managed databases with automated backups; monitoring and alerting on every server; relays in three regions.
  • Incidents. A documented incident response process and a published vulnerability disclosure policy.
  • Subprocessors. Chosen for their security practices and bound by data processing agreements.

Annex III · Subprocessors

SubprocessorPurposeLocationTransfer safeguard
DigitalOceanServers and managed databases for sign-in, the coordinator that connects your devices, the relays, and the panel's dataAustralia (Sydney) for databases, sign-in and coordination; relays in Australia, the Netherlands and the United StatesStandard contractual clauses in DigitalOcean's data processing agreement
VercelHosting this website and the panel, their APIs and scheduled jobs; cookieless website analyticsUnited States, with a global edge networkEU-U.S. Data Privacy Framework and standard contractual clauses
CloudflareStoring and serving downloads (installers, engines, update feeds) and encrypted backupsGlobal edge network; storage location chosen by CloudflareEU-U.S. Data Privacy Framework and standard contractual clauses
ResendSending sign-in codes, invitations and service email; receiving mail to our addressesUnited States and JapanStandard contractual clauses in Resend's data processing agreement
ExpoDelivering session notifications from your computers to your phone, through Apple and GoogleUnited StatesStandard contractual clauses
Apple Push Notification service and Firebase Cloud MessagingThe last step of a notification: delivering it to an iPhone or an Android phoneUnited States and worldwideEU-U.S. Data Privacy Framework and standard contractual clauses
GitHubTracking problems and feature requests in a private repositoryUnited StatesEU-U.S. Data Privacy Framework and standard contractual clauses
AnthropicSorting and handling problem reports and feature requestsUnited StatesStandard contractual clauses in Anthropic's data processing addendum; not used to train models

The current list is always at subprocessors.

Countersigned copies, notices and questions: legal@corewire.ai