HeyJugi Privacy Policy

Effective date: August 29, 2026

Information we collect

HeyJugi may collect account information, settings, chats, memories you choose to save, goals, reminders, projects, creation requests, and information about paired devices.

Automatic device information

When a HeyJugi device app is installed or paired, it may automatically report non-secret technical information needed to operate the connection, including device name, operating system and version, architecture, CPU information, memory size, disk size, HeyJugi app version, supported capabilities, connection status, and recent connection time.

Device permissions and monitoring

Pairing a device does not provide unrestricted access. Device control and monitoring features require device-specific consent. Users choose which scopes are enabled, including device health/status, app control, browser control, approved-folder file access, clipboard access, screenshots, maintenance, and notifications. Permissions can be changed or revoked later.

Files, screenshots, clipboard, and local actions

HeyJugi should process files, screenshots, clipboard contents, and local controls only when the relevant device permission is enabled and the user requests or enables the supported feature. File access should remain scoped to approved locations rather than unrestricted disk access.

Connected services

If a user connects email, calendar, music, cloud storage, or other third-party services, HeyJugi may process information from those services only as needed to provide the requested integration and according to the permissions granted through that provider.

AI processing

Relevant portions of requests and context may be processed by AI model providers used by HeyJugi. As providers and integrations are added, HeyJugi should disclose applicable providers and controls in product settings or supporting documentation.

How information is used

Information may be used to operate and personalize HeyJugi, maintain device connections, perform requested actions, provide reminders and notifications, troubleshoot failures, improve reliability, detect abuse, and protect accounts and the service.

Security

HeyJugi uses account authentication, per-device credentials, hashed device tokens on the server, scoped permissions, confirmations for sensitive actions, audit logging, and signed-update mechanisms where supported. No system can guarantee absolute security.

Retention and deletion

Information may be retained while an account is active or as reasonably necessary to provide the service, meet legal obligations, prevent abuse, resolve disputes, and maintain backups. Supported data and device connections should be removable or revocable through product controls.

Sharing

HeyJugi may share information with service providers that help operate the service, when required by law, to protect users or the service, or as part of a business transaction subject to applicable law. HeyJugi does not need to sell personal information to operate its core service.

User choices

Users can change memory and notification settings, disconnect connected services, edit per-device permissions, and revoke a paired device.

Policy changes

This policy may change as HeyJugi adds features. Material changes should be communicated through the service and the effective date updated.

Contact

Before public launch, replace this section with the legal business name, privacy/support email, and mailing address that will handle privacy requests.

Account recovery and two-factor verification

HeyJugi may process account-recovery requests and optional two-factor verification information. Password-reset links are time-limited and single-use. The service stores a protected hash of each reset token rather than the usable token itself. Authenticator secrets are encrypted at rest, and recovery codes are stored as protected hashes. HeyJugi should never request an authenticator secret or recovery code by email.

Professional onboarding preferences

During optional onboarding, HeyJugi may ask how the account will be used, the kinds of work or learning the user wants help with, preferred response detail, experience level, and an optional near-term outcome. The onboarding flow is not intended to request salary, employer name, age, health, political views, or other sensitive personal information. Users can skip onboarding, change these answers, or disable their use for personalization.

Authentication security records

HeyJugi may keep limited security records such as authentication event type, time, success or failure, and protected hashes derived from network or browser information. These records may be used to prevent abuse, investigate account-security problems, and invalidate older sessions after password or security changes.

Product draft: this policy should be reviewed by qualified legal counsel before HeyJugi is offered broadly to the public.