Privacy policy

This policy explains how Stack Forward LLC (Stack Forward合同会社) (“Haarness”, “we”), Level 9, Ariake Frontier Building Tower B, 3-7-26 Ariake, Koto-ku, Tokyo 135-0063, Japan, handles personal data when you visit haarness.ai or use Haarness Cloud. For personal data about you as a user of the Service we are the controller. For personal data that you put inside a workspace — for example your own customers' data in a repository — you are the controller and we process it for you under the Data processing agreement.

Using Haarness locally is not covered here, with one exception. The open-source CLI, terminal UI and Desktop app keep your work on your machine and send model requests directly to the provider you configure. Apart from the app usage statistics described below, which you can turn off, they send us nothing unless you sign in to Haarness Cloud.

Summary

• We collect what we need to run your account, your workspaces and your billing — and nothing for advertising. There are no analytics, advertising or tracking cookies on the site.
• Your workspace contents stay on your workspace's own encrypted volume. We do not use them, or your prompts, to train models, and we do not sell personal data.
• Prompts you send through the managed router go to the model provider you choose. Our metering records count tokens and cost; they never store prompt content.
• If you turn on notifications in Haarness for iPhone, they reach your phone through Apple. A notification shows the chat's title, the project and computer or the Cloud session's name, and a fixed phrase for what happened, such as “Wants to run a command”. A chat's title usually comes from its first message: a chat Haarness Cloud starts for you is named after the first 80 characters of that message, and other chats get a short title written from it unless you name them. So the start of a prompt can reach Apple through a title. Notifications never contain commands, file contents, questions, your prompts beyond a chat's title, or the agent's output.
• If you turn on notifications in Haarness for Android, they reach your phone the same way through Google (Firebase Cloud Messaging), with the same content, so the same applies to Google.
• The Haarness apps send us daily usage counts — never prompts, code, file names or paths — so we can see what to fix and improve. Turn them off in the app's Settings, with haarness telemetry off, or with HAARNESS_TELEMETRY=0.
• If you report an agent's reply in a Haarness app, we keep your report with the reply's text, so we can review it after the chat is gone.
• You can export workspaces, revoke devices and keys, and delete your account yourself, on the web or in the Haarness apps (how to delete your account), and ask us for a copy of your data at [email protected].

What we collect

Our servers' request logs record, for each request, the method, the route pattern (such as /api/v1/workspaces/{id}, not the actual path with its identifiers), the status, how long it took and a request identifier — ours, or one your client sent. They do not record IP addresses, query strings, headers (including authorization headers and cookies), request or response bodies, or prompt content. Error messages from our payment, sign-in and hosting providers are shortened and stripped of email addresses and credentials before we log or store them, and our logs of service emails show only the kind of email and a masked address, never its content.

We do not knowingly collect data from children under 16, and the Service is for people aged 18 or over.

Why we use it, and our legal basis

We do not use personal data for advertising, profiling or automated decisions with legal or similarly significant effects. We do not send marketing email without your consent.

Who we share it with

We share personal data only with the service providers that run parts of the Service for us — hosting, storage, payments, email and, for the managed router, the model provider you select. Each is bound by a contract that limits its use of the data to providing its service to us. The current list, with what each receives and where, is on Subprocessors.

• Model providers. When you use a model through the managed router or a cloud agent, the request — including the prompt, files and tool results the agent sends — goes to that model's provider to generate the response.
• Stripe processes payments as our processor and, for payment fraud prevention and compliance, as an independent controller under its own privacy policy.
• Google receives your sign-in request only if you use Google sign-in, under Google's own privacy policy.
• Apple delivers the notifications of Haarness for iPhone, once you turn them on: it receives the phone's notification token and what each notification shows — the chat title, the project, computer or Cloud session name and a fixed phrase for the kind of request. A chat's title can be the start of its first message (see above); commands, file contents, the rest of your prompts and the agent's output are never sent.
• Google delivers the notifications of Haarness for Android through Firebase Cloud Messaging, only once an Android phone with Haarness registers for notifications: it receives the phone's notification token and the same content as Apple, as a data message the app turns into the notification. Commands, file contents, the rest of your prompts and the agent's output are never sent.
• Other users see what you share with them: your name and email in shared accounts, and what you publish to the marketplace.
• Authorities, when the law requires it. We review each request and disclose only what is legally required.
• A successor, if our business is merged or sold, under this policy and with notice to you.

International transfers

Cloud workspaces run in the US East (Ashburn, Virginia, United States) region. Some of our providers are based in, or process data in, the United States and other countries. Where personal data from the European Economic Area, the United Kingdom or Switzerland goes to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (and the UK addendum), or on the provider's certification under the EU–US Data Privacy Framework, with additional safeguards where needed. Ask [email protected] for a copy of the relevant safeguards.

How long we keep it

When you delete your account (in account settings or the Haarness apps, as Delete your Haarness account shows) or ask us to, we delete the account, its workspaces, volumes, backups and exports, your sign-in identities, the usage statistics of the apps linked to you and your reports of agents' replies, within 30 days, keeping only the financial and audit records listed above. Sign-ins, devices and keys end at once, and a paid plan is cancelled at once.

How we protect it

Workspaces run on separate machines with their own encrypted volumes; the gateway only connects a client to the workspace its short-lived ticket names. Session tokens, API keys, router keys and attach tickets are stored hashed and shown to you once. Secrets you give agents are encrypted at rest. All traffic uses TLS. More on the Security page.

Your rights

Depending on where you live — including under the GDPR, the UK GDPR, the California Consumer Privacy Act and Japan's Act on the Protection of Personal Information — you have the right to:

• access your personal data and get a copy of it;
• correct inaccurate data;
• delete your data;
• port data you gave us, in a machine-readable format;
• object to processing based on legitimate interests, and restrict processing;
• withdraw consent where processing is based on consent;
• not be discriminated against for exercising these rights.

What you can do yourself today: export any workspace (Export on the workspace page), delete workspaces and sessions, revoke devices and keys, read your full usage and ledger in Billing, and delete your account (Delete account in account settings, or in the Haarness apps). For everything else — a copy of your account data, correction — email [email protected] from your account's address. We confirm it is you, then answer within one month (extendable by two months for complex requests, in which case we tell you why).

You also have the right to complain to a data-protection supervisory authority, in particular in the country where you live or work. Our lead authority is the Personal Information Protection Commission of Japan. We would appreciate the chance to address your concern first.

We do not sell or “share” personal information as those terms are defined in the California Consumer Privacy Act, and we do not use sensitive personal information to infer characteristics about you.

Representatives

EU representative: none appointed yet (write to [email protected]). UK representative: none appointed yet (write to [email protected]).

Changes

We will update this policy when what we collect or who processes it changes. For material changes we notify you by email or in the Service before they take effect. The date at the top of this page shows the current version.

Contact

Privacy requests: [email protected] · Stack Forward LLC (Stack Forward合同会社), Level 9, Ariake Frontier Building Tower B, 3-7-26 Ariake, Koto-ku, Tokyo 135-0063, Japan