Orqara
OrqaraUpdated 8 October 2026

Support

Use the contact routes below for Arc setup, account access, Early Access, Browser Bridge, provider connectivity, billing questions, feedback, and security reports.

Product support

For setup problems, Arc behaviour, Arc MCP, Browser Bridge, provider connections, updates, downloads, or compatibility questions, email support@orqara.com.

Include the Arc version, macOS version, provider or browser involved, what you expected to happen, and what actually happened. Screenshots are helpful when they do not expose private data.

Early Access and reviewer access

Arc is currently distributed through controlled Early Access. If you have an invitation, entitlement, download, lease, or reviewer-access problem, contact support@orqara.com from the email address associated with the request.

Chrome Web Store or other platform reviewers who need companion-app access can request a reviewer invitation through support@orqara.com. Please identify the platform and item under review so the request can be handled correctly.

Account and sign-in help

For Orqara account sign-in, identity, session, invitation, or device-access problems, contact support@orqara.com. Do not send passwords, one-time codes, recovery codes, private keys, or complete OAuth tokens.

Where the issue belongs to a third-party identity provider such as Google or GitHub, Orqara may direct you to that provider's account-recovery or security process.

Browser Bridge support

  • Confirm Arc is installed and running on the same Mac.
  • Confirm Arc Browser Bridge was installed from the Chrome Web Store through Arc → Settings → Setup, and that the extension is enabled in your Chromium browser. Reload provider tabs after installation.
  • Confirm the affected tab is on a supported provider site.
  • Include the browser name and extension version when reporting a connection problem.
  • Do not send complete AI conversation contents unless support specifically asks for a narrowly scoped example and you are comfortable sharing it.

Diagnostics and private data

Arc includes diagnostics intended to help identify setup and connection failures without requiring broad access to your local projects. Before sending logs or screenshots, review them for repository content, API keys, tokens, credentials, customer information, or other secrets.

Support may ask for a limited diagnostic excerpt, version number, connector state, or reproduction steps. Orqara will not ask you to disclose a password or private key.

Security reports

Potential vulnerabilities should be sent to security@orqara.com rather than the general support inbox. The responsible-disclosure policy and security.txt file are available from the Security page.

  • Security policy: orqara.com/security
  • security.txt: orqara.com/.well-known/security.txt

Privacy and legal enquiries

Orqara — operated by Matthew Banham. Trading correspondence address: 7 Willes Close, Faringdon, Oxon, SN7 7DU, UK. Privacy requests and questions about personal data should go to privacy@orqara.com. Legal notices and questions about the Terms should go to legal@orqara.com.

Feedback

Product feedback and feature suggestions can be sent to feedback@orqara.com. Please describe the problem you are trying to solve rather than sending confidential source code or private customer data.

Billing and commercial enquiries

Billing questions can be sent to billing@orqara.com. Commercial or purchasing enquiries can be sent to sales@orqara.com. Where a paid plan is available, the applicable purchase terms and billing details will be shown before payment.

Response expectations

Orqara aims to respond to ordinary support requests within five business days and to credible security reports within five business days. Complex technical issues, provider outages, or Early Access investigations may take longer.

These response targets are goals rather than contractual service levels unless a separate written agreement says otherwise.

Third-party services

Arc integrates with products operated by third parties. Orqara can help diagnose the Arc side of an integration, but cannot control a provider's account status, service availability, browser behaviour, API limits, or policy decisions.