Privacy and network
Local-first storage is a data policy, not a promise of zero network traffic.
Optional analytics
Product analytics are optional and off by default. VStudy asks once at first launch, and you can change the choice in Settings > Privacy at any time. No feature depends on it. When on, VStudy sends usage events keyed to a random installation ID to PostHog in the United States. The events cover launches, active time, features used, AI provider, model and token counts, broad question categories, document and study actions, sanitized errors, how you heard about VStudy, your school when Moodle identifies it, and basic device and app details.
The events never contain your questions, answers, documents, notes, search queries, file names, keystrokes, screenshots, or Moodle identity details. An optional product-update email address is kept in a separate service and never reaches analytics. The Privacy Policy lists every category, the retention periods, and how to request deletion.
When VStudy connects
VStudy sends no analytics unless you opt in. Choosing a Moodle school contacts the school. Enabled AI providers receive prompts and reading context. Optional conversion setup downloads packages from PyPI, and uv may download Python from GitHub.
Downloaded converter workers deny network access on macOS. External links open only after confirmation. Local document and history search do not require an external search service.
Inspect session activity
Settings > Privacy has a bounded, session-only inventory of app-initiated requests and CLI launches. Moodle destinations show hostnames without paths, query strings, passwords, or tokens.
The inventory is not a packet capture. It cannot enumerate every encrypted request inside a CLI or Chromium. Byte counts are currently unknown. Provider privacy policies still apply to information sent to those providers.
Delete application data
Delete all data requires typing DELETE and accepting a native confirmation. It removes the application data namespace and quits. Make a backup first if you want to retain your coursework.
Deletion keeps original files outside the library, CLI logins, and shared Python download caches. It is not secure erasure of backups or SSD blocks. Remove exported backups separately when they are no longer needed.