Legal
Privacy Policy
Effective . This policy explains how Haze AI collects, uses, and shares information when you use Haze at usehaze.ai, the desktop app, and related services. Questions: sam@usehaze.ai.
1. Who we are
Haze AI operates Haze, an AI workspace. This policy covers the website, the Haze desktop application, account and billing pages, public profiles, servers and invites, and the Haze API. It does not cover third-party sites or model providers you reach through Haze — they have their own policies.
2. Information we collect
We collect what you give us, what the product needs to run, and limited technical data:
- Account. Email, password (stored hashed, never in plain text), name, username, avatar, bio, company, and website. If you sign in with Google or GitHub, we receive the account identifiers, email, and profile details those providers share with us.
- Workspace and usage. Agent runs (including whether they ran locally or in the cloud), token usage, plan and limits, servers you belong to, invites you create or accept, and similar product activity needed to operate Haze and show your dashboard.
- Content you put in Haze. Prompts, files, code, canvas documents, messages, and other material you create or connect (for example a GitHub repository). We process this so agents and the workspace can function.
- Billing. Plan, checkout status, and customer identifiers. Payment cards are handled by Polar. We do not receive or store full card numbers.
- Device and logs. IP address, browser or app version, pages requested, and error logs. The website session lives in your browser’s local storage (not a tracking cookie we set).
- Optional diagnostics. The desktop app has an opt-in “anonymized diagnostics” setting for crashes and unhandled errors. Nothing is sent off your machine until a reporter ships with signed builds. The default is off.
API keys you bring yourself (BYOK) are stored on your device, not on Haze’s servers. Requests that use those keys go from your device to the provider you configured.
We do not sell your personal information.
3. How we use information
We use the information above to:
- Create and authenticate your account, including Google and GitHub sign-in and email verification codes.
- Provide the workspace, agents, profiles, invites, and billing.
- Measure usage against your plan and prevent abuse.
- Communicate with you about the product, security, and (if you write to us) support.
- Secure the service, debug issues, and comply with law.
- Improve Haze, including with aggregated or de-identified data.
We do not use your private workspace content to train a public model. If that ever changes, we will update this policy and give you a way to opt out before it applies to you.
4. How we share information
We share information only as needed to run Haze:
- Model providers — when you use Haze-hosted inference, we send the prompt and related context required to complete the request. Their use of that data is governed by their policies and our agreement with them.
- Polar — email and the identifiers needed to start checkout, open the customer portal, and keep your plan in sync.
- Google and GitHub — only to complete sign-in (and GitHub, if you connect a repository, to access what you authorize).
- Infrastructure — hosting and delivery providers such as Cloudflare, which process requests in order to serve the site and API.
- Other Haze users — what you choose to make public (see below) or share in a server.
- Legal and safety — if required by law, to protect people or the service, or in connection with a merger or sale of Haze AI, with notice where the law requires it.
We do not share your information with advertisers for their own marketing.
5. Public profiles
If you claim a handle, your public profile at usehaze.ai/@yourname can show your name, handle, avatar, bio, company, website, and activity such as token usage, agent counts, and streaks. Anyone with the link can see it. You can change profile fields from the dashboard. To unpublish or delete a profile, email sam@usehaze.ai.
6. AI processing
Local agents run on your computer. Cloud agents run on our infrastructure. In both cases, completing a task may require sending Your Content to a model provider. Do not put secrets in prompts if you are not comfortable with that path.
Outputs are generated by models and may include material derived from their training data. That does not make Haze AI a source of personal data about other people that you did not provide.
7. Cookies and local storage
Haze’s own auth and dashboard pages store a session in your browser’s local storage so you stay signed in. We do not use that session for cross-site advertising. You can clear storage and cookies in your browser; you will need to sign in again.
8. Retention
We keep account and billing records for as long as your account is open and for a reasonable period afterward (for example to resolve a billing issue or dispute, or meet tax and legal duties). Usage metrics and logs are kept only as long as needed to operate and secure the service. If you ask us to delete your account, we will delete or de-identify personal data we control, except where we must keep a limited record (such as a transaction or a ban).
Content that lives only on your device (including BYOK keys and local project files) is yours to delete by uninstalling the app or clearing local data.
9. Security
We use HTTPS, hashed passwords, same-origin API access on usehaze.ai, and access controls on the API. No method of transmission or storage is perfectly secure. If we learn of a breach that affects you, we will notify you as required by law.
10. Your rights
Depending on where you live (including the EEA, UK, and California), you may have the right to access, correct, delete, or export your personal information, to object to or restrict certain processing, and to appeal a denial. You can:
- Edit your public profile from the dashboard.
- Manage billing through the Polar customer portal.
- Sign out and clear local storage in your browser.
- Email sam@usehaze.ai to access, correct, or delete your account, or to ask a privacy question. We will need enough information to verify it is you.
If we process data as a “controller,” our legal bases include performing our contract with you (providing Haze), legitimate interests (security, product improvement, preventing abuse), consent where we ask for it (such as optional diagnostics), and legal obligation.
You may lodge a complaint with your local data-protection authority. We would rather hear from you first at sam@usehaze.ai.
11. Children
Haze is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe we have, email sam@usehaze.ai and we will delete it.
12. International transfers
Haze is operated from the United States. If you use Haze from another country, your information may be processed in the United States and in the countries where our providers run (for example Cloudflare’s network). Those places may have different data-protection laws than your own.
13. Changes
We may update this policy. The “Effective” date at the top will change. For material changes we will try to give notice (for example by email or an in-product notice). Continued use after the new policy takes effect means you accept it.
14. Contact
Haze AI
Privacy and legal requests: sam@usehaze.ai
Web: https://usehaze.ai