Benchday shows you the terminal sessions running on your own computers. To do that, some of what is on those screens has to travel through our servers. This page explains exactly what travels, what we keep, who else sees it, and what you can switch off.
This summary is here to be readable. The sections below are the operative terms, and they win if the two ever disagree.
Benchday is a product of Zigzag Technologies, Inc., a company incorporated in Canada. In this policy, "Benchday", "we", "us" and "our" mean Zigzag Technologies, Inc.; "you" means the person using Benchday.
This policy covers the Benchday mobile apps, the desktop and web clients at benchday.zztech.io, the benchday command-line tool, the Benchday daemon you install on your own machines, and the hub service they connect to. It does not cover the coding agents you run (Claude Code, Codex, OpenCode, Aider and others), the terminal programs you launch, or any third-party service you reach from inside your own sessions — those are governed by their own terms and privacy policies.
Benchday is currently in private testing. Features, defaults and the details described here may change as it develops; material changes are handled under section 13.
It helps to know the shape of the system, because it determines what we can and cannot see.
Benchday is not end-to-end encrypted. Terminal content is protected in transit, but our hub processes it in the clear in order to relay it and to run the features you ask for. If you would not want a service provider to be technically capable of seeing something on your screen, do not put it on a screen you attach to Benchday.
To create and secure your account we hold a username, a password verifier (we store a cryptographic hash, never your password), and — if you sign in with GitHub or Google, or add one — an email address and the basic profile the provider returns, such as a display name and avatar. We record the devices registered to your account (a device identifier, a device name, app version) and the machines you enroll, so that we can route you to the right computer and so you can revoke access to any of them.
While you are attached to a session, live terminal content is relayed through our hub so that it can appear on your device, along with the input you send. This is the core of what the product does and it cannot be switched off while you are using the product to view a session.
Depending on the features you use and your privacy settings, the hub may also store derived or captured content: session and pane titles, summaries and digests, text used for search and for resuming past work, conversation context from coding agents running on your machines, and records of pane activity. Whether agent conversation context is stored on the hub is controlled by the AI context on hub setting.
If you dictate, your audio is streamed to a speech-recognition engine to be turned into text — either an engine Benchday operates or one you configure yourself.
Voice audio retention is on by default. Recorded clips are kept on our server for 7 days so the feature can replay them, then deleted. You can turn this off at any time in Settings, under Privacy & data; with it off, dictation still works — your audio is transcribed and then discarded rather than stored. See also the retention rules in section 8.
If you upload a file to one of your machines or download one from it through Benchday, the file passes through the hub in the same way terminal content does.
We collect operational telemetry needed to run the service: connection events, errors, performance measurements, network usage counters, app and daemon versions, and the coarse identifiers needed to attribute them to an account and device. The app also keeps a local "flight recorder" of what happened in the app; by default those recordings stay on your device and are not uploaded. Diagnostic logs reach us only when you push them, or under a support grant you approve (section 10).
Paid plans are billed through Stripe. Stripe collects and processes your card details directly; we never receive your full card number. What we store is the reference identifiers Stripe gives us for your customer and subscription records, your plan tier, and its status and renewal date.
We do not sell your personal information, and we do not use your terminal content to build a profile of you for marketing.
Two different things are easy to confuse here, so we separate them.
Benchday uses large language models to generate session titles, summaries, digests, read-aloud narration, suggested actions and search results. To do this, the relevant content is sent to a model provider on our behalf and a result comes back (see section 6). This happens because you are using the feature — it is not training.
Using your session content to train or improve models is off by default. New accounts start with it off, you are shown the choice before you connect your first computer, and you can change it at any time in Settings → Privacy & data. Relayed terminal content is never used for model training.
If you do turn it on, understand that it cannot be fully undone. Content used to improve a shared model becomes part of that model. Turning the setting off later stops future use, and deleting your data removes it from our stores — but neither removes what a model has already learned. We tell you this in the app before you consent, and we are repeating it here for the same reason.
Turn it on only for sessions whose content you are actually allowed to share. If your work is under an employer's or client's confidentiality obligation, that is your call to make, not ours.
Zigzag Technologies, Inc. is a Canadian company and also operates an affiliated entity in China. Our hub and the service providers listed above operate in a number of countries, and SiliconFlow is based in China. Using Benchday therefore involves your data being transferred to and processed in countries other than the one you live in, including countries whose data-protection laws differ from your own and where authorities may have rights of access under local law.
If that matters to your work, note that the AI features are the surface that sends content to model providers, and they can be limited through the settings described in section 9.
We keep data only as long as we need it, and the hub runs an automated age-based sweep that deletes stored content once it passes its retention window. Different classes of content have different windows: conversation and transcript text, session recordings, voice audio, activity records and suggestion-feedback records each expire on their own schedule, and voice audio has the shortest one.
Some accounts used for our own product development are exempt from these windows so that we can analyse our own usage. That exemption applies only to the account it is set on and cannot reach another user's data.
The controls live in the app under Settings → Privacy & data. They are real switches on real behaviour, not preferences we consult when convenient.
| Control | What it does |
|---|---|
| Local-only mode | Stops the app sending content to the hub beyond what is needed to connect you. |
| AI context on hub | Governs whether agent conversation context is stored on the hub for titles, narration, search and resuming work. |
| Voice audio retention | Governs whether dictation audio clips are retained on the hub. |
| Adaptive-chips training | The model-training consent from section 5. Off unless you turn it on. |
| Session recording | Per-device. Controls the local flight recorder. |
| Push log now | Per-device, and deliberately manual — sends a diagnostic log to us when you decide to. |
| Delete my data | Erases the content the hub holds for your account. See below. |
It removes the content the hub stores for your account — recordings and their audio, activity records, pane journals, suggestion observations and feedback, and the agent conversation context, titles, search text, embeddings and inventories belonging to the machines you own. It keeps your identity — your account, devices, grants and sign-in — so that you stay logged in and can keep using Benchday. It does not touch the transcripts and files on your own machines, which were always yours and never ours to delete. As noted in section 5, it also cannot reverse the effect of content that was already used for model training.
You can ask us for a copy of the personal information we hold about you, ask us to correct it, or ask us to delete your account entirely rather than just its content. Write to contact@zztech.io and we will respond within a reasonable period. Depending on where you live you may also have the right to complain to a data-protection authority.
Sometimes diagnosing a problem needs someone at Benchday to look at data from your device or account. That is gated:
Separately, a small number of our staff can access production systems as part of operating them. Access is limited to what the role requires.
We hold no security certifications. Benchday has not been audited against SOC 2, ISO 27001, HIPAA or any comparable standard, and we make no such claim. No system is perfectly secure, and we cannot guarantee that yours will never be compromised.
Benchday is a developer tool and is not directed at children. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us with personal information, write to contact@zztech.io and we will delete it.
We will update this policy when what the software does changes. The "Last updated" date at the top always reflects the current version. If a change materially reduces your privacy or expands how we use your data, we will give you notice in the app or by email before it takes effect, and where the law requires consent we will ask for it rather than assume it.
Questions about this policy, a request about your data, or a security report — one address reaches us for all of it.
Privacy questions, data requests and security reports all go to the same place, and a human reads them.