Privacy policy

In short

Vilo is a desktop application. It is not a website, it has no user accounts, and there is no Vilo server that your data passes through. When Vilo shows you your timetable, your computer asked Google for it directly and then drew it. Nothing in between belongs to us.

• Google data is read from your computer, by your computer.
• It is held on your computer, in your own user folder, and your Google session is encrypted with your operating system's keychain.
• No data reaches our servers, because we do not run any.
• Your data is never sold, never shared with data brokers, and never used for advertising or to train any model.

Who runs Vilo

Vilo is a free, open-source project maintained by two individuals. It is not a company and there is no business model attached to it. The complete source code — including every line described on this page — is public at github.com/ikerdpv/vilo, and can be read, audited or built from scratch by anyone.

Vilo is not affiliated with, endorsed by, or sponsored by Google LLC.

Which Google data Vilo accesses, and why

You sign in with Google only if you want to. Vilo opens and works without it — the schedule and the assignment list are simply empty until you fill them yourself.

Signing in uses Google's OAuth flow for desktop applications (PKCE with a loopback redirect). Your Google password is never typed into Vilo and never seen by it: you type it into Google, in your own browser, and Google hands Vilo a token afterwards.

These are all of the permissions Vilo requests, and what each one is for:

openid and userinfo.email

To complete sign-in and to display which account is connected. Students routinely have a school account and a personal one, and showing the address is how you can tell which is which. The email address is only shown; it is not transmitted anywhere.

calendar.events

Read: to show your week in the Schedule screen and to answer questions about it. Write: to add the events you explicitly ask for — a study block, an exam, a reminder. Every write is shown to you and waits for your confirmation before anything is sent to Google. Vilo does not modify or delete events you did not ask it to.

classroom.courses.readonly

The list of classes you are enrolled in. Assignments are meaningless without the subject they belong to, and this is where the subject names come from. Read only.

classroom.coursework.me.readonly

Your own coursework and its due dates. This is what fills the task list and what every deadline warning is counted from. Read only, and scoped to you — it grants no access to other students' work.

classroom.student-submissions.me.readonly

Your own submissions: whether each assignment has been handed in, and the mark if it has been graded. Without it, Vilo cannot distinguish finished work from work you have not started, and the Grades screen has nothing to show. Read only, and scoped to you.

drive.file

The narrowest Drive permission Google offers: it grants access only to files Vilo itself creates, or that you specifically open with it. It does not grant access to the rest of your Drive, and Vilo cannot list, read or search files it was not given.

Vilo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Where your data is stored

In your own user folder, on your own machine, as ordinary files you can open, copy, back up or delete:

• macOS — ~/Library/Application Support/Vilo
• Windows — %APPDATA%\Vilo

That folder holds your tasks, exams and grades, your folder-tidying rules and their history, your chat history, and your settings. Calendar events and Classroom assignments are fetched when you open the app and held in memory to be drawn; Vilo does not keep a private copy of your Google account.

Credentials are kept apart from all of it, in an encrypted file. The encryption key belongs to your operating system — Keychain on macOS, DPAPI on Windows — which means the file is unreadable on any other computer, and unreadable by any other user account on yours. This covers your Google refresh token and any model provider API keys you have entered.

Vilo's backup export deliberately leaves credentials out. A backup file with your Google session inside it is exactly the file you do not want sitting in a shared folder.

Whether any data reaches our servers

No, and there is nothing to opt out of, because the servers do not exist. Vilo has no backend, no database, no accounts system and no analytics. There is no telemetry, no crash reporting, no usage tracking and no unique identifier assigned to you or to your installation.

Third parties your computer talks to

Vilo makes network requests directly from your machine, and only to these:

• Google — for the data described above, when you are signed in.
• The model provider you chose — Vilo does not ship with an AI model. If you point it at a hosted one (OpenRouter, OpenAI, Anthropic, Groq, Mistral, Gemini, or a server of your own), then the text of what you ask, and the context needed to answer it, is sent to that provider under their terms and their privacy policy. This is the single case where your information leaves your computer other than to Google, and it happens because you configured it. Choosing Ollama, or Apple's on-device model on a recent Mac, keeps even that local.
• GitHub — to check whether a newer version of Vilo has been released, and to download it. No personal data is sent; it is a request for a file.
• Hugging Face — only if you turn on the realistic voice, to download the speech models once. They then run offline on your machine.

Microphone and voice

The microphone is used only while you are holding the orb or the space bar. Speech is transcribed by a model running on your own computer; the audio is never uploaded and is not written to disk. What you said becomes text on your machine, and from there it is treated like anything you had typed.

What we never do

• We do not sell your data, or any part of it, to anyone.
• We do not use your data for advertising, or serve you advertising.
• We do not use your data — or Google user data — to train any AI model.
• We do not share your data with data brokers, or transfer it to others except as described above, where you asked for it.
• We do not build a profile of you. There is nowhere to keep one.

Disconnecting Google and deleting your data

You can do either at any time, without asking us.

Disconnect Google

1. Open Vilo and go to Settings → Google.
2. Choose Disconnect. Vilo revokes the token with Google and deletes it from your machine.
3. To confirm from Google's side, visit myaccount.google.com/permissions and check that Vilo no longer appears.

Delete everything Vilo has stored

1. Disconnect Google first, as above, so the token is revoked and not merely deleted.
2. Quit Vilo.
3. Delete the data folder: ~/Library/Application Support/Vilo on macOS, or %APPDATA%\Vilo on Windows.
4. Uninstall the application if you want it gone entirely.

That is the whole of it. There is no server-side copy left behind, and nothing to email us about to complete the deletion. The support page has this with more detail.

Your rights

Because your data never leaves your device, the rights that data protection law gives you — access, correction, export, erasure — are yours to exercise directly, and immediately. Your files are in the folder named above. Vilo also has an export in Settings that writes your tasks, exams, rules and chat history to a single JSON file.

We cannot access your data, and so we cannot produce, correct or delete it for you. That is not a limitation we are apologising for; it is the design.

If you are under 18

Vilo is a study tool and many of the people using it are school pupils. It collects nothing about anyone, of any age, because it sends nothing anywhere. If you are using a school Google account, your school administers it and their own policies govern what that account may connect to — some Workspace for Education accounts are configured to block third-party applications entirely, and Vilo cannot and should not work around that.

Changes to this policy

If what Vilo does with your data changes, this page changes with it, and the date at the top changes too. Every version of it is in the site's Git history, so you can see exactly what changed and when.

Contact