Privacy Policy
Last updated: 21 October 2026
Nexus is self-hosted. The Software runs on your server and reads your helpdesk data there. That customer data is processed on your own infrastructure and is not sent to us, a deliberate design choice, and a strong reason to choose a self-hosted wallboard.
1. Who we are & our role
This website and the Nexus subscription/licensing service are operated by Joe Kane, a sole trader in the United Kingdom ("we", "us"). For the limited personal data we handle to run subscriptions and licensing, we are the data controller. Contact: [email protected].
Because Nexus is self-hosted, you are the controller of the helpdesk and operational data the Software reads on your own infrastructure; we never receive it, so we are neither its controller nor its processor. This policy covers only the data we handle: billing and licensing records, optional telemetry, problem reports you choose to send, and basic requests to this website.
If you take our optional managed hosting (self-hosting is the default), that changes for your deployment only: we run your own isolated instance on infrastructure we operate in a UK/EU region, so the helpdesk and operational data your board reads is processed there and we act as your processor for it, under our subscription terms. It stays a dedicated per-customer instance (never shared), secrets and tokens are encrypted at rest, and you can export your data and move to self-hosting at any time. Choose self-hosting and this paragraph doesn't apply: nothing operational reaches us at all.
1b. Our legal basis (UK GDPR)
Where UK/EU data protection law applies, we rely on: performance of a contract (to take payment, and to issue, validate and renew your licence); legitimate interests (to keep the service secure, to understand version/plan/provider adoption from minimal telemetry, and to respond to a problem report you send, balanced against your interests, and you can opt out of telemetry); and legal obligation (to keep invoicing/tax records). For this website's own analytics (§5c) we rely on legitimate interests (understanding which pages help people and fixing what's slow or broken), balanced against your interests: form values are never recorded, replays are masked, full IP addresses are kept only for 30 days, and Global Privacy Control or Do Not Track switches you to anonymous counting.
2. What this site collects
The marketing site is static. We collect only what's needed to run a subscription: when you subscribe, our payment processor (Stripe) collects and processes your billing details. We receive limited information from Stripe (such as your email, plan and subscription status) to issue and renew your licence. Separately, the site runs its own first-party analytics; exactly what that records is set out in §5c.
3. What the Nexus software processes
When you run Nexus, it reads metrics from the providers you connect (e.g. Zendesk Support + Talk). That processing happens on your deployment. API keys and tokens are encrypted at rest on your machine; read access is unauthenticated by design, so you should run Nexus on a LAN or behind a VPN/SSO.
3b. AI features (optional, off by default)
Two parts of Nexus can use an AI provider that you configure (Anthropic or OpenAI) with your API key. Both are opt-in:
- Daily summary sends only the day's aggregate numbers (tickets in/solved, the unassigned total, CSAT %, which monitored services are degraded), never ticket content or anything that identifies a person.
- Switchboard AI routing (the private add-on), when you switch it on, sends the subject and body of an unassigned ticket to your chosen AI provider so it can suggest the best engineer, and only for the tickets the built-in keyword router is unsure about. This is the only Switchboard path that sends ticket content off your server; it always falls back to the on-device router, and with AI routing off nothing is sent. Your API key is encrypted at rest.
When you enable either feature, that data is processed by the AI provider you picked under their terms; it still never reaches us. Leave them off and Nexus uses its built-in, on-device logic only.
4. Licensing data
To operate subscriptions we store a mapping between your Stripe customer/subscription and the activation token that lets your Nexus fetch signed licence keys. We use this solely to issue and renew your licence and to verify your subscription is active.
4b. Free trial without a card
If you start a free trial on the trial page, we store your email address and the date we issued your trial key, together with the key itself, its expiry date, the plan and an opaque licence id. That's all: no name, company or payment details, and nothing from your helpdesk.
We use it for three things only: to email you the key, to send one reminder a few days before the trial ends, and to keep it to one free trial per email address, which includes starting a paid plan straight away, without Stripe's separate card trial, if you buy with the same address. Your browser also remembers that address locally so checkout can pass it on; clear your site data to remove it. We never use it for marketing or newsletters. The record is deleted automatically a year after the key was issued; email us and we'll delete it sooner. The legal basis is taking steps at your request before a contract (sending the key and the reminder) and our legitimate interest in preventing repeat trials.
When the key is issued, this site's own analytics (§5c) also links that visit to your email address, so we can see which pages helped you decide. The key is sent through Resend (§5), like every other licence email.
5. Third parties
We rely on a small number of processors to run the subscription, and we don't sell your data:
- Stripe: payments and subscription management. Stripe's handling of your data is governed by Stripe's own privacy policy.
- Resend: transactional email only. When we send your activation token or trial key, billing/renewal notices, or your PDF licence certificate, your email address and that message content pass through Resend to deliver it.
- Cloudflare: hosts this website and the licensing service, and the infrastructure our own site analytics (Kestrel, §5c) run on. The analytics are ours: they're not a Cloudflare product, and nothing they record is shared with or sold to anyone.
And before you ask: no, we don't even use third-party fonts.
5b. Where your data is processed (international transfers)
This site and the licensing service run on Cloudflare’s edge network; payments run on Stripe; transactional email runs on Resend. These providers may process the limited data described above on servers outside the UK/EEA (for example, in the United States). Where they do, those transfers are covered by appropriate safeguards such as the UK International Data Transfer Agreement / Addendum or the EU Standard Contractual Clauses, as offered by each provider. We choose established providers that publish their own data-protection and transfer terms.
5c. Analytics & cookies on this website
This website uses Kestrel, our own first-party analytics, run by Joe Kane on Cloudflare. It loads from this site's own address; there are no Google, Microsoft or other third-party analytics or advertising tags here, and nothing it records is shared with or sold to anyone.
What it records: the pages you view; clicks, hovers and how far you scroll; which form fields you use (never what you type); JavaScript errors and page-speed timings; the site or campaign that referred you; your IP address, approximate location and network (town or region, country and network provider, as Cloudflare sees the connection); and your device, browser and screen size.
Session replay: it also records how each page was used (scrolling, pointer movement and clicks over the page's layout) so we can see where the site confuses people. Every form field is masked (passwords and card fields are never captured at all), and replays never include scripts.
Cookie: to recognise a return visit it sets one first-party cookie, _kid, lasting up to 400 days and only ever sent to this site (with a matching identifier in your browser's local storage).
How long we keep it: full IP addresses for 30 days, then truncated so they no longer identify a single connection; replays for 30 days; everything else for up to 13 months, then deleted. If your browser sends Global Privacy Control or Do Not Track, you're only counted anonymously: no cookie, no replay, and your IP truncated before it's stored. To have your data deleted, email [email protected].
Aside from that, your in-browser preferences (such as the theme you pick on the homepage) are stored locally in your own browser, not sent to us. Stripe’s hosted checkout may set its own strictly-necessary and fraud-prevention cookies when you go to pay; that’s governed by Stripe’s policy.
This is a website-only thing; the app is a different story. The site analytics exist purely for this marketing site (nexus.joekane.org); they are not part of the Nexus app you download or self-host. Your self-hosted deployment makes no analytics calls (to us or anyone else) at all: it talks only to the integrations you connect and to the licence server to validate your key, and it uses a session cookie purely to keep you signed in to your own deployment. The site analytics stop at the website; the product you run stays yours (its separate, minimal licence telemetry is described in §6).
6. Telemetry
Self-hosted (the default): minimal and opt-out. Licensed Nexus servers send a small periodic beacon (roughly every 30 minutes) to the licence service containing only an opaque licence id, the running version, the plan name, which helpdesk product the board is connected to (e.g. Zendesk or Freshdesk; the product name only, or "none" for a board run without a helpdesk) and an optional self-chosen instance label; no customer data, no helpdesk content, and nothing that identifies a person. Nothing operational leaves your server beyond that beacon. We use it solely for version-adoption, plan-mix and provider-mix figures. It is on by default for licensed installs and you can switch it off at any time in Settings → Licence (or with NEXUS_TELEMETRY_OPTOUT=1).
Managed hosting: the same minimal envelope, always on. If you take our optional managed hosting, the board checks in about every five minutes and this cannot be opted out of. It sends exactly the same fields listed above: { licenceId, version, plan, provider, instanceName? }. It does not send a hosted flag, uptime, health status, provider reachability, an error count or an error message, and never sends ticket content, credentials, customer data or anything that identifies one of your end-customers. The licence service adds a last-seen timestamp when it stores the beacon, allowing us to detect a silent board. Choose self-hosting and the same envelope is opt-out, exactly as above.
6b. Problem reports (user-initiated)
If you choose to send a problem report from the app (Settings → About & updates → Report a problem), we receive exactly what you type, an optional reply-to email if you provide one, and the same basic install facts as the telemetry beacon (version, plan, helpdesk provider, opaque licence id, and the board's name). The report is emailed straight to us so we can respond; it is not stored in any database, and sending one is always your action, never automatic.
6c. Website contact form
If you use the contact form on this website, we receive your name, your email address, the topic you pick and the message you type. It is emailed straight to the developer so we can reply; it is not stored in any database, and your email address is used only to respond to you. The form is rate-limited and protected by a spam honeypot; sending one is always your own action.
7. Your rights
Depending on your location you may have rights to access, correct, export or delete the personal data we hold (which is limited to billing and licensing records, and the email address behind a free trial). We keep those records only as long as needed to run your subscription and to meet our legal and tax obligations (typically up to seven years for invoicing records after a subscription ends), then delete them. Contact us to exercise any of these rights. If you're in the UK or EU and aren't satisfied with how we've handled your data, you also have the right to lodge a complaint with your supervisory authority (in the UK, the Information Commissioner's Office).
8. Changes
We may update this policy; the “last updated” date above reflects the latest version.
9. Contact
Privacy questions? Get in touch.