Getting in touch
Email — support@vilo.page
For anything private: your account, your data, a question about the
privacy policy.
GitHub issues —
github.com/ikerdpv/vilo/issues
For bugs and feature requests. Better than email, because the answer stays public
and helps the next person with the same problem.
Vilo is maintained by two people in their spare time. Replies are not instant, and there is no support contract behind this — but everything gets read.
Disconnecting your Google account
This revokes Vilo's access with Google and deletes the stored session from your machine. Your calendar and Classroom data are untouched; Vilo simply stops being able to read them.
- Open Vilo.
- Go to Settings → Google.
- Choose Disconnect. Vilo asks Google to revoke the token and then deletes its copy.
- Optional, and worth doing once: open myaccount.google.com/permissions and confirm Vilo is no longer listed. Everything with access to your Google account is on that page, not only Vilo.
You can sign in again at any time. Nothing you wrote down yourself — tasks, exams, grades — is affected either way.
Deleting everything Vilo has stored
All of it is in one folder on your own computer. There is no server-side copy, so deleting that folder is genuinely the end of it — you do not need to email anyone to complete the deletion.
- Disconnect Google first (above), so the token is revoked with Google rather than merely deleted from your disk.
- Quit Vilo completely — including the tray or menu bar icon.
-
Delete the data folder:
- macOS —
~/Library/Application Support/Vilo - Windows —
%APPDATA%\Vilo
- macOS —
-
Uninstall the app if you want it gone: drag Vilo from
/Applicationsto the Bin on macOS, or use Settings → Apps → Installed apps on Windows.
On macOS, the folder is inside a hidden Library. In Finder, press
⌘⇧G and paste
~/Library/Application Support/Vilo.
On Windows, press WinR and paste
%APPDATA%\Vilo.
That folder is everything: tasks, exams, grades, folder rules and their history, chat history, settings, and the encrypted credentials file. Uninstalling on its own leaves it behind on purpose, so that reinstalling finds your things where you left them.
Taking a backup with you
Settings → Advanced → Export writes your tasks, exams, folder rules and chat history to a single JSON file you can keep, move to another computer, or open in a text editor to read.
Credentials are deliberately left out of it. They are encrypted with your machine's own keychain and would be unreadable elsewhere anyway — and a backup file with your Google session inside it is exactly what you do not want in a shared folder.
Common problems
Google sign-in fails, or the window closes immediately
The most likely cause is that your school's Google Workspace administrator has blocked third-party applications. There is no way around that from Vilo's side — it is a setting on the account, and working around it would be exactly the wrong thing to do. You can still use Vilo without signing in, or sign in with a personal Google account instead.
Windows says the installer is unrecognised, or antivirus flags it
Vilo's Windows build is not code-signed, so SmartScreen warns the first time and some
antivirus engines flag a newly built .exe on heuristics alone.
The full explanation is in the repository,
along with the portable .zip, which trips those heuristics far less
often.
The realistic voice is slow the first time
The speech models are downloaded once, on first use, and then run offline. The first sentence after that is also slower than the rest while the model warms up. If your machine has a GPU that WebGPU can reach, the larger package uses it and is considerably quicker.
Chat says no model is configured
Vilo does not ship with one. Open Settings → Models and either paste a key from a provider, point it at an Ollama install, or — on macOS 26 with Apple silicon — turn on Apple's on-device model, which needs neither key nor download.
Reporting a bug
Useful things to include, roughly in order of how much they help:
- What you expected, and what happened instead.
- Your operating system and its version, and Vilo's version (Settings → About).
- Whether you were signed in to Google, and which model provider was selected.
- Anything from Settings → Advanced → Open logs around the time it happened.
Please check the log before pasting it. It should not contain credentials, but it can contain the names of your classes and files.