Legal

Privacy policy

Version 2.1 · Effective 10 November 2026

The short version

Corewire connects machines you own. Your prompts, files, sessions, models and everything they produce stay on those machines, and travel between them encrypted end to end. We never receive them.

What we hold is what an account and a private network need — your email, your spaces and devices, byte counts — plus usage statistics and problem reports that never carry content, each with a switch in Settings to turn it off. We sell nothing, run no advertising, use no analytics company, and set no tracking cookies. This page lists all of it.

1 · Who we are

Corewire is run by Gooey Technologies Limited, a New Zealand limited company (company number 9395690, NZBN 9429053355720), registered office 579d New North Road, Kingsland, Auckland 1021, New Zealand. We are the controller of the personal data described here — the “agency” under New Zealand’s Privacy Act 2020. For anything in this policy, write to privacy@corewire.ai; a person reads every message.

When a business uses a Team or Enterprise space for its people, that business is the controller of its members’ data in the space and we process it on its behalf, under our data processing addendum.

2 · What never reaches us

Prompts and chats. The files your agents work on, and their sessions. Generated text, images, audio and video. Models and their weights. Your devices’ own record of what ran where, which you can export and purge from the app. Traffic between your devices — direct or through our relays — is encrypted end to end with WireGuard: we can count its bytes, and we cannot read it.

The one way a fragment of a session can leave your machines through a company we use is a notification you turn on: see section 6.

3 · What we hold, why, and for how long

WhatWhyLegal basisKept
Account: email address, sign-in methods (passkey public keys, authenticator enrolment, backup codes), and a name if you give oneSigning you in; sign-in codes, invitations and service emailContract (GDPR Art. 6(1)(b))Until you delete the account
Spaces: names, members and their roles, invitationsSharing devices with the people you chooseContract (GDPR Art. 6(1)(b))Until the space is deleted; your membership until you leave
Devices: names, operating system, network keys, private network address, IP addresses and endpoints, last seenConnecting your devices to each other, and showing them in the panelContract (GDPR Art. 6(1)(b))Until the device is removed or the space deleted
Relay byte counts and monthly usage counts: per device, per month, counts of requests, tokens and bytes per kind of work — never contentMetering the relay allowance; the totals page in the panelContract (GDPR Art. 6(1)(b))While the space exists
Billing: plan, dates and state of a subscription, the payment events Lemon Squeezy reports, its order and subscription references — never card numbersGiving a space the plan it paid for; accountingContract (GDPR Art. 6(1)(b)); Legal obligation (Art. 6(1)(c))At least 7 years, as New Zealand tax law requires
Agreement records: which version of the terms and privacy policy you accepted, when, and where (at sign-up or in the panel)Proving what was agreedLegal obligation (Art. 6(1)(c)); Legitimate interests (Art. 6(1)(f))While the account exists, and afterwards as long as the law requires
Usage statistics: see section 4Knowing which parts of Corewire are used and where people get stuckLegitimate interests (Art. 6(1)(f))Raw events 13 months; daily totals derived from them are kept as counts
Problem reports and feature requests: see section 5Finding and fixing what breaks; deciding what to buildLegitimate interests (Art. 6(1)(f))24 months after the problem was last seen
Email you send us, and enquiries from the pricing pageAnswering youLegitimate interests (Art. 6(1)(f))24 months after the conversation ends
Service and security logs: IP addresses and request details at our servers and hostsKeeping the service running and secure; investigating abuseLegitimate interests (Art. 6(1)(f))Up to 30 days, longer only for an open investigation
Operator actions on your account or space (an audit log)Accountability for what our staff doLegitimate interests (Art. 6(1)(f))24 months
Infrastructure health readings: uptime, latency and traffic of our own servers — nothing about youKnowing the service is upLegitimate interests (Art. 6(1)(f))90 days

A job runs every day to delete what has outlived the periods above.

Deleting your account (panel › Settings) erases it at once: the account, the spaces you alone own and their devices, your usage statistics — including those your devices sent before you signed in — your votes on feature requests, and the usage and relay records of the deleted spaces. Problem reports and feature requests you sent stay only as text belonging to no one: their link to you and your spaces is removed, and a problem’s count is shared with everyone who hit it. Deleting a space does the same for everything kept about that space. Database backups age out within 30 days.

