Skip to content
HRONAUT
Product
Use cases

What you can do with Hronaut.

  • Test your local appLet your agent check localhost in a stable, visible browser.
  • Signed-in appsSign in yourself, then hand the session back to your agent.
  • Parallel agentsGive every task its own isolated browser workspace.
  • Resume after disconnectPick up the same tabs when an agent reconnects.
  • Local Web3 walletsApprove wallet requests without exposing keys.
  • Split viewCompare two live pages side by side.
All use cases →
Agents

Connect the coding agent you already use.

  • Codex
  • Claude Code
  • Cursor
  • VS Code / Copilot
  • Gemini CLI
  • OpenCode
All supported agents →
Resources

Reference, security and troubleshooting.

  • Compare browser toolsChoose the right browser ownership model.
  • MCP tool catalogEvery browser tool, grouped by task.
  • Security & release trustWhat is isolated, and how to verify a release.
  • Browser lifecycleHow tasks, connections and the browser outlive each other.
  • Connection troubleshootingWSL, containers, VMs and remote sessions.
All guides →
PricingBlogChangelog
Download
Product
Use cases
Test your local appSigned-in appsParallel agentsResume after disconnectLocal Web3 walletsSplit viewAll use cases →
Agents
CodexClaude CodeCursorVS Code / CopilotGemini CLIOpenCodeAll supported agents →
Resources
Compare browser toolsMCP tool catalogSecurity & release trustBrowser lifecycleConnection troubleshootingAll guides →
PricingBlogChangelogAll guidesGitHub
LegalPrivacyTermsRefunds

Legal

Privacy Policy

How Hronaut handles information connected with the Hronaut website, commercial checkout, licensing service, and desktop application.

Last updated: November 8, 2026

On this page
  1. Who we are
  2. Information we handle
  3. Hronaut desktop data
  4. Why we use information
  5. Service providers and disclosure
  6. Retention and security
  7. Your choices and rights
  8. International processing and children
  9. Changes

1. Who we are

Hronaut is provided by Hronaut, operated by Yevhen Tienkaiev ("Hronaut", "we", "us"). For privacy, licensing, or support questions, contact [email protected].

2. Information we handle

Website delivery and analytics

Cloudflare processes ordinary technical request information, such as IP address, browser information, requested URL, security signals, and timestamps, to deliver and protect the site. We also use Cloudflare Web Analytics to measure aggregate page views, referrers, and page-performance metrics. Cloudflare describes this service as privacy-first: its Web Analytics beacon does not use cookies, local storage, or fingerprinting to identify individual visitors. For an allowlisted campaign link under /go/, we store one aggregate entry event containing only the campaign label and event-schema version. If that landing page directly leads to a package selection, we store one additional aggregate download event containing the same approved campaign label, a download-event schema version, and the non-personal package key. We do not put an IP address, user agent, referrer, query string, cookie, browser-storage value, or visitor identifier in either campaign event. Campaign context is carried only in the current page or download-link URL and is not saved in a cookie or browser storage.

Advertising measurement

We use the X conversion pixel on this website to measure whether our ads on X lead to site visits, downloads, checkout starts, and purchases. When a page loads, your browser requests a script from X and sends X information such as the page URL, your IP address, browser details, and identifiers stored in X cookies. X may link this activity to an X account and uses it under its own Privacy Policy. We do not send X your name, email address, payment details, or license key.

Purchases and subscriptions

When commercial checkout is available, Creem acts as Merchant of Record and processes customer identity, billing, payment, tax, invoice, subscription, and license-key information. We receive identifiers and subscription events needed to provide and support the commercial license. We do not receive or store full payment card details.

License activation

When you activate Hronaut, the desktop application sends the license key and a random, non-personal installation label through our Cloudflare endpoint to Creem. Later checks send the key and Creem instance identifier. The endpoint does not return or intentionally log the key. Hronaut stores the key locally using operating-system secure storage. Our database stores opaque Creem license, subscription, product, and customer identifiers, subscription status, relevant dates, and webhook event identifiers so canceled subscriptions can be denied. It is designed not to store license keys or customer email addresses.

Support

If you contact us, we receive the information you include in your message, such as your email address, order identifier, diagnostic details, and correspondence.

3. Hronaut desktop data

Hronaut is designed around a local browser profile. Tabs, browsing history, cookies, local storage, IndexedDB, cached data, saved permissions, and other browser-profile information remain on the device where Hronaut runs unless you intentionally share, export, synchronize, or transmit information through a website or another tool. Websites you visit receive data under their own privacy practices.

4. Why we use information

  • deliver and secure the website and licensing endpoints;
  • create, validate, and administer commercial licenses and device activations;
  • process subscription events, cancellations, refunds, and support requests;
  • prevent abuse, investigate errors, and comply with legal obligations;
  • measure whether our advertising on X leads to visits, downloads, and purchases;
  • communicate material service or policy changes.

5. Service providers and disclosure

We use Cloudflare for website delivery, security, Pages Functions, and D1 storage; GitHub for source code and software releases; Creem for checkout, payments, taxes, invoices, subscriptions, and customer self-service; and X for advertising measurement. These providers process information under their own terms and privacy notices. We may also disclose information when required by law, to protect users or the service, or as part of a legitimate business transfer.

6. Retention and security

We keep information only for as long as reasonably needed for licensing, support, security, dispute handling, and legal compliance. Retention by Creem, Cloudflare, GitHub, X, and websites visited through Hronaut is controlled by those providers. We use access controls, encryption in transit, secret storage, hashing, and data minimization, but no system can guarantee absolute security.

7. Your choices and rights

You may ask us to access, correct, or delete personal information we control, or object to or restrict certain processing where applicable. Some records may need to be retained for legal, fraud-prevention, accounting, or dispute purposes. Contact [email protected]. You can limit the X pixel with your browser's tracking protection or a content blocker, and through the privacy settings of your X account. You may also manage payment and subscription data through the Creem Customer Portal.

8. International processing and children

Our providers may process information in countries other than yours and use lawful transfer safeguards where required. Hronaut and its commercial service are not directed to children, and we do not knowingly collect personal information from children.

9. Changes

We may update this policy as the product or legal requirements change. The updated date above identifies the current version. Material changes will be posted on this page.

HRONAUT

A visible desktop browser for coding agents, with a separate workspace for each project.

Local-first · Source-available

Follow Hronaut

XBlueskyYouTubeLinkedInGitHubDiscordProduct Hunt

Follow the maintainer · Hronom

XBlueskyThreadsDEVRedditHacker NewsGitHub

Product

OverviewProduct tourPricingDownloadChangelogBlogSource code

Use cases

Test your local appSigned-in appsParallel agentsResume after disconnectLocal Web3 walletsSplit view

Agents

Set up HronautCodexClaude CodeCursorVS Code / CopilotGemini CLIOpenCodeAll supported agents

Resources

Compare browser toolsMCP tool catalogSecurity & release trustBrowser lifecycleConnection troubleshootingFAQFactsAll guides

Support & legal

[email protected]Manage subscriptionGitHub IssuesDiscordPrivacyTermsRefunds

© 2026 Hronaut.

Source available under the Hronaut Subscription and Trial License.