What we hold, and what we never see.
GATKO Technology Inc. handles personal information under Canada's PIPEDA. This page says exactly what is collected for the website, the waitlist and the licence service — and what stays on your machine.
01Who we are, and what this covers
GATKO Technology Inc. is the organisation responsible for the personal information described here (the data controller, in GDPR terms). GNexusOS is our product.
GATKO Technology Inc. — incorporated in Canada. 318-30 Baseball PL, Toronto ON M4M 0E8, Canada.
GNexusOS is GATKO Technology Inc.'s product. The company's domain is gatkotech.com; the product's is gnexusos.com. Legal and privacy: [email protected]. Product and support: [email protected].
This policy covers three things: the website at gnexusos.com, the GNexusOS waitlist, and the licence service that issues and activates GNexusOS licences. Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) is the framework we work to. Because the product sells internationally, section 10 sets out the rights that EU and UK customers have under the GDPR and UK GDPR. We do not claim any privacy certification or audit.
02The short version
- This website sets no cookies. None at all. There is no analytics, no tag manager, no tracking pixel, no advertising network and no third-party script on it.
- We never receive the contents of your work. Prompts, files, agent transcripts and conversations stay on your machine. So do your AI provider keys.
- The desktop application contains no analytics or telemetry. It sends us no usage reporting of any kind.
- When purchasing opens, the application will check its licence with us — sending a licence id, and nothing else. On every launch, plus daily for about the first two weeks after a purchase and about once a year after that — until your copy becomes self-sufficient, after which it never contacts us again. Section 7 says exactly what is sent, how often, what that reveals, and why it does not stop sooner.
- What we do hold is small and listed below: a waitlist entry if you gave us one, and a licence record if you buy.
- We do not sell personal information, and we do not share it for advertising.
03The website
The site is static. Visiting a page does not create an account, set a cookie, or write anything to your browser's storage.
What is unavoidable
The site is hosted on Cloudflare Pages. Serving a page means Cloudflare processes the network request, which includes your IP address, as any web server must, and applies its own edge security protections. We do not receive a per-visitor log or a visitor identity from it.
Web fonts, named because it is a real transfer
The site loads two typefaces (Inter and JetBrains Mono) from Google's font servers at fonts.googleapis.com and fonts.gstatic.com. Your browser requests those files directly from Google, so Google receives your IP address and browser User-Agent for that request, and its handling is governed by Google's own privacy policy. Nothing comes back to us from it, and no cookie is set by us.
Social links
The icons in the footer are ordinary outbound links to our profiles on X, LinkedIn, Facebook, Instagram, TikTok and YouTube. They are not embedded widgets or share buttons: those platforms receive nothing until you click, after which their own policies apply.
04The waitlist
If you submit your email address to the waitlist, we store, against that address:
- the email address itself;
- the time you signed up;
- a two-letter country code for the request (the country only — not a city, not a precise location);
- your browser's User-Agent string, truncated to 256 characters.
Why: to run the waitlist, to send you the dispatches you asked for, and to know roughly which countries the interest comes from. Our basis for this is your consent, given by submitting the form; you can withdraw it at any time (section 10).
Your IP address is not stored with your signup
To stop a signup form being abused, the service counts submissions per network address per hour. That counter holds the raw IP address for about one hour, keyed by address and hour, after which the storage expires it automatically. It is never written into your waitlist record and is not used for anything but rate limiting.
Resend
Your address is also added to our mailing list at Resend, the service that delivers our email, which sends the welcome message and later dispatches.
How long we keep it
Until you ask us to stop. The one-click unsubscribe link in every dispatch marks you unsubscribed at Resend and stops the email. To be straight about the limit of that: unsubscribing stops the sending, and does not by itself delete the signup record described above. Email [email protected] and we will delete it.
05GNexusOS licences
When purchasing opens, buying a licence creates a record in our licence service. It holds:
| Record | What it contains |
|---|---|
| The licence | The purchaser's email address, the tier bought, the entitlements (such as the number of agent seats), the update window, the time it was created, whether it came from a purchase or was granted, the time and reason it was revoked if it ever is, the payment provider's identifier for the purchase event, and the activation limit. |
| Activations | For each machine: a machine fingerprint supplied by the application, a machine label, when the machine was first and last seen, and when the slot was released if it has been. |
| Granted licences | For a licence GATKO gives away rather than sells: who received it, who authorised it, the stated reason, and the time. |
A machine label is supplied by you or by your computer, and in practice it often contains a person's name — “Dana's MacBook” is a typical computer name. If you would rather we did not hold that, use a label that does not identify anyone; you can release an activation and re-activate with a different one.
Why we hold this: to issue and support your licence, to answer the licence check-in described in section 7, to enforce the machine limit and the update window you bought, to handle refunds and chargebacks, and to keep the business and tax records a company must keep. Our basis is the performance of our contract with you and our legal obligations.
How long we keep it
Licence records are kept as business and tax records for as long as the law requires and for as long as they may be needed to answer a question about a purchase. A revoked licence is not deleted: the record of what was bought and what happened to it is the point of it.
06Payments
Paddle is the merchant of record for purchases of GNexusOS. Paddle takes your payment, issues the invoice and handles tax. We never see or store your card details. Paddle passes us what we need to issue your licence — such as your email address, what you bought, and its identifier for the transaction.
Paddle's own privacy notice governs what Paddle does with your payment information.
07The desktop application
GNexusOS runs on your machine. We verified the following in the application's own source before writing it here:
- No analytics and no telemetry. There is no analytics or crash-reporting SDK in the application, and it sends us no usage data.
- Your work does not pass through us. Conversations, tasks, files, artifacts and agent records are stored on your disk. When an agent calls an AI model, the request goes from your machine directly to the provider whose key you configured, under your own account with that provider — not through any GATKO server.
- Your provider keys stay with you. API keys are encrypted on your machine using your operating system's own encryption facility (on macOS, backed by the login Keychain) and are never transmitted to us.
What the application sends
Update checks. The application checks our update feed at updates.gnexusos.com for a newer version, and downloads it in the background when there is one. Like any download, that request necessarily carries your IP address and the version information needed to answer it, and it is served by Cloudflare. We do not use it to build a profile of you.
The two below concern licences. Neither happens today, because purchasing is not open and there are no licences to check; they are written here because they will be true of a licensed build and a privacy policy that waits until then is a privacy policy nobody read before buying.
Licence activation. Activating a machine, or releasing it, will send the licence id, the machine fingerprint and the machine label to the licence service — the activation record described in section 5. Nothing about your work is included.
The licence check-in. The application will contact the licence service and send one thing: the licence id. Not your prompts, not your files, not your agent transcripts, not your provider keys, and no usage data of any kind. The service answers with the current state of that licence. How often it asks:
- Every time you launch the application — for as long as the licence needs checking at all, not only during the first fortnight. This is the one that catches a payment reversed months later.
- And at most once every 24 hours while it is running, during roughly the first two weeks after a purchase. The licence issued at the moment of purchase is time-limited, and this is the period in which a refund is still possible.
- And about once a year on a timer after that, indefinitely. Once the refund window has closed the check returns a licence valid for a year, and the application asks again before that year is out.
- Then it stops permanently if your copy becomes self-sufficient — which happens if we cannot be reached for six months, or if we publish a signed notice that the licence service has been retired. After that the application never contacts us again, and your copy keeps working.
The yearly check is also the point at which the application asks whether your update window was renewed, so it is one request and not two. Letting updates lapse does not affect it: the licence is renewed either way, because the right to run the software and the right to new versions are separate things. The Refund Policy explains why it is built this way, and the Terms of Service set out what it means for your licence.
We would rather be exact than flattering here. The application does not stop contacting the licence service after the first two weeks, and the check is not only on a timer: it happens every time you launch the application, for as long as the licence needs checking. That is deliberate — it is what lets us honour a payment reversed months after a purchase, which a chargeback can be. We are not going to tell you the connection ends when it does not, or that it is rarer than it is.
What it is not: it is not a heartbeat, and it is not a usage signal. It carries one licence id and no information about you, your machine or your work. It does not report how long you used the application or what you did with it, and nothing in it describes your activity.
But be clear about the one thing it does reveal: because a check happens when you launch, the pattern of those requests shows roughly when you opened the application. We do not use it for that, we do not build a profile from it, and the licence record in section 5 does not store it — but we are not going to claim a request tied to launching tells us nothing about launching. It is the honest cost of catching a reversed payment, and you should know it before you buy rather than after.
Like any request, a check-in necessarily carries your IP address in order to reach us, and the endpoint will be rate limited — which means counting requests per network address for a short period, as the waitlist form does (section 4). Your IP address is not written into your licence record, and the licence record is listed in full in section 5.
08Who processes data for us
| Provider | What for |
|---|---|
| Cloudflare | Website hosting, the waitlist and licence services, their data stores, and the update feed |
| Resend | Delivering email to the waitlist |
| Paddle | Payments, as merchant of record |
| Google Fonts | Delivering the site's two typefaces to your browser (section 3) |
These are service providers acting on our instructions, except Paddle, which is the seller in its own right for the payment, and Google, which serves the font request to your browser under its own policy.
09International transfers
GATKO Technology Inc. is in Canada. Our hosting, email and payment providers operate internationally, so information covered by this policy may be processed outside Canada, including in the United States, the United Kingdom and the European Union.
We choose providers that offer data-processing terms with recognised transfer mechanisms, such as the European Commission's standard contractual clauses. If you want to know what applies to a particular provider or a particular record, ask us at [email protected] and we will tell you.
10Your rights, and how to use them
Write to [email protected]. We may ask you to confirm that you control the email address a request concerns, so that we do not disclose or delete someone else's record on someone else's word. There is no charge for a straightforward request.
Everyone
You can ask us what we hold about you, ask us to correct it, ask us to delete it, and withdraw your consent to our dispatches.
Under PIPEDA
You have the right to access your personal information and to challenge its accuracy. We will respond within 30 days, as PIPEDA requires. If you are not satisfied with how we handled it, you may complain to the Office of the Privacy Commissioner of Canada.
Under the GDPR and UK GDPR, if you are in the EU or the UK
You have the rights of access, rectification, erasure, restriction of processing, data portability, and objection, and the right to withdraw consent at any time where consent is our basis. You may also lodge a complaint with your national supervisory authority. Exercising a right costs you nothing and we will not treat you differently for it.
Where erasure is requested, we will delete what we are not required to keep. A licence or purchase record that we must retain as a tax or accounting record is the exception, and we will tell you if that applies to your request.
11Security
Waitlist and licence data are held in Cloudflare's storage services, reachable only through the service endpoints described here. The administrative routes that read a licence back out require an operator credential that is held outside our code repository; a licence id alone does not read a licence record.
Your AI provider keys and your work are not part of this at all: they are on your machine, encrypted there by your operating system in the case of keys.
No service is perfectly secure and we do not claim otherwise. If a breach of security safeguards creates a real risk of significant harm, we will report it to the Office of the Privacy Commissioner of Canada and notify the people affected, as PIPEDA requires, and will meet the equivalent obligation where the GDPR or UK GDPR applies.
12Children
GNexusOS is a tool for professional work and this site is not directed at children. We do not knowingly collect personal information from children.
13Changes, and contact
We will update this policy when what we collect changes. The version in force always carries its “last updated” date at the top of this page.
Privacy questions, and any request about your information: [email protected], or GATKO Technology Inc., 318-30 Baseball PL, Toronto ON M4M 0E8, Canada. Product and support questions: [email protected].