Three kinds of record are kept after deletion, because the law or accountability requires them, and are used for nothing else: billing records (subscriptions and payment events, for tax), agreement records (which terms you accepted, as proof), and the audit log of what our operators did. Shared spaces you leave keep standing for their other members; what is deleted is you.

Where we rely on legitimate interests, we have weighed them against yours: each use is limited to running and improving the service you chose, uses data that is not your content, and — for statistics and automatic problem reports — comes with a switch to turn it off.

4 · Usage statistics

Corewire’s apps — the desktop app, the phone app and the background service on each device — and the signed-in web panel send us usage statistics, so we can see which features are used and where people get stuck. They are stored only in our own database; no analytics company receives them.

Each event is a name from a fixed list — for example “a session started”, “the app was opened”, “a model served a request today” — with a few properties that are also chosen from fixed lists: which kind of model (chat, image…), which coding agent (Claude Code, Codex…, or “other”), which screen, and whether it ran on this device or another of yours. Events also carry a random identifier made when Corewire is installed, the Corewire version (major.minor.patch) and the operating system family (macOS, Windows, Linux, iOS, Android). When the device is signed in, its events are linked to your account and space, including events from before you signed in on that install.

They never contain what you type, prompts or model output, file names or paths, device names, hostnames, email addresses or IP addresses. The service that receives them does not store your IP address either.

Turning it off. Settings › “Share usage statistics”, on each device and in the web panel, turns this off at any time; turning it off also deletes anything not yet sent. Our servers record a few facts about the service itself regardless of the switch, because we already hold them to provide it: that an account was created, that a device was added, that a subscription started, changed or ended, that a space reached its relay allowance, and that a problem report was received.

5 · Problem reports and feature requests

When Corewire notices an error — a crash, a failed request, a session that did not start, a screen that broke — it sends a report to our developers: the error, where in our code it happened, how often, the Corewire version, the operating system and the versions of the runtimes involved. Secrets, paths, addresses and names are removed before a report leaves your device; it never contains a prompt, a file or a session.

Turning it off. Settings › “Send problem reports automatically”, on each device and in the web panel. Off, reports stay on your device, listed in Settings › Problems, and are sent only if you report a problem yourself. Problems and feature requests you or an agent report on purpose carry the words you or it wrote; Settings › Problems shows the exact text before it goes.

Reports and requests are stored in our own database and processed by the service providers listed on our subprocessors page, after a scan in our code removes anything shaped like a key, a token or a password. Anthropic does not use this data to train models.

6 · Notifications on your phone

If you turn on notifications in the phone app, it gives your computers a push token — an address for your phone at Apple or Google. Your computers keep it; our servers never do. When a session needs you, finishes or stops, the computer running it sends a short notice through Expo’s push service, which hands it to Apple or Google to deliver.

By default a notice says what the agent asks or the first line of its answer — that text passes through Expo and Apple or Google on its way. Settings › Notifications › “Say what the agent asks” off makes notices name only the agent and the computer. Turning notifications off makes your computers forget the token.

7 · This website and the panel

corewire.ai and the panel use Vercel Web Analytics and Vercel Speed Insights, which are cookieless and aggregate: page views, referrers, country, device type and page-load timings, without identifying you. We also count page visits and download and pricing clicks in our own database, using an identifier made when the page loads and kept nowhere, so we count visits, not visitors. For a visit’s first page we note what kind of site sent you (an AI assistant, and which one; a search engine; or another site), never the address of the page you came from. No cookies are set for analytics, and there is no advertising, cross-site tracking or profile of you.

Global Privacy Control. If your browser sends Global Privacy Control or Do Not Track, our own counting records nothing.

The panel sets a few cookies that keep you signed in and remember which space you were looking at; they are strictly necessary, which is why there is no cookie banner. The cookie policy lists each one.

8 · Services your devices contact directly

