Orlim Privacy Policy

Orlim processes the information needed to connect services, retrieve quota and status information, summarize local coding activity, show system and window controls, save settings, and respond to support requests. The categories below distinguish local processing from information sent to the connected provider you choose.

Orlim does not collect this information into a Jambo account or central Orlim database. Credentials, logs, activity summaries, quota history, system readings, window data, and settings are processed locally unless a specific action sends information to a connected provider, a local service, the public policy website, or a support contact as described below.

Orlim uses information for the following purposes. If the purpose or the data flow materially changes, this policy will be updated before or when the change takes effect where required.

- Connecting the provider accounts and local sessions that you choose to use, including supported CLI, browser, API-key, cookie, editor, and local-service connection methods.

- Requesting and displaying current usage limits, quota windows, plan or account labels, reset times, and supported provider service-status information.

- Reading local Codex and Claude activity summaries and local Ari-Nomous status so Orlim can show coding activity, working or waiting states, completions, failures, and attention notices.

- Building the local quota history and activity views, including model, task, token, provider, and time-based summaries that the app displays on your Mac.

- Sampling system health and reading window-server information so Orlim can display metrics and perform the window-management actions you request.

- Saving your preferences, delivering local alerts or notifications that you enable, improving reliability, responding to support or privacy requests, protecting the app, and complying with legal obligations.

- Orlim does not include advertising SDKs, advertising identifiers, third-party analytics, or a routine Jambo telemetry endpoint in the current build.

Orlim does not sell your personal information and does not send local activity summaries, system metrics, window data, or Orlim settings to a Jambo-hosted application backend. Information may be made available to a third party in the following limited situations.

- A connected AI coding provider receives the authentication material and request data needed to answer the quota, usage, login, or status request that you initiate or have enabled. The provider controls its own processing, records, and privacy practices.

- A provider CLI, editor, browser, or local companion service may receive information as part of a sign-in, credential, browser, window, or local integration flow that you choose. Orlim does not control the subsequent processing by those products.

- Ari-Nomous, when present on the same Mac, can receive Orlim's local requests over the loopback interface. Those requests are not sent to Jambo's remote servers by Orlim.

- The public policy website and its hosting provider may process ordinary technical request data needed to deliver, secure, and monitor the policy page.

- A sharing action, export, support request, or other action that you start can pass selected information to the recipient you choose. That recipient controls its subsequent processing.

Information may also be disclosed when required by law, valid legal process, or an urgent need to protect the rights, safety, or security of users, Jambo.team, or the public.

Orlim does not operate a hosted account or data-processing backend for the local information described in this policy. For the limited external processing associated with the product, the relevant service providers or platform services are as follows.

- Connected AI coding providers: quota, usage, account, authentication, and service-status processing when you connect or enable a provider.

- macOS Keychain, browser storage, provider CLIs, editors, and local companion services: credential, session, browser, or local integration processing that occurs on your Mac and is controlled by the relevant product or operating system.

- Cloudflare Pages or another static hosting provider: delivery of the public Orlim privacy page and ordinary website security and request processing.

- Jambo.team support systems: handling privacy or support correspondence that you choose to send.

These services process information under their own terms and privacy notices. Changes to Orlim's external integrations or the categories of information sent to them will be reflected in this policy where required.

Orlim keeps information only for as long as it is needed for the purpose described in this policy, unless a longer period is required by law or needed to resolve a dispute or security issue. Orlim does not maintain a central copy of local app data.

Orlim removes local information when you use the applicable in-app control or delete the relevant local data, subject to normal macOS and file-system behavior.

- Turn off local activity tracking to stop scanning and remove Orlim's activity cache. This does not delete the original Codex or Claude logs that belong to those tools.

- Turn off quota history to clear Orlim's local quota-history file. You can also remove Orlim's local preferences or application-support data through macOS file-management tools when the app is not running.

- Use Orlim's account-change flow to review and remove the listed provider credential files and Keychain entries, including the Orlim-owned entry. Browser cookies and unrelated provider data must be removed through the browser or provider that owns them.

- Delete source session logs, provider accounts, browser records, or provider-side data through the relevant tool or provider. Information held by a connected provider, policy host, or support system must be deleted through that recipient and is subject to its retention rules.

Orlim does not maintain paper files containing user data. Electronic records under Orlim's control are removed using the applicable local storage, Keychain, preference, or provider deletion mechanism.

You can review and manage the information Orlim stores locally by changing or deleting settings, disabling activity tracking or quota history, clearing provider credentials through the account-change flow, disconnecting providers, and removing local application data.

You can revoke macOS permissions that Orlim no longer needs, including Full Disk Access, Keychain access, and Accessibility access, through macOS settings. You can also exercise account, access, correction, deletion, or objection rights directly with the connected provider whose service processes your information.

Because Orlim does not operate a Jambo account backend and does not retain local activity or system data on a Jambo server, Jambo.team cannot retrieve or delete those local records on your behalf. For a privacy question or complaint, contact [email protected] with enough detail to investigate; do not send API keys, cookie headers, provider tokens, or private session-log contents unless they are specifically necessary.

Orlim is a desktop utility for AI coding tools and is not directed to children under 13. It does not knowingly request personal information from children. A parent or legal representative who believes a child has provided personal information may contact [email protected].

Orlim does not set or use web cookies, advertising identifiers, or cross-service tracking identifiers in the macOS app. Its browser-cookie connection option is a user-started import of existing provider session cookies; it is not a cookie that Orlim creates for tracking.

Jambo.team uses reasonable technical and organizational measures appropriate to Orlim's local-first design and limited external data flows.

If Orlim's data practices, integrations, authentication methods, or purposes change, we will update this policy, the app's legal notice, or both, and change the effective date. For material changes, we will provide notice through the app, release documentation, public policy page, or another appropriate channel where required.

Jambo.team is responsible for operating Orlim and handling privacy questions or complaints about the service.

[Orlim privacy contact]

- Operator: Jambo.team

- Privacy email: [email protected]

When contacting us, please avoid sending API keys, cookie headers, provider tokens, private session logs, or other sensitive credentials unless we specifically request information that is necessary to resolve the issue.

This personal information processing policy comes into effect on 28 August, 2026.