How Relevare protects your data. Built for IT teams and security reviewers who need to understand exactly how Relevare runs.
Last updated: July 2026
Relevare runs on the employee's workstation. Capture and storage are local: screenshots, the raw accessibility tree, and the full text corpus live in an encrypted database on the machine and are never uploaded. To turn that into advice, the analysis stages send text excerpts describing the work (app names, window titles, URLs, short passages of on-screen text) to an AI model under a zero-retention policy. Screenshots are never transmitted. That excerpt path is the one place captured content leaves the device, and the sections below describe exactly what it contains.
Relevare does not install kernel extensions or system-level drivers. It uses standard user-space APIs on each platform: the accessibility tree and screen-capture APIs on macOS, and UI Automation and the Desktop Duplication API on Windows. A bug in Relevare cannot cause a kernel panic or blue screen, because the operating system's process isolation contains it.
The short version: what Relevare records stays on the machine, and the only thing that leaves is a bounded set of text excerpts sent for analysis under a zero-retention policy. The full technical detail, capture by capture and endpoint by endpoint, is in the security review you can request below.
Capture is scoped to the foreground window, the local API binds to 127.0.0.1 and is restricted to the desktop app's own origins, and known password managers and secure input fields are excluded from capture. Retention is tiered and aggressive: screenshots clear within a day, and raw text is purged as soon as analysis has read it.
Analysis excerpts are drawn from what is on screen, so they can contain real work content, including names and figures. That is the trade the product makes: it cannot tell you where your time goes without reading what you were doing. It stays on the machine except for the excerpt path, that path is bounded and text-only, and the model it reaches retains nothing. The full security review documents exactly what those excerpts contain and every endpoint involved.
Relevare's capture layer is built on open-source technology with full source code available for inspection. Anyone (your security team, a third-party auditor, or the public) can read exactly what data is captured, how it is stored, and what leaves the device.
This is a trust signal that closed-source monitoring products cannot provide. You don't have to take our word for how the agent works. You can verify it yourself.
Open source: screen capture, accessibility text extraction, data storage, local API, OCR. Proprietary: the intelligence pipeline (workflow analysis, bottleneck detection, solution design, executive summaries).
| Capability | macOS | Windows |
|---|---|---|
| Code signing | signed | signed |
| Signing authority | Apple Developer ID | Azure Trusted Signing (Authenticode) |
| Notarization | notarized | N/A |
| Hardened runtime | enabled | N/A |
| Update signature verification | minisign | minisign |
| Enterprise managed deployment | supported | supported |
macOS builds are signed with an Apple Developer certificate, notarized with Apple's notary service, and run with hardened runtime enabled. Windows builds are signed via Azure Trusted Signing as part of the CI/CD release pipeline. Updates on both platforms are cryptographically verified using minisign before installation.
Enterprise builds disable in-app auto-updates, allowing IT teams to manage deployment through their existing tooling (Intune, Jamf, etc.).
| Certification / standard | Status |
|---|---|
| Privacy policy | published |
| Terms of service | published |
| SOC 2 Type II | in progress |
| GDPR compliance | in progress |
| HIPAA (team tier) | architecture compatible, BAA available |
| ISO 27001 | planned |
| Penetration test | planned |
Relevare's on-device architecture reduces compliance scope substantially, though not to zero. Screenshots and the full captured corpus stay on the workstation and reach no vendor. The AI provider receives bounded text excerpts, which may contain personal data, under a zero-retention policy, so that data is processed but not stored. Relevare itself holds no captured content: encrypted sync is not enabled, and there is no server-side store of screen data. SOC 2 scope covers SDLC, code signing, access controls, the AI proxy, and organizational policies. That is materially smaller than a cloud competitor that ingests raw user data, though the excerpt path is in scope and should be assessed.
The page above is the overview. Security teams, IT reviewers, and prospective customers can request the full security review: the complete capture-by-capture breakdown, the exact contents and limits of what is sent for analysis, the network egress inventory, retention mechanics, and the local API model. We send it directly, usually within one business day.
If you discover a security vulnerability, please report it responsibly:
We acknowledge reports within 48 hours, triage within 7 days, and coordinate disclosure with the reporter. We do not take legal action against good-faith security researchers.
Full disclosure policy available upon request. Contact security@relevare.tech
For detailed IT deployment information, see our IT Security & Deployment Guide. It covers permissions, network call inventory, managed deployment (MDM), data model, and independent verification steps.