Some things your devices do reach other companies without passing through us, and those companies see your IP address under their own policies: public STUN servers (run by Cloudflare, Google and Tailscale) that help two of your devices find a direct path; Hugging Face and GitHub, where models and engines you choose to install are downloaded from; and whatever service an agent or runtime you run talks to — for example Anthropic for Claude Code or OpenAI for Codex, under your own account with them.

9 · Who else sees it

Processors. These companies process personal data for us, only on our instructions and under data processing agreements: DigitalOcean, Vercel, Cloudflare, Resend, Expo, Apple Push Notification service and Firebase Cloud Messaging, GitHub, Anthropic. The subprocessors page says what each does, with which data, where, and under which safeguard.

Lemon Squeezy. Lemon Squeezy, LLC sells Pro and Team as merchant of record. It collects your payment details and billing address under its own privacy policy, as a controller in its own right; we receive the subscription’s plan, dates and state.

People in your spaces. Owners and administrators of a space see its members’ email addresses and roles, and its devices and their usage.

When the law requires it. We disclose data to authorities only when a valid legal process compels us, and we tell you unless we are forbidden to. We hold no content to disclose. If Corewire is sold or merged, your data moves with it under this policy, and we tell you first.

We do not sell personal data, and we do not share it for advertising.

10 · Where it lives, and transfers

We are in New Zealand, which the European Commission and the United Kingdom recognise as giving adequate protection to personal data. Our databases and the services that sign you in and connect your devices run in Australia (DigitalOcean, Sydney); relays run in Australia, the Netherlands and the United States, so that relayed traffic takes a short path. Several processors are in the United States.

Where personal data from the European Economic Area, the United Kingdom or Switzerland goes to a country without such recognition, it is protected by the European Commission’s standard contractual clauses (with the UK addendum and Swiss amendments) or by the EU-U.S. Data Privacy Framework, as each processor’s row on the subprocessors page says. For New Zealand’s Privacy Act, each processor is bound by contract to protect the data in a way comparable to that Act.

11 · Your rights

You can ask us for a copy of your data, to correct it, to delete it, to receive it in a portable format, to restrict how we use it, and to object to uses based on legitimate interests — as New Zealand’s Privacy Act 2020 and, where they apply to you, the GDPR and UK GDPR provide.

  • Yourself, any time: export your data and delete your account in the panel at app.corewire.ai (Settings); change your email and sign-in methods there too; turn usage statistics and automatic problem reports off in Settings on each device and in the panel, and notifications off in the phone app.
  • Anything else: write to privacy@corewire.ai. We answer within one month, and may ask you to confirm the request comes from your account’s email.

If you are unhappy with how we handled your data, tell us first if you can. You can also complain to New Zealand’s Office of the Privacy Commissioner (privacy.org.nz), to the data protection authority of the EU country you live or work in, or to the UK Information Commissioner’s Office (ico.org.uk).

12 · California residents

Under the California Consumer Privacy Act, as amended by the CPRA: in the past 12 months we collected the categories above — identifiers (email, IP address, device keys), commercial information (subscription status), and internet activity (usage statistics, logs) — for the purposes above, and disclosed them only to the processors listed. We do not sell personal information and do not share it for cross-context behavioural advertising, and have not in the past 12 months; we honour Global Privacy Control as a request not to. We do not use sensitive personal information to infer anything about you. You have the right to know, to delete, to correct, and not to be treated differently for using these rights; write to privacy@corewire.ai, or have an authorised agent do so.

13 · Children

Corewire is not for children: you must be 16 or older to have an account. If we learn we hold data about someone younger, we delete it. If you believe a child has an account, tell us at privacy@corewire.ai.

14 · Security

Traffic between your devices is encrypted end to end with WireGuard; every connection to our services uses TLS; our databases and storage are encrypted at rest. Access to production systems is limited to the people who run them. If a breach puts your data at risk, we tell you and the regulators the law requires, without undue delay. Report vulnerabilities to security@corewire.ai; our disclosure policy is at /.well-known/security.txt on every host we answer on.

15 · Changes

We email account holders before a material change to this policy takes effect, and every version carries its number and effective date at the top of this page. Earlier versions are available on request.

Privacy questions and requests: privacy@corewire.ai · The agreement itself: the terms of service · Every legal document: corewire.ai/legal