Legal

Security

Darvy reads your screen and types on your behalf. That's a lot of trust to ask for. Here's what we do with it.

Status

Current product behavior. Darvy has no server-side store for transcripts, documents, email, audio, screenshots, or browser content. Narrow service databases hold aggregate metering and separately consented content-free events.

What stays on your machine

  • Your account passwords and login cookies for Google, Microsoft, etc.
  • Documents, emails, and files Darvy reads to answer your question.
  • Conversation history (if you enable history — off by default).
  • Your license key (stored in your OS keychain).

What leaves your machine

  • Microphone audio goes to a speech-to-text provider for transcription. Audio is not retained by that provider after transcription.
  • Transcribed text and tool descriptions go to a large-language-model provider to decide what action to take. We do not opt in to provider-side training.
  • Reply text goes to a text-to-speech provider to generate the voice you hear.
  • Required service metering sends license-linked aggregate duration, provider, token/call totals, response timings, version, and platform fields.
  • Optional product analytics sends strict event/action categories, outcomes, reason codes, durations, version, and platform only after consent.
  • Optional crash diagnostics sends scrubbed error type, stack locations, OS version, and app version only after separate consent.

Reporting safeguards

Reporting never includes prompts, transcripts, audio, model answers, screenshots, filenames, paths, URLs, document text, browser content, tool arguments, or tool results. Optional product analytics uses a random installation ID rather than an email, license, machine name, or hardware fingerprint. Raw product events are retained for at most 90 days and daily aggregates for at most 13 months.

Both optional choices start off and can be changed independently under Privacy and data. Product opt-out deletes the local ID and queued reports. Crash opt-out closes the Sentry client.

Payment data

Card details go directly from your browser to Polar, our PCI-compliant payment processor. We never see them. We see only your email address and a Polar customer ID.

Responsible disclosure

If you find a security vulnerability — in this website, the desktop app, or our license server — please report it to support@darvy.ai with "Security" in the subject. We'll acknowledge within 48 hours and work with you on a coordinated disclosure timeline. We don't have a paid bug bounty programme yet but we'll publicly credit you (with permission) once a fix ships.

More detail

For deeper technical detail, see the canonical legal/security.md document or email security@darvy.ai.

Last updated: 2026-07-13.