Your work has a boundary.

Hara is operated by Wuxi Nanhara Technology Co., Ltd. (“Nanhara”, “we”, “us”). Questions and privacy requests can be sent to biz@nanhara.com.

• Account identity: a one-way hash derived from the phone number, email address, or Apple subject used to sign in, plus an account ID and display name. Verification destinations are sent to the selected delivery provider and are not stored as profile fields.
• Trusted devices: device label, platform, public key, key fingerprint, credential version, pairing state, and security timestamps. Hara does not receive a device private key.
• Connection metadata: opaque account, device, stream, and message IDs, delivery sequence, expiry, and encrypted payload size needed to route a mobile connection.
• Website analytics: privacy-filtered aggregate visits through our self-hosted Umami service. Search text, URL fragments, form input, account/contact data, and Do Not Track visitors are excluded.

Session history, terminal output, local paths, files, model API keys, browser credentials, and device private keys stay on your computer or phone. A Desktop must explicitly publish a Session and its permissions before Mobile can access it. Relay payloads are end-to-end encrypted; the service routes ciphertext and cannot read the message or terminal content.

When you ask a model provider or connected service to process content, that provider receives the content you chose to send under its own terms and privacy policy.

We process this limited data to authenticate you, send verification codes, pair devices you approve, route encrypted commands, restore a short interrupted connection, prevent abuse, and operate support and security. We do not sell personal data or use Session content for advertising.

Account and trusted-device records remain while your account is active. Verification codes expire after five minutes and are stored only as non-reversible hashes. Relay envelopes have a maximum lifetime of one minute and are removed after delivery, acknowledgement, or expiry. Operational logs are access-controlled and must not contain message bodies, terminal content, credentials, or authorization headers.

Hara separates mainland China and global account regions. Transport encryption, short-lived credentials, device-bound P-256 keys, explicit capability grants, and revocation checks protect remote access.

In Hara Mobile, open Settings → Account management → Delete Hara account. Confirm with a fresh code sent to a linked phone or email. If the account uses Sign in with Apple, authenticate with Apple again so Hara can revoke that authorization before deletion.

Deletion removes Hara login identities, refresh sessions, trusted devices, pairing and Desktop authorization records, and inactive membership projections, then clears Hara credentials and device keys from the phone. Active organization memberships must first be left or transferred. Files and local Session history on your computers are not deleted. If the in-app route is unavailable, contact us from the email above and include only the account region and sign-in method, never a password or verification code.

You can stop publishing a Session or revoke a paired phone from Desktop, release terminal control or sign out from Mobile, link an additional sign-in method, or delete the account. You may also request access, correction, or deletion where applicable by law. We may ask you to verify ownership before acting on a request.

We will update the date above when this policy changes materially. A change that affects account data or remote-access behavior will also be presented through the product or release notes before it takes effect.