Privacy Policy

Who is responsible for what

For this website and for your HypAware Cloud account details, Hyperparam decides how the data is used. In legal terms we are the controller.

For the AI sessions your organization syncs to HypAware Cloud, your organization decides what is recorded and shared, and we process it for them. In legal terms they are the controller and we are their processor. Our Data Processing Addendum covers that processing. If your sessions were synced through your employer’s organization, ask them first about access or deletion.

What this website collects

We use PostHog (US Cloud) for site analytics. Requests go through our own domain and are forwarded to PostHog. The PostHog script loads with the page. Where consent is required, we show a banner before setting analytics cookies or recording sessions. We determine this from the country of your connection. If your country cannot be determined, we show the banner.

Where consent is required, before you choose, and if you choose Decline, PostHog runs without cookies, without browser storage, and without session replay. Page views and the events listed below are still sent to PostHog. Decline means no cookies and no replay. It does not mean no analytics.

Outside those regions, PostHog uses a cookie and browser storage and records sessions by default. In any region, choosing Accept enables those features. Replay masks everything typed into form fields. It does not mask page text.

What is sent: page views, plus seven named events: install command copied, outbound link clicked, sign-in clicked, contact form submitted (the form name only, never the fields), pricing viewed, docs viewed, and section viewed. We do not attach your name or email to analytics.

PostHog receives your IP address with each event and uses it to estimate your country and city. We have not turned on PostHog’s option to discard it.

The contact forms collect your name, email, company, and message. The sales form also asks for company size. With each submission we also send which form you used, the full address of the page you were on (including anything after the question mark, such as campaign tags), and the time. Submissions go to Clarify, our CRM. A hidden field catches spam bots; if it is filled in, nothing is sent.

Pages load fonts from Google Fonts. Your browser requests them from Google directly, so Google receives your IP address and browser user agent on each page load.

The site is static files on Amazon S3 behind Amazon CloudFront in the United States (us-east-1). CloudFront receives your IP address to serve the page.

Cookies and browser storage on this site

You can change your choice at any time with the Cookie settings link in the footer of every page.

PostHog keeps session replays for 30 days. Analytics events have no expiry set in PostHog; we keep them until we delete them. Contact form submissions stay in Clarify until we delete them.

The HypAware CLI on your machine

The CLI records AI activity from the capture sources you turn on during setup: Claude Code, Claude Desktop, Codex, Cursor, OpenCode, OpenClaw, Hermes, raw Anthropic and OpenAI API traffic routed through the local gateway, and OpenTelemetry logs, traces, and metrics. Recording is content-level. A recorded session can include:

• Prompts, responses, and system prompts
• The tool list, tool calls with their arguments, and tool results. Tool results can contain file contents, command output, and anything else the agent read
• Model, client version, timestamps, and token and cost figures where the client reports them
• The working directory and repository root as absolute paths, which usually include your OS user name
• The git remote URL (credentials in the URL are stripped), branch, and commit SHA
• Your AI provider account identifier: the Anthropic account UUID or the OpenAI user field
• Request and response headers for each exchange, with authorization, API key, cookie, and account ID headers redacted

Environment variables are not recorded as a field. Anything that appears inside a conversation is recorded as part of it, so recordings may contain personal, confidential, or secret information. On AI providers HypAware does not fully support, it may record less than the full session, never more.

Recordings are stored in a local cache under ~/.hyp. Rows age out after 120 days on a machine that is not connected to an organization, and after 90 days on one that is. You can change the window.

A machine that is not connected to an organization does not send your recordings anywhere. The HypAware daemon still makes two kinds of outbound connection. When installed globally through npm, it checks the npm registry about once a day for a new version of the hypaware package and, by default, installs it. That is a version check, not an upload; the registry sees your IP address and a user agent. Setting auto_update to false turns it off. When you route an AI client through the local gateway, the daemon forwards that client’s traffic to the AI provider it was already going to. There is no crash reporting, and there is no usage telemetry on a machine that is not connected to an organization.

In proxy mode, all of the AI client’s HTTPS traffic passes through the local gateway. Only AI provider hosts (api.anthropic.com, api.openai.com, chatgpt.com) are decrypted, using a certificate authority generated on your machine and limited to those hosts. Everything else is tunnelled without being decrypted: the gateway sees the hostname and byte counts and does not record them. The Security page has the details.

When you connect a machine to an organization

Running hyp remote login or hyp join, or choosing the managed option during setup, connects the machine to HypAware Cloud, operated by Hyperparam. From then on recorded rows are sent to our server, including conversation content and every field listed above. hyp remote login also sends the machine’s hostname as a label.

Defaults to know about. Every folder syncs unless you mark it otherwise. History already on the machine is imported and synced too, back as far as the local retention window. A browser sign-in that enrolls a machine for the first time holds the first sync until the end of the day (or the end of the next day, if fewer than four hours remain) so you can review what will be sent. hyp join and token sign-ins have no hold and show no notice.

Your controls

• Mark a folder ignore (never recorded), local-only (recorded, never synced), or sync, with a committed .hypignore file or the hyp privacy commands
• Be asked once per new folder instead of syncing by default: hyp privacy folders ask
• Keep one conversation out of the record: hyp session ignore. Not available for OpenClaw and Hermes sessions
• Delete local recordings: hyp privacy purge. This never deletes copies already synced
• Disconnect: hyp leave. This stops syncing. It does not delete anything on the server
• Folder markings do not apply to raw API traffic or OpenTelemetry data, because those sources carry no working directory

