Orqara
OrqaraUpdated 16 October 2026

Privacy Policy

This policy explains how Orqara handles information across orqara.com, Orqara accounts and cloud services, Arc for macOS, Arc MCP, and Arc Browser Bridge. Arc is designed around a local-first boundary: local workspace permissions and machine actions remain under the authority of software running on your Mac.

Scope and contact

Orqara — operated by Matthew Banham. The operator responsible for personal data processed directly by Orqara is Matthew Banham, trading as Orqara. Trading correspondence address: 7 Willes Close, Faringdon, Oxon, SN7 7DU, UK.

This policy applies to Orqara-operated websites, account and cloud services, Arc software distributed by Orqara, and Arc Browser Bridge. Third-party AI providers, identity providers, app stores, and other external services operate under their own privacy policies.

Questions, access requests, deletion requests, or other privacy enquiries can be sent to privacy@orqara.com.

Information you provide

  • Account information such as your email address, basic profile information, authentication method, and account-security metadata.
  • Support, feedback, legal, security, or other communications you choose to send to Orqara.
  • Information you submit when requesting Early Access, including your name, email address, optional AI subscription plans and use-case notes, or when managing an entitlement or using account and device-management features.
  • Payment and billing information if paid services are offered. Payment-card data, when applicable, is intended to be handled by the relevant payment provider rather than stored directly by Orqara.

Website and account services

Orqara uses Cloudflare to deliver and protect its websites and cloud endpoints. Cloudflare may process ordinary network and security data such as IP address, request headers, TLS/HTTP metadata, timestamps, and abuse or security events.

Orqara account authentication is provided through Clerk. Clerk processes identity, session, authentication, recovery, and security information required to operate sign-in. If you choose a social sign-in method, Google or GitHub may also process authentication information under their own terms.

  • Orqara does not use the public marketing site for behavioural advertising.
  • Orqara does not sell personal data.
  • Essential cookies or equivalent storage may be used for authentication, security, and service operation.

Arc and Arc MCP on your Mac

Arc MCP is the local authority for workspace access and machine actions. Workspace configuration, local permission decisions, local secrets, repository contents, command output, and other local project data are not uploaded to Orqara merely because Arc is installed.

When you explicitly use a remote provider or Orqara-managed connection, data necessary to perform that request may pass between the selected provider, Orqara-operated transport, and your Mac. Local permissions are still enforced by Arc MCP on the Mac.

  • Workspaces must be explicitly authorized locally.
  • Read, write, Git, task, and broader machine permissions remain locally scoped.
  • Account, connector, or relay state cannot silently increase local workspace permissions.

Orqara Cloud and managed connections

Where you use Orqara-managed account, device, entitlement, OAuth, connector, or relay features, Orqara processes the minimum state reasonably required to authenticate the device, route the selected connection, keep it alive, revoke it, secure it, and operate the service.

Managed relay infrastructure necessarily processes request and response bytes in transit so that a supported remote provider can reach the Arc MCP endpoint on your Mac. Routine service logging is designed around operational and security metadata rather than retaining MCP request and response bodies as a general-purpose activity log.

  • Account and opaque customer identifiers.
  • Device identifiers, device public keys, and device-registration state.
  • Provider, surface, connector, authorization, and revocation state.
  • OAuth grants or tokens when required for a provider connection.
  • Entitlement, liveness, rate-limit, routing, and security metadata.
  • Arc app version, internal build number, and last checked time for each registered device. This is used for compatibility, rollout monitoring, and support.
  • Version and cryptographic digest of the Terms accepted, acceptance date/time, account and device identifiers, and the app version/build used at acceptance. This is evidence of agreement, not marketing consent.

Arc Browser Bridge

Arc Browser Bridge is an optional Chrome/Chromium extension used only on supported AI-provider pages to connect those browser sessions to Arc on the same Mac. Its current supported host permissions are limited to chatgpt.com, claude.ai, and gemini.google.com. It does not run on unrelated websites.

