Security
Orqara welcomes responsible reports about vulnerabilities affecting Orqara-operated services, Arc for macOS, Arc MCP, Arc Browser Bridge, or official Orqara release infrastructure.
Report a vulnerability
Send security reports privately to security@orqara.com. Please provide enough information to reproduce and understand the issue without including unrelated personal data, credentials, private keys, or customer content.
For urgent issues that could materially affect users, clearly mark the message as urgent and describe the likely impact and any known exploitation.
- Affected product, service, hostname, version, or component.
- A concise description of the vulnerability and expected security impact.
- Steps to reproduce, including any required configuration or preconditions.
- Proof-of-concept material where needed to demonstrate the issue safely.
- Whether you believe the issue is being actively exploited.
Response process
Orqara aims to acknowledge credible security reports within five business days. Complex issues may require additional time to reproduce, assess, coordinate, and remediate.
Where practical, Orqara will keep the reporter informed of material progress and will coordinate disclosure timing once a fix or mitigation is available. Response targets are goals rather than contractual service levels.
In scope
- orqara.com and Orqara-operated account, control-plane, relay, MCP-edge, release, and related production infrastructure.
- Official Arc for macOS builds distributed by Orqara.
- Arc MCP and Orqara-provided native helper processes.
- Arc Browser Bridge as distributed by Orqara through an official browser-extension channel.
- Authentication, authorization, entitlement, device identity, revocation, connector isolation, and workspace-boundary failures in Orqara-operated components.
Out of scope
- Vulnerabilities that exist only in third-party services, AI providers, browsers, operating systems, or libraries and do not arise from Orqara's integration.
- Social engineering, phishing, physical attacks, credential stuffing, or attacks against Orqara personnel or users.
- Denial-of-service, load testing, destructive testing, or activity that degrades service for other users.
- Reports based only on automated scanner output without a reproducible security impact.
- Issues requiring a compromised device, account, or provider session unless the report demonstrates a meaningful failure of an Orqara security boundary.
Research guidelines
- Use only accounts, devices, workspaces, and data you own or are explicitly authorized to test.
- Use the minimum access needed to demonstrate the issue and stop if you encounter data belonging to another user.
- Do not persist, download, alter, or disclose data that is not necessary to demonstrate the vulnerability.
- Do not leave backdoors, persistent access, or modified production data after testing.
- Give Orqara a reasonable opportunity to investigate and remediate before public disclosure.
Good-faith research
Orqara does not intend to pursue or recommend legal action against security researchers for good-faith research conducted consistently with this policy. This does not authorize unlawful activity, testing of systems you do not have permission to test, or activity that materially harms users or service availability.
A vulnerability report does not create an entitlement to payment. Orqara does not currently operate a standing bug-bounty programme unless a reward has been expressly agreed in writing.
Security architecture
Arc is designed around explicit local workspace authorization and least-privilege provider connectivity. Arc MCP remains the final local authority for workspace and machine permissions even when a provider reaches the Mac through an Orqara-managed remote connection.
- Official macOS releases use Apple Developer ID signing, hardened runtime, notarization, and Gatekeeper-compatible distribution.
- Hosted services use encrypted network transport and scoped authentication appropriate to the service.
- Device and connector identities are separated so one provider or connector cannot silently inherit another connector's authority.
- Browser Bridge uses Chrome Native Messaging to communicate with the local Arc app and is scoped to the supported provider sites declared in its manifest.
- Sensitive local paths and workspace boundaries are enforced independently of cloud account or relay state.
Secrets and sensitive material
Do not send passwords, API keys, private keys, full OAuth tokens, repository secrets, or unrelated customer information in a security report. If sensitive material is genuinely required to reproduce an issue, contact security@orqara.com first so an appropriate transfer method can be agreed.
Security notices
If a vulnerability materially affects users, Orqara may provide remediation guidance, require an update, revoke affected credentials or connectors, or take other protective action. Security-related updates may be distributed independently of feature releases where necessary.
Contact
Security reports: security@orqara.com. General product support: support@orqara.com. Privacy matters: privacy@orqara.com.