Privacy

Browsing and local research

You can read public benchmark data without an account. Watchlists, Research entries and notes, saved views, chart choices and display preferences are stored in your browser. They are not synced to a BenchmarkWatcher account. Clearing site data in your browser removes those local copies; export any Research backup you want to keep first.

The site uses a session cookie for signed-in accounts and a preference cookie for the selected view. Your browser may also request font files from Google Fonts. Opening an external source or community link takes you to that site under its own privacy practices.

Native research on your device

The Swift and Kotlin development apps save followed companies, report snapshots, notes and review baselines on your device. They do not automatically sync those records into a web account. Company searches and explicit report refreshes contact the public BenchmarkWatcher research API; local notes are not included in those requests. The current native apps do not connect to paid AI providers.

Opening a filing source sends you to the SEC website under its own privacy practices. Uninstalling an app or removing its app data may remove local research, so retain any files you need before doing so.

Account and saved work

If you create a company-research account, we store your username, password and recovery-code hashes, sign-in sessions, saved company reports, questions and answers, AI connection settings and API request-usage records. Passwords and recovery codes are not stored as plain text. Connected provider keys are encrypted in the server database.

These records support sign-in, saved reports, request limits and the usage information shown in Profile. Account and saved-work records are not automatically deleted on a fixed schedule. Email us if you want to ask for access to or removal of your account data.

Source and AI requests

BenchmarkWatcher requests public benchmark data and SEC filings from their sources to build the views you open. Connecting an optional AI provider sends your key to that provider for a connection test. Before sending a question and the described public filing or workbook evidence, the app asks for your consent. For workbook questions, you may choose to remember consent for the same provider setup until you sign out. Built-in calculations do not contact an AI provider.

DeepSeek and TypeSafe / Jev handle information sent to their services under their own terms and privacy policies. Provider charges, if any, are billed by the provider. Do not include private information in an AI question that you do not want to share with that provider.

Operating the site

Our hosting service may process your IP address and request information in access or error logs to deliver and protect the site. We use HTTPS for the public website. No security measure eliminates every risk; keep your password, recovery code and provider keys private.

Choices and contact

You can use public benchmarks without signing in, remove a saved AI connection in AI settings, and clear browser-stored data through your browser. To ask about account data or this notice, email benchmarkwatcher@aulenor.com. Please do not post private details in a public GitHub issue.

We will update this page when site data handling changes. For product help, visit Support.