Privacy Policy

Updated 27 September 2026

This policy applies to Hangar and hangar.iney.app, provided by Iney. Questions and data requests go to hello@iney.app.

Your workspace stays local

Hangar stores workspace settings, session metadata, terminal replay data and Quick Run history on your Mac. It does not upload your source code, terminal content or commands to Iney. Local terminal processes and session recovery may keep running after the app window closes.

Agent integrations

Hangar reads local Claude Code and Codex session information to show status and help resume conversations. Usage integrations can contact the corresponding provider using your existing local sign-in. Those credentials are not sent to Iney. Your shell commands and third-party AI tools may send data to services you use; their own settings, terms and privacy policies govern that activity.

Optional app diagnostics

Starting with the version after 1.0.0, Hangar reports diagnostics when it launches and periodically while it runs, so we can tell whether installations work and which features matter:

• Installation and environment: a random installation ID, Hangar and macOS versions, the Mac model identifier, and the resolution, scaling and built-in or external status of connected displays. We keep the last received configuration and a history of its changes. We do not collect hardware serial numbers or display names.
• License and setup state: whether Hangar is in its trial, with the days left, or licensed, and whether the Claude Code and Codex command-line tools were found on your Mac. Only whether each was found is reported, not where it is installed or anything about your accounts.
• Usage counts: daily counts of how many times Hangar was launched and how often its features were used. These are numbers only, never terminal content, commands, prompts, file or folder names, or window titles.
• Crash reports: if Hangar ends unexpectedly, the next launch reports the installation ID, Hangar and macOS versions, the type of crash and where in Hangar's own code it happened. We never send the crash log itself, file paths, memory contents or terminal content.

You can turn diagnostics off in Hangar Settings. Turning them off stops future reports; licensing checks described below continue because the license depends on them.

Licensing and purchases

• Email and order details: when you start checkout, we record the email, invoice reference, amount, currency, any promo code and payment status. If website measurement is enabled, the order also carries the random browser and visit IDs described below, so we can see how many visitors reach payment. Unpaid checkout attempts may also be retained for payment support.
• Payment: Lava.top processes payment and supplies the information needed to issue a license. We do not receive or store your full card number or card security code.
• Activation: we store your license email, a random device identifier, the device name supplied by the app and activation/deactivation times to enforce the three-device limit. The license token and local trial information are stored in macOS Keychain.
• License checks: Hangar contacts our licensing services to activate and restore licenses and retrieve license configuration and revocation information.

This website

The Hangar landing page has no advertising trackers and sends no data to analytics companies. Unless you turn it off below, it reports the following to our own service:

• Visits: a random browser ID, a random visit ID, approximate country supplied by our host Vercel, browser language, broad device, operating system and browser type, the referring website's hostname, approximate active time, how far down the page you scrolled, and which page of this site you came from. Active time excludes hidden tabs and periods without interaction; it is an estimate, not a recording.
• Downloads: when you click Download, the time, the Hangar version, which Download button it was and the same browser and visit IDs. This counts download requests, not completed transfers.
• Checkout: whether the checkout window was opened, once per visit. The email and promo code you enter are sent only when you apply a code or continue to payment, as described above.
• Download linking: after a download, clicking “Installed? Open Hangar” passes a one-time token to the app, which links that download with the installation that opens it. The token expires after 7 days. If that installation later activates a license, the linked download and visit history can be associated with your license email. We do not match people by IP address or fingerprint their hardware.

The browser ID is stored in your browser for up to 90 days so repeat visits can be grouped; each visit gets its own ID. We do not store the full user agent, URL query parameters, raw IP addresses or precise location in these records; the IP address is used only to derive a short-lived key that limits abuse. Do Not Track and Global Privacy Control turn this measurement off, as does the switch below. Downloads and checkout work either way.

Share optional website activity

Local storage also remembers which studio announcement you dismissed so it does not appear again. Announcements load from our shared Supabase service. Our host may process standard request metadata, such as IP address, browser type and time, to deliver the website and downloads and protect against abuse. The main page loads fonts from Google Fonts, which receives normal network request metadata when those fonts load.

Providers

We use Vercel for the website and downloads, Supabase for licensing, checkout, website activity and diagnostics records, Lava.top for payments and Resend for license email. These providers receive the information needed to operate their part of the service under their own terms and privacy policies. We do not sell your data or share it for advertising.

Retention and your rights

We retain license and purchase information while it is needed to provide your license, resolve support requests, prevent fraud and meet legal or accounting obligations. Website activity and diagnostics are kept for product measurement and support until no longer needed or you ask us to delete them. Turning measurement or diagnostics off stops future reports; it does not erase earlier records. Operational logs follow the relevant hosting provider’s retention settings. You can request access, correction, export or deletion of the personal information we hold by emailing us. Deleting license records may prevent restoring or using that license; legal retention requirements may limit deletion.

Changes

If how we handle data changes, we will update this policy and the date above.