Privacy Policy

1. Local Execution & Data Isolation

The Jarqon connector executes commands exclusively on your local machine. The contents of your files, source code, and internal directories are never proactively uploaded, scraped, or indexed by our servers. The only data transmitted is the explicit input and output of the terminal sessions necessary to fulfill an agent prompt.

2. Account and Session Information

To provide the service, we collect basic account information (such as email, authentication tokens, and billing details). The text of your prompts, AI responses, and terminal output are stored securely in our database to provide session history and context windows across your devices.

3. Third-Party AI Models

Jarqon utilizes third-party LLM providers (e.g., Groq, OpenRouter) to process your text prompts and command logs. We only send the minimum context necessary to these providers. While these providers have data retention endpoints, we enforce non-training agreements where possible.

4. Telemetry and Analytics

Our application and control plane collect anonymous, aggregated telemetry regarding execution times, connection stability, state errors, and infrastructure health to help us prioritize debugging efforts. Personal identifiers are stripped from this stream.

5. macOS Permissions & File Access

The Jarqon connector runs as a background service under your user account. It executes only the commands you approve through the mobile app. To search and navigate your filesystem without interruption, the connector benefits from Full Disk Access — a macOS permission you grant explicitly in System Settings.

• Why it's needed: Without Full Disk Access, macOS displays a permission popup every time the agent accesses folders like Desktop or Documents, requiring you to physically tap “Allow” on your Mac — defeating the purpose of remote control.
• What it enables: Read-only operations (listing files, searching, reading code) run silently without popups. Write operations (creating, deleting, modifying files) still require your explicit approval from the mobile app.
• What it does NOT do: Full Disk Access does not grant network access, does not send your files to our servers, and does not allow the connector to act without your approval on write operations.
• Revoking: You can revoke Full Disk Access at any time in System Settings > Privacy & Security > Full Disk Access. The connector will continue to work but may trigger permission popups for certain directories.

6. Deletion & Off-boarding

You may request a complete deletion of your account at any time from the Jarqon mobile app or by contacting support. When you remove a connector through the app (Settings → Remove Connector), our backend sends a remote uninstall command that:

• Unloads and removes the macOS LaunchAgent (sh.jarqon.connector.plist)
• Stops all running Jarqon connector processes
• Revokes the connector token on our servers
• Deletes the entire ~/.jarqon directory from your machine, including credentials, configuration, and cached data
• Removes all temporary log files

You may also uninstall manually by running ~/.jarqon/bin/jarqon-connector-uninstall.sh on your machine. After removal, no further communication can occur between our servers and your device.