privacy

Harness is an independent project, not a registered company. It is run by the people building it, and it does not have a corporate entity behind it today. If that changes, this page changes with it.

For anything in this policy, including access and deletion requests, reach us on our Discord.

• Reading your screen. Capture, OCR, image recognition, indexing, and history search happen in your browser. If you choose a remote answering model, the selected current or recalled frame or crop for that turn leaves the device.
• A short buffer of what you recently shared. So you can ask about something you scrolled past a minute ago. Held on your device only.
• Your memory. What Harness learns about you over time, like your preferences and the thread of your work, lives in a database on your own device.
• Your own AI provider keys, if you use them, are stored in your browser. A hosted turn sends the relevant key to Harness in the request so the server can call that provider; Harness does not persist it.

When you send a message, your device puts together only what's needed to answer it, and sends that. Specifically:

• Your message, and any file you attach.
• Selected screen evidence. This can be a current frame or crop while you're sharing, or a recalled historical frame from local screen history. Harness can only capture the tab, window, or screen you chose, and live capture stops the instant you stop sharing.
• Browser extension evidence. When you connect a page or select a section with the Harness extension, relevant page text, links, field values, and browser-action results can go through Harness to your selected answering model. This does not require screen sharing. Section 4 explains when a browser screenshot is included. Advanced browser automation can inspect more page data than the standard selected-section reader; information returned by a browser program becomes evidence for that conversation. A website receives actions and files when the requested task interacts with that website.
• A compact text log of recent screen changes (and audio transcript segments, if the shared tab has sound), so answers stay relevant between screenshots. In standard and private modes this working ledger transits Harness, is held in memory rather than written as durable screen history, and is discarded automatically within the hour. Confidential mode keeps it on your device.
• Anything from your memory that's actually relevant to your question.

The extension keeps settings and a bounded conversation mirror on your device. Before a managed restart or update, it saves a local recovery checkpoint for eligible page drafts. Recovery requires the same page document and account; checkpoints are eligible for 15 minutes and are removed after recovery or when checked after expiry. Browser-program traces and generated screenshots are stored locally under the conversation's retention rules. Copy diagnostics in extension settings includes version, browser, and connection status, without page content, conversations, or account identifiers. These diagnostics are shared only when you choose to send them.

The Harness browser extension (“Harness · point & ask”) brings a Harness conversation and browser help to the page you are working on. Here is exactly what it can do with your browsing, in plain terms.

• It reads a page when you use it. It reads a page when you select a section of it, when you send Harness a message while that page is connected to the conversation, or when you ask Harness to do something in your browser. Once you agree to what Harness reads in the extension's setup, the conversation follows the tab you are on by default, on sites you have given the extension access to; you can keep one page or pause this in the companion or the extension's settings. While it follows, the extension tells your open Harness tab the address and title of the page you are on each time you switch tabs, so the companion can show which page it will use; Harness does not keep a history of them. If you turn on Follow along, which is off by default, Harness also sends the current page's title and address, not its contents, to your AI model so it can offer help as you browse. It does not read the contents of pages you have not connected or asked about.
• What it can read. On pages you ask about: the text, links, form fields and their values, the page layout, and a screenshot of the tab. When you select a section, the Screenshot option on the prompt decides whether one is included; it starts on. When the conversation follows your tab, Harness can take a screenshot when it needs to see the page. Password fields, hidden fields, payment codes and areas a site marks private are left out of normal page reads and screenshots. This is not a guarantee of finding every secret: ordinary text and field values on a page you ask about are part of what it reads.
• Where it goes. What the extension reads goes through Harness to the AI model you selected, to answer you or complete your request, and is then handled like the rest of the conversation under this policy, including how long it is kept (sections 5 and 12). The extension itself sends it nowhere else. Nobody at Harness reads it unless you ask us to, for example to look into a problem you report, or it is needed to investigate security or abuse, or the law requires it.
• Acting in your browser. When you ask for a task, Harness can click, type, fill in forms, switch and open tabs, move between pages, and download or upload files for that task. Chrome shows its own “started debugging this browser” notice while Harness is controlling a tab. Harness can open and move between any sites you have given the extension access to without asking again, so choose that access in Chrome with care. Downloading a file from a site the task has not used yet waits for you to allow it. Downloads Harness starts that Chrome flags as dangerous are cancelled.
• Browser automation. For harder tasks, Harness can write a short program that runs on the page. These programs run in a locked-down space inside the extension with no direct internet access, and they can see more of the page than a normal read, including fields a normal read leaves out and anything else the page itself can reach. Browser automation also starts once you agree in setup, and can be turned off in the extension's settings.
• Documents a page links to. When you ask, the extension can open a document a page links to, such as a PDF, using your existing sign-in to that website, the same way your browser would.
• Site tools. Some websites offer tools for AI assistants. The extension uses them only if you turn site tools on in its settings; they are off by default.
• On your device. The extension keeps its settings, a short copy of the on-page conversation, and recovery drafts in your browser's storage; removing the extension deletes them. Files and records from browser tasks are kept on your device by the Harness app, under that conversation's retention rules.
• What it never does. We don't sell what the extension reads, use it for advertising, use it to decide anyone's creditworthiness, or use it for anything other than answering you and completing what you asked. It is shared only as needed to answer you: with the AI provider, and any routing service, described in sections 6 and 7.
• Chrome Web Store policy. The use of information received from the Harness browser extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
• Harness's own site. The extension connects only to your signed-in Harness tab at tryharness.ai. Other websites have no way to talk to it.

