Halofy

Legal

Halofy Privacy Policy

Halofy, operated by Hivenix Inc.

Last updated: 16 November 2026

1. Scope and responsibility

Hivenix Inc., a Delaware corporation, operates Halofy. This policy covers our website, desktop software, web services and Console, Android and iOS/iPadOS apps, Connect, Cloud and related services. Information handling depends on the features, computers and services you use.

We are responsible for our account, service, security, support and billing activities. Where we process workspace information on an organization's instructions, that organization determines its use; its privacy notice and our agreement also apply.

Contact contactus@halofy.ai, or Hivenix Inc., 2810 N Church St, STE 88490, Wilmington, DE 19802, United States, for privacy questions and requests.

2. Information and purposes

We receive information from you, your devices, connected services, and organizations or people who authorize access or share with you:

  • Account information: names, email addresses, account identifiers, sign-in records, preferences and organizational roles, used for authentication, access and communication. Sign-in services, such as Google or GitHub, provide relevant identity and profile information.
  • Content and connections: prompts, messages, responses, selected files/photos, other attachments, task context, tool inputs/results, project information and connection credentials/settings, used to perform tasks and provide conversations, integrations and sharing. Content can include sensitive information about you or others.
  • Device and network information: device/installation identifiers, computer names, system/app versions, IP addresses, pairing credentials, connection records and notification tokens, used to connect devices, deliver tasks, notifications and updates, and secure access.
  • Usage and diagnostics: feature activity, model/provider choices, outcomes, durations, usage counts and errors, used for reliability, product improvement, troubleshooting and abuse prevention. Workspace usage supports budgets and work insights.
  • Transactions: billing details, subscription/entitlement status and customer, payment and invoice records, used for paid services, renewals and financial obligations. Payment processors handle card details; we do not store full card details.
  • Support and communications: requests, feedback, surveys and reported AI responses, used to respond and investigate quality or safety issues. Reporting sends the selected response, reason and app/platform information to our review inbox; its content may identify people.

We also use relevant information to enforce agreements, protect people and systems, comply with law and handle legal claims. We may use aggregated or de-identified information for analysis and improvement without attempting re-identification.

3. Computers, AI and connected services

Tasks go to your chosen environment. Mobile prompts and selected files/photos go to the connected computer, which sends relevant content to configured AI providers such as Anthropic, OpenAI or Google. The computer may be yours, organization-provided or hosted in Halofy Cloud.

AI providers can receive conversation history, attachments, content an agent reads and tool inputs/results. Supporting features, including summaries, also process relevant context. Connected tools receive information needed for their tasks. Content therefore does not necessarily stay on your device.

Provider retention, training and other data uses vary by service, account and configuration; their terms apply. Review recipients before sending sensitive information. You can avoid sending tasks, disconnect services or remove computers, but these actions do not retrieve information already received by others.

4. Workspaces and sharing

Account sign-in supports device linking and Cloud. A signed-in computer with authorized workspace access can connect and share activity automatically, without a separate capture switch. Signing in on a phone alone does not enable host capture.

Workspaces can receive new messages, supported tool inputs/results and failures, helper-agent activity, usage and project/setup information for history, budgets and reusable work practices. Usage can include earlier activity. Capture varies by provider. Attachments are not uploaded as attachment bodies by conversation capture, but message/tool content can contain file contents; setup sharing can separately collect instruction documents, skills and settings.

Authorized organization administrators and managers can access shared records and manage rules; information may be available to your associated teams. Sign-in and workspace screens describe sharing. Signing out of the host stops future sharing, not previously received records; reconnecting can resume sharing. Contact your administrator about organization-managed access, retention or deletion.

Share links give recipients access to shared material. Revoking a link prevents further access through it, but cannot erase copies already saved.

5. Hosting, connections and security

Connect authenticates devices and relays traffic. Public Connect connections are encrypted in transit. Ordinary live content is processed while forwarded and is not end-to-end encrypted against Connect. Supported offline mailbox messages have additional end-to-end encryption to their destination computer; routing, account and delivery information remain visible. The destination decrypts content to execute tasks, including when it is a Halofy-managed Cloud PC.

Cloud stores conversations, files, application state and configured credentials on managed infrastructure, including supported backups. Own-device files remain on devices you control; hosted copies are separate. Suspending a computer or canceling its subscription does not delete files.

We use access controls, encryption where appropriate and other security measures. Local connections and configured services can differ. No system is completely secure; protect credentials and access links and report suspected unauthorized access.

6. Analytics and choices

Website cookies support sign-in, preferences and operation. Optional browser analytics follow cookie settings; restricting essential cookies can affect functionality. Separately, we may send installer-download analytics to PostHog even when optional browser analytics is declined. This download measurement uses persistent visitor identifiers, including cookies, and can link downloads to existing browser analytics profiles and sessions. It can include IP addresses, browser and device details, referring pages and campaign information. Website cookie choices do not disable this download measurement.

Desktop/host product analytics is on by default and uses PostHog in the United States. It includes an installation identifier, system/app information, provider/model choices, outcomes and usage, including historical usage. Basic analytics excludes message text, prompts, code and file bodies, although user-defined labels may contain personal information.

