How Relevare protects your data. Built for IT teams and security reviewers who need to understand exactly how Relevare runs.
Last updated: August 2, 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 not uploaded. To turn that into advice, the analysis stages send filtered text describing the work (app names, window titles, URLs, and short passages of on-screen text) to an AI provider. Screenshots are not sent for analysis. That text path is the one place captured work content leaves the device, and the sections below describe 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 captured work content that leaves is filtered text sent to the chosen AI provider for analysis. The full technical detail, capture by capture and endpoint by endpoint, is in the security review you can request below.
Text capture is scoped to the foreground window. Screenshots can include the full display. The local API binds to 127.0.0.1 and rejects untrusted browser origins. Relevare filters known sensitive apps and lets users add exclusions, but no filter can guarantee that sensitive text will never be captured. Cleanup runs hourly: screen images and raw trees default to one day, text is removed after analysis with safety limits, and frame metadata defaults to seven days.
Analysis text is drawn from what is on screen, so it can contain real work content, including names and figures. That is the trade the product makes: it cannot explain where time goes without reading what the user was doing. Captures stay on the machine; only filtered text goes to the configured AI provider. The full security review documents what may be included 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 | not certified; no BAA offered |
| ISO 27001 | planned |
| Penetration test | planned |
Relevare's on-device architecture reduces compliance scope, but does not remove it. Screenshots and the full captured corpus stay on the workstation. The AI provider receives filtered text that may contain personal data, so that processing must be assessed. Relevare does not operate a server-side store of screenshots or captured history. Security reviews should still cover software delivery, code signing, access controls, the AI provider path, service providers, and company policies.
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 [email protected]
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.