• Account. Your email address, and a name or photo if you add one.
• A copy of recent messages, plus each conversation's title and a short summary. This supports recent chat continuity and search; the full conversation lives on your device. We drop the message copy after about a month; only the title and summary stay.
• Profile. A short summary Harness keeps of how you like to work, used to shape its replies.
• Writing samples. Messages you've sent, so Harness can match your voice when it drafts something for you. Deletable anytime.
• Billing. Your subscription and payment history. Stripe handles your card details directly; we never see them.
• Encrypted backup, if you turn it on. A sealed copy of your memory and conversations, so they survive a lost device and follow you to a new one. We store it, but can't read it. Only you hold the key, and if you lose it, neither can we recover it.
• Background tasks. If you ask Harness to keep working after you close the window, or to delegate something, we keep the instructions and results so they're there when you come back.
• Prediction research and monitoring, if you use these features. We keep the market references, selected sources, monitoring rules, positions, and operating-payment records needed to resume and explain your strategy. Quotient receives the public market identifiers you research, not your screen stream or private screen history. If you explicitly connect a Quotient API key in advanced settings, Harness stores that integration key encrypted on the server so monitoring can continue; removing the connection deletes the stored key.
• Short-lived technical logs, used for billing and to keep things running smoothly, like basic connection and usage records. These don't contain what you said, and are deleted automatically within days.

Harness never trains AI models on your data. You choose how your requests are handled, in settings:

• Standard. The default. Gets you the best available AI, including major closed models — the provider sees your message to answer it, but not who you are.
• Private. Skips closed AI models entirely, using only open models from providers who commit to not keeping your data.
• Most private. Uses AI running in specially secured, verified environments. The compact screen ledger stays on your device, and web search plus general-purpose tools are switched off. If explicitly enabled, a separately requested work-pattern audit can use an approved end-to-end encrypted route.

For Standard and Private requests, we often use a routing service to find an available AI provider; it can see the request on its way to that provider. It never sees anything in Most private mode.

When you use a frontier model, meaning one of the large, closed AI models rather than an open or on-device one, your request runs through Venice, the AI infrastructure Harness is built on. Your message, and your screen content while you're sharing, go to Venice to produce the answer. Venice doesn't receive your name, your email, or anything that identifies your account, only the request itself.

Prefer to avoid frontier models entirely? Choose Private or Most private in settings.

Analytics are anonymous by construction, not by promise. An event can never be attached to your account, your email, or your name. We don't record your screen or the interface, don't collect the text of things you click, and don't capture error messages automatically, since those can carry data we don't want. What remains is simple counts: pages viewed, buttons clicked, how long a reply took.

If you run Harness on your computer, once a day it also tells us how much your agents did the day before: how many tasks were posted, finished and failed, how many handoffs, threads, posts and coordinator rounds, split by agent type. It never sends the text of your work, the names of your files or folders, or anything about the computer, and we add the numbers into one total for the day without your account. To turn it off, run npx tryharness usage-totals off.

• Sign-in. Keeps you signed in. Can't be read by page scripts.
• Guest. If you try Harness without an account, lasts seven days so your trial conversation survives a refresh. Cleared when you create an account.
• Analytics. Avoids counting one person as many. Not linked to your account.

We don't use advertising cookies, and we don't sell data.

Guest conversations are handled the same way signed-in ones are. To stop automated abuse of free usage, we record the IP address a guest session was created from, along with a daily count. If you later create an account, your guest conversation moves onto it.

• Delete your account and everything in it, from settings. One operation, and it can't be undone.
• Delete a single conversation, at any time, from the interface.
• Delete your encrypted backup and its history.
• Delete your writing samples.
• Wipe local data by clearing site data in your browser, which removes your on-device memory and screen buffer.
• Turn off screen sharing at any time, which stops all capture immediately.

For anything you can't do yourself, ask on our Discord and we'll action it.

Your conversation titles and summaries are kept until you delete them or your account. The messages themselves are kept for about a month, then only the summary remains. Live screen and audio context is discarded within the hour. Technical logs are deleted within days. Guest sessions last seven days. Backups persist until you delete them.

Traffic is encrypted in transit, and your data is kept separate per account in our systems. Encrypted backups are sealed on your device with strong encryption (AES-256) before they're ever sent to us, using a key made from your passphrase, which we never see.

No system is perfectly secure, and we won't claim otherwise. If you find a vulnerability, please tell us on our Discord.

Harness is not intended for anyone under 13, and we do not knowingly collect their data.

When this policy changes materially, we'll update the effective date and say so in the product.