Security at GearFive is architectural. The product is designed so that the most sensitive data — your prompts and source code — never has to be trusted to anyone, because it never leaves the device. This page describes how the Service is built and protected.
Privacy by architecture. GearFive parses AI coding-agent activity locally and syncs metadata only — model identifiers, token counts, estimated cost, and timestamps. Prompt text, completions, files, and source code are never transmitted.
Device identity
GearFive needs to attribute usage to a device, not a person. It derives a device identifier from the device's hardware, hashes it with domain separation, and re-derives it on each run. The raw hardware identifier is never persisted, logged, or transmitted, so the stored identifier cannot be reversed back to the underlying hardware.
Data in transit and at rest
- In transit: all metadata is uploaded over authenticated TLS connections.
- At rest: metadata is stored on Google Cloud / Firebase infrastructure, protected by access controls and the provider's encryption-at-rest.
- Least privilege: access to production data is restricted to what is required to operate the Service.
Application integrity
The GearFive macOS application is distributed signed with an Apple Developer ID certificate (Kelios LLC) and notarized by Apple, so macOS Gatekeeper can verify it has not been tampered with before it runs.
Privileged operations
Enforcement that must write protected system settings is handled by a separate privileged
helper registered through Apple's SMAppService. The helper communicates with the
app over an XPC trust boundary and verifies the calling app's code signature
before acting, so only the genuine GearFive app — not arbitrary local software — can request
privileged operations. The helper holds the minimum privileges required for its task.
Enforcement model
On devices managed through Apple mobile device management (MDM) or Automated Device Enrollment, GearFive's model and budget policies are delivered as managed configuration and are designed to be tamper-resistant. On unmanaged installs, controls are local and may be altered by a user with sufficient privileges — which is why un-bypassable enforcement is offered through MDM deployment.
Subprocessors & infrastructure
We rely on a small set of infrastructure providers, including Google Cloud Platform / Firebase (hosting and data) and Apple (software distribution and MDM). These providers operate under their own security programs and our contractual obligations.
Responsible disclosure
We welcome reports from security researchers. If you believe you have found a vulnerability, please email security@gearfive.io with enough detail to reproduce the issue. We ask that you give us a reasonable opportunity to remediate before public disclosure and avoid accessing or modifying data that is not yours. We will not pursue good-faith research conducted under these guidelines.
Working with enterprise security teams
Enterprise customers often have specific security and compliance requirements. We're glad to walk security teams through our architecture, data flows, and deployment model — reach out via Book a demo or security@gearfive.io.
Related
See our Privacy Policy for how we handle data and the Terms of Service for the terms that govern use of the Service.