The hypaware-privacy review skill samples your local recordings to look for secrets and personal material. It runs inside your coding agent, so the excerpts it samples are sent to that agent’s model provider like any other turn. It masks credential values in what it reports back.

A connected machine reports product telemetry to our server: command names, outcomes, durations, error codes, adapter names, OS type, CPU architecture, Node major version, and HypAware version. It never includes prompts, responses, paths, or command arguments. hyp telemetry off turns it off. On the server, telemetry is kept for 30 days.

HypAware Cloud

Synced data is stored on a single server we operate in Amazon Web Services in the United States (Oregon, us-west-2), behind Amazon CloudFront. Everything for your organization, including recorded sessions, search indexes, reports, and report generation transcripts, lives on that server’s data volume, separated from other organizations by partition. Daily snapshots of the volume are kept for 14 days.

Inside your organization, visibility is uniform. Every member can list, search, and read every other member’s synced sessions in full, including prompts, tool arguments, tool results, and working directory paths. Every member can read every published report. Admins can also see the member roster, including emails, last sign-in times, and machine names, and can add and remove members and manage access tokens.

Hyperparam operators can read any organization’s data: sessions, search, reports, report drafts, member rosters, and machine lists. Operator standing is limited to named staff, granted and removed by hand. Today operators use it to review generated reports before they are published, for support you ask for, and for security and keeping the service running. We do not read your session logs outside those purposes, and we do not copy customer data off the server to laptops, personal AI accounts, or test environments. Operator reads through query and search are written to an audit trail for the organization concerned. Operator views of reports and report drafts are not audited, and neither are listing views. The audit trail is not visible to your organization today. Staff with access to the server itself can read data without leaving an audit record.

Reports are generated on our server using Anthropic’s API under Anthropic’s standard commercial terms, through Hyperparam’s own account. To write a report, the model runs queries over your organization’s synced sessions, and the results are sent to Anthropic as they are stored: prompts, responses, tool arguments, paths, git remotes, and account identifiers can all be included. Nothing is redacted first. Requests use a prompt cache that Anthropic holds for one hour. Anthropic’s commercial terms exclude training on API inputs and outputs. Report generation can run on a schedule without a person starting it.

A generated report starts as a draft that only Hyperparam operators can see. An operator reviews it in the dashboard, may edit it, and publishes it to your organization. Reports can quote session text word for word. We keep the full transcript of each generation run (the instructions, the model’s output, and the query results it saw) with your organization’s data. Operators can read those transcripts. Members cannot.

If GitHub data is collected for your organization, it arrives in one of two ways. A member’s CLI can sync GitHub activity it observed using that member’s own token, and that activity becomes visible to every member. A Hyperparam operator can also run a backfill for configured repositories using a token held on our server. The backfill pulls issues, pull requests, reviews, commits, changed file paths, and actor logins. It does not store titles or bodies.

You sign in with Google. For your account we hold your verified email, the identifier Google gives us, your organization and role, sign-in times, active sessions, the machines you connected (ID and hostname label), and a record of the terms version you accepted and when. We do not store passwords, your name, IP addresses, or browser user agents. Server logs do record the email address of a sign-in that was refused, along with organization names and session IDs. Logs never contain session content or query text.

The dashboard sets a sign-in cookie (HttpOnly, Secure, SameSite=Lax) that lasts up to 90 days and expires after 30 days without use. Two short-lived cookies are used during sign-in and onboarding. The dashboard keeps one local storage entry that remembers which reports you have seen. Its name contains your organization name and your user identifier, its value is a timestamp, and it is not removed when you sign out. The dashboard loads no analytics, no third-party scripts, and no third-party fonts.

Retention and deletion

Synced sessions, reports, audit records, and report generation transcripts are kept until deleted. Data already sent to Anthropic to generate a report is held by Anthropic under its own retention terms and is not covered by our deletion. Removing a member revokes their access and does not delete the sessions they synced. hyp leave and hyp privacy purge do not delete anything on the server.

There is no self-service way today to delete synced sessions or an organization’s data. Deletion is done by hand by Hyperparam on request, or when your organization leaves. We delete within 30 days of the request, and backup snapshots expire 14 days after that. To ask for deletion, write to legal@hyperparam.app. Published reports can also be deleted by an operator on request.

You can pull your organization’s data out through the query interface (up to 10,000 rows per call) and download your reports. There is no one-step bulk export today.

How we use data

We use synced data to provide the service to your organization: session search, usage analysis, reports, and administration. We use site analytics, product telemetry, and information about how the product is used, with your content removed, to improve product performance and customer experience.

We do not use your session content to train models. We do not sell personal information, and we do not share it for advertising.

We do not publish findings from your reports, with or without your name, unless you approve it.

Who we share data with

We share data with the service providers on our Subprocessors page, each for the purpose listed there. We give organization admins 30 days’ notice before adding a provider that handles synced data. We may disclose data when the law requires it, and we would transfer it as part of a merger or sale of the business, under this policy’s terms.

Your rights

Depending on where you live, you may have the right to access, correct, delete, or receive a copy of your personal data, and to object to or limit how it is used. For website and account data, write to legal@hyperparam.app. For sessions synced through an organization, ask that organization. We will help them respond.

We do not discriminate against anyone for using these rights. If you are in the EU or UK, you can also complain to your data protection authority.

We are based in the United States, and data is processed in the United States.

HypAware is a tool for professional software teams. It is not directed at children, and we do not knowingly collect data from anyone under 16.

Contact

Hyperparam Corporation. Privacy and legal requests: legal@hyperparam.app.

We will post changes here with a new date. If a change affects how synced data is handled, we will tell organization admins before it takes effect.

Updated October 1, 2026.