Privacy Policy
How EVB Viewer handles documents, settings, analytics, and optional assistant features.
Effective September 4, 2026
Documents and local processing
EVB Viewer opens documents selected by you. Desktop document viewing, OCR, annotation, page operations, and export are performed on your device. The browser app processes selected documents in your browser unless you choose a feature that explicitly uses an external service. EVB Viewer does not upload your documents to the developer by default.
Optional assistant services
Assistant features are optional. When you use an assistant backed by Codex, OpenAI, or Anthropic Claude, prompts and any content or attachments you choose to include are sent to that provider under your account and are governed by that provider’s terms and privacy policy. EVB Viewer does not sell this information.
Optional Sentry error reports
EVB Viewer is the controller and uses Functional Software, Inc. d/b/a Sentry as its processor for optional client error reports. Desktop and browser reports are sent only with your consent. A report may contain a random Error ID, time, severity, diagnostic code, app release, operating system and runtime names and versions, EVB Viewer stack frames (file, function, line and column), and the error type and message after local paths, file names, URLs and quoted text are removed. For a native crash it records which process ended and why; the memory dump is never sent. It never contains document contents or text, local paths or logs, URLs or request data, console output, screenshots, attachments, account data, IP address, or identity. Reports are used only to diagnose crashes and product errors, never for analytics, advertising, profiling, AI, or training. Sentry stores events in the EU region for up to 90 days and may use its published subprocessors and the DPA and Standard Contractual Clauses for limited onward transfers. You can withdraw consent at any time to stop future reports. The EVB Viewer web service sends no server-side error reports.
Analytics and technical information
The EVB Viewer website and browser app use Vercel Web Analytics. It records page paths without query strings, the referrer, country, browser, operating system, and device type, plus a few feature events such as the type of document opened or an installer download. Visitors are counted with a hash that resets daily; no cookies are set, and document names, paths, and contents are never included. The desktop app sends no analytics.
Settings, recent files, and updates
App preferences, workspace state, and recent-file references may be stored locally on your device. The desktop app may contact GitHub to check for and download software updates. Operating-system and app-store services may process additional technical information under their own policies.
Cookies and browser storage
EVB Viewer uses first-party preference cookies to remember language and, in the browser app, theme. Language cookies may last up to one year, and the theme cookie may last up to 180 days. The download site uses an opaque, HttpOnly cohort cookie for up to 90 days to keep staged release recommendations consistent; it is not used for advertising or cross-site tracking. The browser app also uses local storage, session storage, and IndexedDB for preferences, recent-file references, workspace state, and document data you choose to retain. EVB Viewer does not set advertising or third-party cookies. You can remove cookies and browser-stored data through your browser’s site-data controls; doing so resets preferences and locally retained app data.
Retention and choices
Local app data remains on your device until you remove it or uninstall the app. You control which documents and attachments are opened or sent to optional assistant services. Website analytics are aggregated by Vercel and kept within the retention limits of its Web Analytics service.
Contact
Private contact for privacy requests is currently unavailable. Do not publish personal details or Error IDs in public channels.