Skip to main content

Privacy

Celeris is a local app. Your files, screen captures, command output and session history live on your machine. What leaves it is what a task needs to be answered, plus optional product telemetry you control.

What is sent to run a task​

To answer the turn you asked for, Celeris sends the model:

  • your prompt;
  • the screen capture, when the turn started from the hotkey. Celeris resizes it before sending and attaches it only to that turn, not to follow-ups;
  • the name and window title of the frontmost app, when available;
  • the tool results the task needs, such as the output of a command you approved.

Nothing is sent for a turn you do not start. Turns started from the chat window carry no screenshot at all.

What stays local​

  • Session history. Celeris writes every session's transcript, tool calls and output to a log on your device, and replays them from there.
  • Credentials. Your Celeris key, connector tokens and any speech provider key are stored in your operating system's keychain. Only Celeris's background process uses them, and they are never shown in the interface.
  • Your allowlist and settings.

Deleting a session removes its local log.

Telemetry​

Celeris reports anonymous usage under an install identifier that is not tied to your account: which features are used, whether a task succeeded, and roughly what kind of work a session was. Celeris uses it to decide what to build next.

Telemetry never includes your prompts, screen captures, file contents, command output, or the raw list of applications on your machine. Where the shape of your work is useful, Celeris aggregates it ("looks meetings-heavy") rather than itemising it.

You can change what is shared, including turning telemetry off, in Settings → Privacy.

Product feedback​

When you send feedback from inside Celeris, you choose what to attach, and the form shows you each attachment in full before you send it.

  • A picture of the Celeris window, taken as the form opened, so a defect in Celeris's own interface can be seen rather than described. This is Celeris's window only, never your screen, and it is attached unless you untick it.
  • Recent activity in the session you are reporting on: what you asked and which tools ran, as short lines. Attached unless you untick it, and shown in the form so you can read exactly what will be sent.
  • The message you opened feedback from, when you started from one.
  • What is on your screen: the active app, its window title and a screen capture. This stays off unless you turn it on.

These attachments are the only case where session content leaves your machine outside of running a task, and they are kept for a bounded period.

Celeris removes the secrets it recognises from the text attachments first: your description, the session activity, and the attached message. The pictures are sent as captured. Celeris does not read text out of an image to redact it, and it deliberately does not scrub what your transcript displays on screen. A token that a command printed is therefore visible in a picture of the Celeris window. That is why the form shows you each picture before you send it. Look at it, and untick it if it shows something it should not.

Support bundle​

When Celeris support needs to see what happened, Celeris can gather a bounded diagnostic bundle: this device's local-data summary, a chosen session's trajectory, connector health, and installed-package and release state. It is untrusted diagnostic data: it cannot run instructions or grant Celeris any authority. Secrets, tokens and private file paths are removed before anything is written, and the preview lists every redaction and omission before you export. Build one in Settings → Privacy; it is written to Celeris's own folder for you to hand over.

The Include only these applications list on this page also has a fixed exclusion: Celeris itself and known sensitive surfaces are never recorded in Activity History, whatever the list says.

Permissions you can revoke​

Screen Recording, Accessibility, the microphone and each connector are separate grants. Revoke any of them in your operating system's settings, or disconnect a connector in Settings → Tools → Connectors, and it takes effect immediately. Celeris loses that capability and nothing else changes.