Browser Bridge communicates with Arc through Chrome Native Messaging. Browser-session information handled by the extension is used for exact conversation identification and routing, browser-session status, and user-controlled Browser-mode automation. Browser Bridge does not send your AI conversation contents to Orqara-hosted services.

The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Browser Bridge data is not sold, used for advertising, used to determine creditworthiness, or used for unrelated purposes.

  • Supported-provider URL and conversation identifier, with query strings and fragments removed where Arc stores a canonical conversation URL.
  • Visible tab title and whether the supported provider tab is active or focused.
  • Coarse page state such as whether the supported provider appears to be generating a response.
  • Limited visible page information used to identify supported Arc workflow state.
  • Composer state needed to avoid overwriting an existing draft and to verify Arc's own fixed wake notification before an optional browser-side send requested by Arc.
  • A Claude authentication callback may be forwarded locally to Arc when required to complete a user-initiated Claude connection flow.

How information is used

  • Provide, operate, secure, troubleshoot, and improve Orqara and Arc services.
  • Authenticate accounts and devices and enforce entitlements or revocations.
  • Route provider connections selected by the user.
  • Deliver software, release metadata, service notices, and support.
  • Investigate abuse, fraud, security incidents, or violations of applicable terms.
  • Comply with legal obligations and protect users, Orqara, and third parties.

Sharing and service providers

Orqara shares information only when needed to provide the service you request, operate infrastructure, protect the service, comply with law, or complete a corporate transaction subject to applicable requirements. Orqara does not sell personal data or share it with advertising data brokers.

  • Cloudflare for website delivery, network protection, Workers, and related infrastructure.
  • Clerk for account authentication and session management.
  • Google or GitHub when you choose those identity providers.
  • OpenAI, Anthropic, Google, or another provider when you explicitly connect or use that provider.
  • Professional advisers, authorities, or other recipients where reasonably necessary for legal, security, or compliance purposes.

Retention

Orqara keeps information only for as long as reasonably necessary for the purpose for which it was collected, to operate and secure the service, to resolve disputes, or to meet legal obligations. Retention periods vary by data type and feature.

Account, entitlement, device, authorization, and security records may remain while an account or device is active and for a reasonable period afterward. Terms acceptance records may be retained as needed to evidence the contract and resolve disputes, subject to applicable retention and deletion rights. Transient relay traffic is not intended to become a retained archive of your MCP activity. Support correspondence may be retained while the issue is active and afterward where needed for continuity, security, or legal records.

Security

Orqara uses technical and organisational measures appropriate to the services being provided, including encrypted network transport for hosted services, scoped credentials, device and connector authentication, signed software distribution, and local permission boundaries. No system can guarantee absolute security.

Please report suspected vulnerabilities to security@orqara.com rather than including sensitive exploit details in general support messages.

International processing

Orqara and its service providers may process information in countries other than the country where you live. Where applicable law requires safeguards for international transfers, Orqara relies on the mechanisms available to the relevant provider or otherwise required by law.

Your choices and rights

Depending on where you live, you may have rights to request access to, correction of, deletion of, restriction of, or portability of personal data, or to object to certain processing. You may also be able to withdraw consent where processing relies on consent.

You can disconnect providers, revoke supported connections, remove local workspaces, or stop using Arc Browser Bridge at any time. For account-level privacy requests, email privacy@orqara.com. Orqara may need to verify your identity before acting on a request.

Children

Orqara products are intended for users who are legally able to use developer and AI-provider services in their jurisdiction. They are not directed to young children. If you believe a child has provided personal information to Orqara inappropriately, contact privacy@orqara.com.

Changes to this policy

Orqara may update this policy as the product, service providers, legal requirements, or data practices change. Material changes will be reflected by updating the date on this page and, where appropriate, by providing an additional notice through the relevant service.