Security — GENbyAI

Local software, with nothing of ours in the middle

BOOX Mirror connects your Mac and tablet over USB or local Wi-Fi. Our servers do not relay screen content.

The app has no account or telemetry. Settings and logs stay on your Mac, so we cannot recover or inspect them remotely.

BOOX Mirror — the same five questions, answered plainly

What leaves your machine: Screen frames and, if enabled, input events travel over USB or your local Wi-Fi network. Nothing goes to GENbyAI.
What is stored, and where: Connection settings stay on your Mac. We collect no screen content, usage data or telemetry.
Account required: No account or sign-in.
Cloud processing: None. No GENbyAI service is in the connection path.
AI in the product: No AI features or model calls.

BOOX Mirror

The cable, the network and the permissions

Screen frames go to the tablet. If enabled, input events return to the Mac.

USB: the cable is the whole path

USB needs no network. It is required once to pair the tablet and install the receiver, even if you later use Wi-Fi.

How pairing works

Over USB. On the BOOX you turn on Developer options and USB debugging, then unlock the tablet and accept Allow USB debugging for this Mac. That approval is what lets the Mac check the connection and install the receiver.
Over Wi-Fi. The Mac shows its local IP address and port beside This Mac, along with a six-digit pairing code. You type all three into the BOOX, and macOS asks for local-network access at that point.
What the code is not. The six-digit code is part of starting a Wi-Fi connection, not protection for it. The traffic it starts is still unencrypted, so it does not help against someone who is already on the network and watching it.

The permissions macOS asks for

Screen Recording and USB access are required for setup. Accessibility is needed for tablet control; Local Network is needed for Wi-Fi. Details below.

Each permission, and the specific thing it is for

Screen RecordingRequired: Required by macOS for any app that captures display output. Without it there is nothing to send to the tablet.
Accessibility: Only needed for Control Mac from BOOX — it is what lets tablet input drive the Mac. Skip it and the display stays view-only.
Local network: Only for Wi-Fi connections, to reach the tablet on your own LAN. USB connections never request it.
USB device accessRequired: For the debugging tunnel used during setup and for USB connections.

The display is view-only until you change that

Window capture is view-only unless you grant the macOS Accessibility permission and enable Control Mac from BOOX. Until both of those are true, input on the tablet cannot drive the Mac, and the only thing crossing the cable or the network is screen output. If you never turn it on, nothing travels back.

Full requirements and limitations on the BOOX Mirror page

Distribution

Code signing: ad hoc signed, not notarised

The current build of BOOX Mirror is ad hoc signed and has not been notarised. It is signed, but not with a developer identity that macOS can attribute to us, and Apple has not run its notarisation checks over the file we ship. On first launch macOS says it cannot verify the developer. You dismiss that alert, open System Settings, go to Privacy & Security, and choose Open Anyway, then Open.

What that actually means for you

macOS cannot tell you who built the app. The warning is accurate. There is no verified developer identity for the system to show you, so it shows you a warning instead.
You have to allow it explicitly. The app will not open until you go into Privacy & Security and permit it. That step is deliberate on Apple’s part, and it is a step we are currently making you take.
Apple has not scanned this build. Notarisation includes an automated check of the submitted software. This build has not been through it, so you do not have that second opinion — you have ours.
Your judgement is doing the work. Because the signature cannot identify us, where the file came from is what is left. Install the DMG from the link in your receipt or from this site, and not from a copy someone passed on to you.

It is outstanding work

Notarisation is on the list and it is not done. Until it ships, the unverified-developer warning is expected behaviour rather than a sign that something went wrong, and we would rather you read that here than meet it for the first time after paying. When it changes, this section changes — not before.

This website

What this site does while you read it

No analytics, no trackers

There is no analytics product on this site, no tag manager, no advertising pixel, no A/B tooling and no third-party embed. The one typeface is downloaded when the site is built and served from this site, so opening a page does not call out to a font host either.

Preferences stay in your browser

The text size, contrast, motion and focus controls on the accessibility page save your choices in your own browser’s local storage, under a single key. They stay on that device, they are never sent to us, and clearing the site’s data removes them. Checkout also sets a short-lived, essential cookie to limit download access to the buyer's browser.

Payment happens somewhere else

Stripe Managed Payments is our merchant of record. Checkout, card details, tax and the receipt are handled on their side. There is no card form anywhere on this site, so card data never reaches us and cannot be exposed by us. We also hold no order database — the provider’s dashboard is the record, and we have not built one of our own to sit alongside it.

A gap worth naming

What our hosting provider records on our behalf is set out under Server logs on the privacy page. What we have not confirmed is that provider’s own retention period for those records, so we are not going to quote one from memory. When it has been checked, it will be stated there.

Disclosure

Reporting a vulnerability

If you have found something that looks like a security problem — in our software or on this site — email [email protected]. It reaches a person, and you do not need to be certain it is a real issue before you send it.

What helps us reproduce it

The product and the version you are running, or the page address.
What you did, in enough detail that we can do it again.
What happened, and what you expected instead.
Any conditions it needs — a particular macOS version, a shared network, a device attached, a specific transport.
A proof of concept if you have one. Please leave other people’s data out of it.

What happens next

We will acknowledge your report. We have not set a response-time target, so we are not going to quote one — you will get a reply from a person rather than a ticket number. If a report leads to a change, the change is described on the relevant product page or on this one.

What we do not have

No bug bounty. We do not pay for reports, and we would rather say so up front than let you spend time expecting otherwise.
No PGP key. Email to us arrives in plain text. Keep the sensitive detail out of the first message; if a report needs a more careful channel, say so and we will arrange one.
No advisory feed. There is no published security advisory list yet. If a report leads to a fix, it is described on the relevant product page or on this one.

Email [email protected]Other ways to get help