capy.

capy Privacy Policy

Effective date: 1 October 2026 · 中文版

This Privacy Policy explains how the capy application accesses, uses, stores and shares your data, including the Google user data capy can access after you sign in with Google and grant consent, and how you can revoke access and delete your data.

The short version: capy is an open-source program that runs on your own computer. It has no backend server. Your data stays on your computer, in your own Google Drive, and on the music services you connect. No user data or credentials ever pass through us, and we have no means to collect them.

1. What this policy covers

This policy applies to the capy application (the command-line tool and its built-in local web interface, capy --web) and to this website, capy.taislife.work. capy is maintained by Tai (GitHub: Tai-ch0802) as an individual. The source code is public on GitHub under the MIT License, so every statement below can be verified in the code.

2. Google user data capy accesses

Signing in with Google is optional. When you run capy auth login google and grant consent, capy requests exactly the following three scopes and no others:

3. How that data is used

4. Where data is stored

5. Sharing and transfer

capy does not sell your Google user data and does not give it to us, and it does not share or disclose it to any third party except in the cases below, which you trigger yourself. It sends the data, as described in section 3, only in the cases below, only when you trigger it, only for the feature you are using, and only to services you signed in to or configured yourself: to the music services you are signed in to when you sync, move or look up matching tracks (and to Google as search queries when looking for a song on YouTube Music), to that music service to play a song when you press ▶ on My playlists, and to the AI endpoint you configured when you press Wiki. In addition, when you click a link on the web UI (such as "Listen on Spotify", YouTube Music's "Open", or the song wiki's MV link), your browser opens that page, and the link carries that song's or playlist's ID on that service (for the MV link, the song's title and artist as a YouTube search). Apart from that, the data never leaves your computer and your own Google account. capy never uses this data to train any AI or machine-learning model; how a service that receives it handles it is governed by that service's own policy.

When the song wiki (capy wiki) is about the song that's playing or a title you type, it sends the public song details listed in the previous section to the AI endpoint you configured yourself, at your direction; those come from the music service or from what you typed, so they are data about the music, not your Google user data, and capy sends no account information with them.

The Wiki button on My playlists is different: the title and artist it sends are taken from your playlist's master copy stored in your Google Drive, so they are Google user data. capy transfers them only to provide the song wiki you asked to see, only when you press the button, and only to the endpoint you configured, and never uses them to train any AI or machine-learning model. Whether that endpoint keeps what it receives or learns from it is governed by that service's own policy, so choose one whose terms you accept.

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

6. Retention and deletion

Because the data is in your hands, you decide how long it is kept. To remove everything:

7. Security

All connections between capy and Google, Spotify, Apple and YouTube Music use HTTPS. Tokens are stored only in the operating system keychain. The capy --web interface binds only to 127.0.0.1 (reachable only from your own computer), uses a one-time access code on every start, and never shows any token or secret on the page. If the AI endpoint you set up uses plain http to another computer, capy warns you when you set it (the API key and custom headers would travel unencrypted).

8. This website

capy.taislife.work is a static website: it sets no cookies, loads no third-party resources, has no forms, and contains no analytics or tracking code of our own. It is hosted by Cloudflare, and the hosting provider may automatically add analytics code to pages at the domain level. This site's Content Security Policy (default-src 'none') forbids pages from running or loading any script; in our tests that code is blocked by your browser and is neither executed nor loaded.

As with any website, Cloudflare processes the technical information needed to serve a request (such as IP addresses and the headers your browser sends with the request) under its own privacy policy. Our Cloudflare account may keep access logs (the requested URL, the time, and the technical information above) for a limited period, solely to troubleshoot the website; we do not use those records to identify or track visitors. This site shares its parent domain with taislife.work: if you have visited other pages on taislife.work, your browser may include cookies set by those pages in the request headers it sends to this subdomain. Like any other header they reach the hosting provider and are covered by the previous sentence; nothing on this website reads or uses them, and we never look at them.

9. Children

capy is not directed to children under 13, and we do not (and cannot) collect personal data from anyone.

10. Changes to this policy

If the way capy accesses data changes (for example, a new permission), we will update this page and the effective date above before releasing the new version. Every revision is kept in this file's version history.

11. Contact

Questions about this policy or your data: please open an issue on GitHub Issues (do not paste tokens or personal data into a public issue).