The computer/environment operator can disable product analytics in its configuration; contact us for instructions. This stops future collection through those exports, not previously sent data. Website cookie choices do not control host analytics. Logs and crash/error diagnostics stay local by default; configured remote diagnostics or support reports can include error details and paths.

Manage camera, photo and notification permissions in device settings. Enabled push delivery uses Apple or Google services, which receive tokens, titles and routing information. Agent-reply notifications omit reply bodies, but agent names can appear on lock screens.

Unsubscribe from promotional emails using their link or by contacting us. Essential account, security and billing communications continue.

7. Recipients

We disclose information for the purposes above to:

  • Service providers for infrastructure, storage, delivery, communications, analytics, security, payments and support. Examples include Azure for hosting/email, Vercel for web/domain services, PostHog for analytics and Stripe for applicable payments. Each receives information relevant to its service, such as hosted content, usage events or transaction records.
  • Configured services and authorized recipients: AI/sign-in providers, connected tools, workspace members/administrators and people you share with receive relevant identity, credentials, content or activity. Independent services' terms and roles can differ from Halofy's processors.
  • Legal, safety and transaction recipients: authorities, advisers or other parties where necessary for legal obligations, security, rights protection or a corporate transaction, subject to applicable safeguards and notice requirements.

We do not sell personal information or share it for cross-context behavioral advertising, including children's information. Third-party sites and services have their own privacy notices.

8. Retention, deletion and billing

Retention depends on the category and purpose:

  • Account and connection records support active accounts and access. Deletion removes or revokes associated records, with lawful exceptions.
  • Content, workspace records and shares follow the relevant host/workspace storage and deletion controls; share snapshots can remain until removed. Own-device files remain under your control.
  • Queued tasks and delivery records support delivery and outcome reconciliation. Expiry or completion does not ensure immediate physical removal; inactive queues can retain records longer than active ones.
  • Cloud content and backups persist separately from running computers. Account deletion initiates permanent cleanup, which can continue after sign-out. Recovery copies remain until backup processing removes them.
  • Analytics, diagnostics, support and reports support analysis, reliability and issue/safety review. Retention considers age, sensitivity, unresolved issues and whether less identifying information serves the purpose. Report emails can retain content separately.
  • Financial, security and legal records remain for required recordkeeping, fraud prevention, disputes and claims, including after account deletion where justified.

Use Delete account in account settings or the account deletion page. Ownership verification and Cloud-deletion confirmation may be required. Contact us for other deletion requests or assistance.

Account removal and Cloud cleanup are separate stages. Deletion does not remotely erase your own computers. Organization-controlled records require the organization's process; we assist with requests and service-provider deletion where required. Independent recipients may retain their copies under their responsibilities.

Account deletion does not automatically cancel Cloud subscriptions. Stop renewal through web/desktop Cloud subscription settings before deleting the account, or contact support. Cancellation takes effect at the applicable paid-period end and does not delete files. Mobile shows subscription status; cancellation is in web/desktop settings. Uninstalling an app does not delete remote data or stop billing.

9. International processing and legal bases

Information may be processed in the United States, India and other countries where our providers and authorized operations teams work. Privacy laws differ; contact us about applicable transfer safeguards.

Where European or UK law applies, our bases depend on the purpose: contract performance for requested services; legal duties such as financial recordkeeping; legitimate interests in security, support and improvement balanced against your rights; or consent where required, including optional analytics/marketing. Organizations determine the basis for processing we perform on their instructions.

10. Rights and requests

Depending on applicable law, you may access, correct or delete information, obtain a portable copy, restrict processing, object or withdraw consent. Withdrawal does not affect earlier lawful processing; withholding necessary information may prevent a feature working.

Email contactus@halofy.ai. We verify identity proportionately, accept authorized representatives where permitted, explain exceptions and respond within statutory periods. Organization-controlled requests can be routed to the organization.

EEA, UK and Switzerland: applicable rights include access, correction, erasure, portability, restriction, objection and consent withdrawal. You may complain to your data protection authority and invoke applicable safeguards for solely automated decisions with significant effects.

California: where CCPA/CPRA applies, you may request categories/specific information, sources, purposes and recipients; correction/deletion; sale or advertising-sharing opt-out; and limits on certain sensitive-information uses. We do not sell or share for cross-context advertising. Sensitive information supports requested services and permitted security/operational purposes. You may use an authorized agent. We do not discriminate or retaliate for exercising rights.

India and elsewhere: rights apply as relevant laws take effect. Where the relevant provisions of India’s Digital Personal Data Protection Act apply and are in force, rights include processing information, correction/erasure, grievance redressal, nomination and consent withdrawal. Contact us with grievances; applicable regulator and statutory escalation rights remain available.

11. Children

Halofy is for adults aged 18 or older. We do not knowingly collect children's personal information. Contact us if a child has supplied information so we can investigate and delete it as appropriate.

12. Changes

We revise this policy and its date as practices or requirements change, giving appropriate advance notice of material changes through website, app or account communications. Policy updates and continued use do not replace separately required consent.