The short version. Pylon is a program that runs on your own computer. It has no servers, no accounts and no analytics, so there is nowhere for your data to be sent and no one to receive it. Anything Pylon reads — your calendar, your files, what you say to it — stays on your disk unless you have configured a service that needs the network, and this page lists every one of those.
Pylon is an independent open-source project (the “project”). This policy covers the Pylon daemon and its desktop interface, which you download and run yourself. There is no hosted version of Pylon and no service operated by the project.
Because Pylon runs entirely on your machine, the project does not receive your data at all — not in aggregate, not anonymised, not at any point. Where this page says “stays local”, it means the project has no technical way to see it.
Google Calendar and Google Drive are optional integrations. If you never run
pylon auth google, Pylon never requests or receives anything from
Google.
If you do connect them, Pylon requests exactly two scopes:
calendar.events(read and write) |
Reads today's events so the daily briefing can say how many you have and answer questions about your day. Creates an event when you explicitly ask for one (“add a dentist appointment tomorrow at three”). Pylon does not delete events, and it does not modify events it did not create. |
|---|---|
drive.metadata.readonly(read-only) |
Searches your Drive by file name and lists recently modified files, so Pylon can tell you where something is. This scope returns metadata only — names, dates and links. Pylon cannot read the contents of your documents and never asks for permission to. |
pylon recall can show you the last few turns. That database is
a file on your disk.| Google access and refresh tokens | Encrypted (AES-256-GCM) in Pylon's local vault under your user
configuration directory — ~/.config/pylon/ on Linux, the
equivalent on macOS and Windows. Never written to a config file in plain
text. |
|---|---|
| Recent replies and commands | A local SQLite database in the same directory, holding a limited number of recent turns. |
| Session records | Which of your tracked applications were open and for how long — local only, and only for applications you list yourself. |
pylon auth google logout deletes the stored tokens
immediately.~/.config/pylon/ removes everything Pylon has ever
stored, including the local database.Pylon's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Pylon does not transfer Google user data to anyone, does not use it for advertising, does not sell it, and does not allow humans to read it — there is no server on which any of that could happen.
Pylon has no network dependencies of its own, but several optional features call services you choose and configure. Each is off until you set it up.
| AI model provider (Gemini, OpenAI or Anthropic) |
Receives the text of the command you typed or spoke, and a short description of your speaking style. It does not receive your calendar, your files, or the results Pylon produces. Your key stays in the local vault. Their handling of that text is governed by their own privacy policy. |
|---|---|
| Speech to text | Runs locally by default (whisper.cpp on your machine). Your voice is not uploaded anywhere unless you configure a remote transcriber yourself. |
| Text to speech | Disabled unless you set voice.tts_cmd. Pylon passes the
reply text to whatever command you name. If you choose a
network-based voice, that reply text — which may include a calendar entry
Pylon just read to you — goes to that provider. A local engine
such as piper keeps it on your machine. |
| Weather, exchange rates | Public, key-less APIs (Open-Meteo, open.er-api.com, CoinGecko). They receive the coordinates or currency codes you configured — never personal data. |
| GitHub, FreshRSS, Spotify, Docker | Contacted only with the credentials you provide, to fetch what you asked for. Docker talks to the socket on your own machine. |
The only network call Pylon makes on its own initiative is an update check
against GitHub's public release API when you run pylon update,
which sends nothing but the request itself.
Pylon is a developer tool and is not directed at children under 13. The project collects no data from anyone, including children.
If the way Pylon handles data changes, this page changes with it, and the date at the top is updated. Because the policy lives in the project's public repository, every revision is visible in its history.
Questions about this policy, or about what Pylon does with anything, go to GitHub Issues, where they are answered in public. The code that handles Google data is readable in internal/services/google if you would rather check than take this page's word for it.