隐私政策

车载点歌台 · 更新于 2026 年 10 月 28 日

车载点歌台（下称「本 App」）是一个车上的点歌工具：司机的 iPhone 放歌，朋友扫码在网页上点歌。本 App 由个人开发者开发（下称「开发者」）。本 App、点歌台服务器程序和这个网站都没有广告，不做追踪，也不用任何统计、分析或崩溃上报工具。

你的数据存在哪台服务器上

除了直接从 QQ 音乐的服务器放歌、加载封面（见第三方），本 App 只连你设置的那台点歌台服务器。数据存在哪台服务器上，就由谁保管。用邀请码开的车，在 App 的「设置 → 我的车」里能看到它建在哪个地址上。

你的车	数据在哪	谁保管
用开发者发的邀请码开的车	开发者的服务器 `39.108.51.5`（阿里云，中国大陆）	开发者。下面「开发者服务器上存什么」说的就是这种车
用朋友发的邀请码开的车	那位朋友自己的服务器	那位朋友。服务器程序存的东西和下面一样，日志、备份怎么管由他决定。开发者收不到这些数据
你自己搭的服务器	你自己的云服务器	你自己。开发者收不到这些数据

自己搭服务器时，安装和以后更新都要从开发者的服务器下载程序。这时开发者的服务器会看到你那台服务器的 IP 地址，只在内存里用来限制下载次数，不写日志。装好以后，你的服务器不会再联系开发者的服务器。安装时还要从别的网站下载运行环境 Node.js 和申请证书用的 certbot，那些网站也会看到你那台服务器的 IP 地址，见第三方。

存在你手机上的

播放器链接（服务器地址和这辆车的播放器密钥）存在 iOS 钥匙串里，旁边还有一个标记，记着这是不是用邀请码开在别人服务器上的车。它们不会同步到 iCloud 钥匙串。
- 删掉 App 以后它们还留在钥匙串里，重装会自动连回原来的车。
- 它们会跟着加密的 iPhone 备份走，包括 iCloud 云备份。从备份恢复到新手机，链接也在。
- 「设置 → 忘掉这辆车」和「删除这辆车」会把它们从钥匙串里删掉。
- 极少数情况下钥匙串写不进去，链接和标记会先存在 App 自己的设置里，下次打开再搬进钥匙串。
设置：音质、「队列空时保持后台在线」开关。用邀请码开车时还会存一个一次性的请求编号，车开成以后就删掉。
把 QQ 音乐登录二维码存到相册时，App 会请求「仅添加照片」权限，不读你的相册。存进去的二维码留在相册里，登录完可以删掉。

这些里面，只有三样会发给这辆车所在的服务器：播放器链接里的密钥，每个请求都带着，用来证明你是司机；音质设置，取播放链接时带上，服务器用完不存；开车时的请求编号，见下面的「邀请记录」。钥匙串里那个标记和「队列空时保持后台在线」开关不发出去。播放器密钥在服务器上怎么存：用邀请码开的车，服务器上只存它的哈希；服务器主人自己的那辆车（比如你自己搭的服务器上的车）不一样，密钥原样存在服务器上，每次启动还会打进日志（见服务器日志）。

App 用着的时候，还会发给这辆车的服务器：在放哪首（服务器把正在放的那首存进这辆车的文件，放完移进播放历史，见下表）；放到哪、暂停没有（这两样服务器只放在内存里，给同车的人显示进度，不写进文件）；播放出错的信息（写进日志，见服务器日志）；你在 App 里改的车名和车的规矩、导入歌单时贴的链接或歌名，以及调整队列、删歌。车开在开发者的服务器上时，这台服务器就是开发者的。

朋友用的点歌网页

点歌网页不用 cookie。浏览器的本地存储里记着：点歌链接里的密钥、一个随机编号、填过的昵称，以及问没问过你昵称。每次打开点歌页、点歌、撤回，随机编号都会发给服务器：服务器靠它认出是同一部手机（分动画角色名、算点歌人编号），撤回自己点的歌时也要带上它。清除这个网站的浏览器数据，这些就删掉了。
司机在 Safari 里用的网页播放器也一样不用 cookie，本地存储里记着播放器链接里的密钥和「保持屏幕常亮」开关。
同一辆车里扫了码的人，都能看到队列、最近放过的 10 首，以及每首歌的点歌人昵称和点歌人编号。点歌人编号不是你的随机编号，是服务器用这辆车自己的随机密钥把它打乱以后的：只看得出哪几首是同一个人点的，推不回你的随机编号，换一辆车也对不上，别人拿它冒充不了你。
搜的词发给服务器，服务器再去 QQ 音乐搜，不带任何人的登录信息。搜索结果按搜的词存在服务器内存里，所有车共用，对应不到是谁搜的；搜的词不写进日志。缓存没有固定的保留时间：被后来的搜索挤掉（最多留几百条），或者服务器重启时清掉。

开发者服务器上存什么、存多久

下表是用开发者的邀请码开的车在开发者服务器上存的东西。车本身不会自动删除，不删就一直留着。

数据	用途	什么时候删除
车名、车的规矩、建车时间、用的哪个邀请码；一个随机的设备编号	显示车名，按车的规矩办；设备编号在取播放链接时报给 QQ 音乐（一辆车一个，和手机无关）	删除这辆车时
点歌密钥（点歌二维码里的那个）；播放器密钥只存哈希	认出这辆车的司机和朋友	删除这辆车时。之后两把密钥的哈希和这辆车的编号再留 30 天，只用来让旧链接显示「这辆车已经被删掉了」、认出没删干净的文件，以及保证新开的车不会用上同样的编号和密钥
播放队列和正在放的那首。每首歌存歌名、歌手、点歌人的昵称和点歌网页的随机编号、点歌时间	排队，显示谁点的歌，让朋友撤回自己点的歌。发给同车的人时，随机编号换成打乱过的点歌人编号	放完的歌移进播放历史；删除这辆车时全部删除
这辆车自己的一个随机密钥	把点歌人的随机编号打乱成点歌人编号	删除这辆车时
播放历史：最近放过的 50 首，内容和队列一样，再加上播放时间	点歌页显示最近 10 首；没人点歌时不重复放刚放过的	超过 50 首时最早的被挤掉，没有时间上限；删除这辆车时全部删除
每个打开过点歌页的人随机分到的动画角色名（填没填昵称都分），和他点歌网页的随机编号、最近一次打开点歌页或点歌的时间存在一起	没填昵称时当作他的名字；同一部手机再扫码，名字不变	12 小时没动静以后，下次有人打开点歌页或点歌时让出来（一辆车最多记 200 个，多了先让出最久没来的）；删除这辆车时。朋友自己填的昵称跟着点的歌存在队列和播放历史里，不会在 12 小时后删除
导入的兜底歌单：歌单名、歌名、歌手，导入人的昵称和随机编号	没人点歌时随机放	清除导入、导入新的歌单，或者删除这辆车时
最近有人用这辆车的时间、司机最近用的时间、播放器链接第一次用上的时间	司机最近用的时间决定什么时候续期、什么时候自动删除 QQ 音乐登录凭证（以前版本的服务器存的车看最近有人用的时间，见下）；最近有人用的时间还让服务器的主人看出哪辆车很久没人用了；播放器链接第一次用上的时间用在 App 开车时没收到回复、重试的时候：用过的车不再重发播放器链接	删除这辆车时
司机的 QQ 音乐登录凭证（cookie，里面有 QQ 号和大约两个月有效的续期令牌）。司机扫码登录以后才有	用司机自己的账号向 QQ 音乐取播放链接、读歌单、续期登录	司机退出 QQ 音乐登录或删除这辆车时马上删除。服务器每小时检查一次：司机连续 60 天没用过这辆车，或者 QQ 授权已经过期，就自动删除
邀请记录：邀请码只存哈希和前 3 个字符，还有开发者写的备注、能用几次、到期时间、用它开了哪几辆车（车的随机编号）；App 开车时带的一次性请求编号和开出来的车	管理邀请码；开车的回复没收到、App 重试时认出是同一次	请求编号 24 小时后删除；整条在邀请码过期或作废 7 天以后删除

「司机用过」只算带播放器链接的请求，来自 App 或网页播放器都算。朋友在点歌页一直在用，不算。例外是以前版本的服务器存的车：那时候只记了最近有人用这辆车的时间（朋友用也算），没单独记司机的，这样的车按这个时间算 60 天。一个时间都没记着的车（文件坏了、没了的）：服务器正在运行这辆车时，60 天从这次启动算起；没在运行它时（比如服务器的主人关掉了用邀请码开车），只等 QQ 授权过期。

这些文件万一读坏了（比如磁盘出错），有几种服务器会把坏的那份改个名留着查原因，30 天后自动删除：一辆车的队列和播放历史那份、导入的歌单（服务器运行这辆车、读它们的时候）；QQ 音乐登录凭证（服务器有没有在运行这辆车都一样）；邀请记录（服务器开着用邀请码开车的时候）。别的不改名：存车名和规矩的那份坏了，这辆车就开不起来，文件原样留着，不会自动删除；删掉的车的记录（密钥的哈希和车的编号）那份坏了，旧链接就显示不了「这辆车已经被删掉了」，服务器开着用邀请码开车时，下次再删一辆车会把这份整个重写（坏的内容就没了），没开时原样留着。

QQ 音乐登录凭证

只用来以你的身份向 QQ 音乐请求这辆车要用的东西：播放链接、兜底歌单、导入的 QQ 音乐歌单，以及定时续期登录。只有司机 7 天内用过的车才会定时续期。
不会出现在网页、推送和服务器日志里。别的车、点歌的朋友都看不到它。
服务器上不加密存放：加密用的钥匙也得放在同一台服务器上，挡不住服务器的管理员。开发者是这台服务器的管理员，技术上能读到它。App 在你开车之前也这样提示过。
同一个 QQ 号已经登在这台服务器的另一辆车上时，服务器会提醒你一句，但不说是哪辆车。两辆车续期时可能互相把登录顶掉。
从服务器上删掉凭证，不等于在腾讯那边取消了授权：这份授权在 QQ 那边要到期才失效。想马上作废，在手机 QQ 的「安全中心 → 授权管理」里取消 QQ 音乐的授权。

谁能接触到

别的车的人：不能。每辆车只认自己的密钥。
同一辆车里的人：能看到车名、队列、最近放过的 10 首、点歌人的昵称和打乱过的点歌人编号；看不到别人的随机编号、司机的 QQ 号和登录凭证。
开发者：作为服务器的管理员，能读服务器上的所有文件，包括上表里的全部数据和 QQ 音乐登录凭证。开发者只用这些数据让你的车能用。
阿里云：数据存在它的云盘上。如果服务器开着云盘快照，删除之前的数据会留在快照里，直到快照过期。

服务器日志

服务器不记访问日志：不记每个请求和访问的网址，也不记点歌的人从哪个 IP 来。
运行日志里会有这些：
- 车的编号和车名；
- 建车、删车、换链接、作废邀请这类管理记录，包括开发者写的邀请备注；
- 兜底歌单和导入的歌单的名字，导入人的昵称；
- 播放出错的信息：App 报上来的原文，服务器取播放链接失败的原因；
- QQ 音乐扫码登录、续期成功没有和失败的原因，退出登录；
- 每小时的清理删了什么（到期的登录凭证、没删干净的车、30 天以前读坏了的文件），以及有哪个文件它看不了、删不掉。
某个网络地址短时间里猜错密钥或邀请码太多次、被锁住时，日志会记下这个 IP 地址（IPv6 记前 64 位）。
用邀请码开的车，服务器不把 QQ 音乐登录凭证、密钥、QQ 号和 QQ 昵称写进日志。App 报上来的播放出错信息是原样记的，万一里面夹着 QQ 号或者凭证，服务器按常见的写法（cookie 和接口参数里的这些字段、o0 开头的 QQ 号）先抹掉；认不出的写法抹不掉。服务器主人自己的那辆车不一样：每次启动，日志里会打出它的播放器链接和点歌链接（带着密钥）；主人扫码登录 QQ 音乐时，会记下主人自己的 QQ 昵称。
日志存在服务器的系统日志（systemd journal）里，用系统默认的设置，没有单独设保留期限：占的空间到了上限，最早的先删。系统装着 rsyslog 的话（Ubuntu 一般装着），同样的行还会写进 /var/log/syslog，按系统的轮转设置定期删掉。删除一辆车，不会删掉已经写进日志的那些行。
为了挡住猜密钥、刷接口的人，服务器在内存里按 IP 地址计数。这些记录最多 12 小时就不再用，每小时清一次，不写进文件，服务重启就没了。

第三方

QQ 音乐（腾讯）：搜歌、歌词、歌单、播放链接和扫码登录，都由服务器去问 QQ 音乐。另外，App 直接从 QQ 音乐的服务器播放音频、加载封面，点歌网页也直接从 QQ 音乐的服务器加载封面，所以腾讯能看到你的手机或浏览器的 IP 地址。点歌网页不向腾讯发送来源网址，链接里的密钥不会被带过去。这些适用腾讯的隐私政策。本 App 和腾讯没有合作关系。
其他音乐平台：导入歌单时如果粘贴了网易云音乐、酷狗、酷我、汽水音乐、Apple Music 或 Spotify 的分享链接，服务器会去那个平台读这个公开歌单的歌名和歌手，不带任何人的账号。
阿里云：开发者的服务器托管在阿里云。
Let's Encrypt：服务器用它的免费证书提供 https 加密连接。
自己搭服务器时的下载站：安装程序从 npmmirror.com 下载 Node.js 运行环境，从阿里云的 mirrors.aliyun.com 下载申请证书用的 certbot，其他系统软件从服务器自己配好的软件源（apt）安装。这些网站会看到你那台服务器的 IP 地址。已经装好、版本够新的就不再下载。
GitHub Pages：这个帮助网站和隐私政策放在 GitHub Pages 上，GitHub 会看到访问者的 IP 地址，适用 GitHub 的隐私声明。网站本身不用 cookie，不跑脚本，也不从别的网站加载字体或文件。
Apple：如果你在 iPhone 的「设置 → 隐私与安全性 → 分析与改进」里选了与开发者共享，Apple 会把汇总的使用情况和崩溃报告提供给开发者。本 App 自己不收集这些。

删除你的数据

用邀请码开的车

删除这辆车：在「设置 → 我的车 → 删除这辆车」里输入车名确认。服务器会马上删掉这辆车的全部文件：车名、规矩、队列、播放历史、昵称、导入的歌单和 QQ 音乐登录凭证。App 同时忘掉这辆车的链接。
删除以后还会剩下这些，各自到期后删除：
- 两把密钥的哈希和这辆车的编号，30 天后删除；
- 邀请记录里这辆车的编号，那条邀请清理掉时删除；
- 已经写进服务器日志的行；
- 删除之前的云盘快照（如果有）。
退出 QQ 音乐登录（「设置 → 我的车」）：只删服务器上的登录凭证，车还在。
忘掉这辆车（在设置里往下翻）：只删手机上的链接。服务器上的车和数据都还在。
链接丢了，在 App 里删不了：发邮件给开发者，写上车名，请开发者删除。

点歌的朋友

还没放的歌，可以在点歌页撤回。
你的昵称会留在播放历史里，直到被新歌挤出最近 50 首，或者这辆车被删除。你导入过歌单的话，昵称也跟着导入的歌单存着，直到有人清除导入、导入新的歌单，或者这辆车被删除；导入成功时还会和歌单名一起写进日志。贴歌名列表导入的歌单就叫「你的昵称的歌单」，有人清除这个导入时，这个歌单名也会写进日志。想提前删掉，请司机删除这辆车，或者发邮件给开发者。
浏览器里记着的密钥、随机编号和昵称：清除这个网站的浏览器数据就行。

自己搭的服务器

你的 QQ 音乐登录在服务器的 /opt/car-jukebox/config.json 里，队列、播放历史和导入的歌单在 /opt/car-jukebox/data/ 里。
按帮助里的卸载步骤删掉整个 /opt/car-jukebox。只删 data/ 的话，QQ 音乐登录还留在 config.json 里。
最彻底的办法是直接释放这台云服务器，系统日志也一起没了。以前手动建过云盘快照的话，在云控制台里另外删掉。

儿童

本 App 不面向 13 岁以下儿童，也不会有意收集儿童的个人信息。

政策变更

这份政策有变化时，会更新这一页，并改上面的日期。

联系

对本政策有疑问，或者想删除数据，请联系：540393671@qq.com

Privacy Policy (English)

Car Jukebox (点歌台) is a jukebox for car rides: the driver's iPhone plays music while passengers request songs from a web page. It is made by an individual developer. The app, the jukebox server software and this website have no ads, no tracking, and no analytics or crash-reporting tools.

Who holds your data. Apart from loading audio and cover art directly from QQ Music (see Third parties), the app only talks to the jukebox server you set up. Whoever runs that server holds the data. Settings → 我的车 shows the server a car was created on.

A car created with the developer's invite is on the developer's server, 39.108.51.5 (Alibaba Cloud, mainland China). The developer holds that data, as described below.
A car created with a friend's invite is on that friend's server, and the friend holds the data.
On your own server, you hold the data.

In the last two cases nothing reaches the developer. Installing or updating your own server downloads the software from the developer's server. That server sees your server's IP address, keeps it in memory only for rate limiting, and does not log it. The installer also downloads Node.js and certbot from other sites, which see that IP address too (see Third parties).

On your phone.

The player link (server address and the car's player key) is stored in the iOS Keychain, with a flag saying whether the car was created with an invite on someone else's server, without iCloud Keychain sync. Both survive deleting the app, so a reinstall reconnects. They are included in encrypted backups, including iCloud Backup. 忘掉这辆车 (Forget this car) and 删除这辆车 (Delete this car) remove them.
The app also stores playback quality, the keep-alive switch, and a one-time request ID while you create a car.
Saving the QQ login QR code uses add-only Photos access. The app never reads your library.

Of these, only three things go to the car's server: the player key with every request, the quality setting with each play-link request (not stored), and the one-time request ID (see invite records below). The Keychain flag and the keep-alive switch stay on the phone. For a car created with an invite, the server stores just a hash of the player key; for the server owner's own car (such as yours on a server you set up), it keeps the key itself and prints it in the log at every start. While in use, the app also sends the car's server what is playing (saved as the car's current song, then in its play history), how far along it is and whether it is paused (these two are kept in memory only), playback errors (logged), and any car name, rules, playlist imports and queue changes you make. For cars created with the developer's invite, that server is the developer's.

Passenger web page.

The page uses no cookies. Browser local storage keeps the join key, a random ID, your nickname, and whether you were asked for one. The random ID goes to the server each time you open the page, add a song or withdraw one: it lets the server recognize the same phone (for the cartoon name and the requester ID) and is needed to withdraw your own songs. The Safari web player for drivers likewise keeps only the player key and its keep-screen-on switch.
Everyone in the same car sees the queue, the last 10 songs, requesters' nicknames and requester IDs. A requester ID is derived from the random ID with the car's own secret key: it shows which songs came from the same person, but cannot be turned back into the random ID or matched across cars, so nobody can act as you with it.
Search terms go through the server to QQ Music without anyone's login and are not logged. Results are kept in server memory by search term, shared by all cars and not linked to anyone, with no fixed retention: newer searches push them out (a few hundred at most), and a restart clears them.

Stored on the developer's server, per car. Cars are never deleted automatically.

The car name, rules, creation time and invite used, plus a random device number sent to QQ Music with play-link requests (one per car, unrelated to your phone), and a random key that derives requester IDs.
The join key and a hash of the player key.
The queue, the song now playing and the last 50 played songs, each with the requester's nickname, random ID and times. There is no time limit; older songs are pushed out by newer ones.
A cartoon name auto-assigned to everyone who opens the passenger page (used as their name if they set none), stored with their random ID and last-visit time, and released after 12 hours of inactivity (at most 200 per car; the longest-idle go first). Nicknames that passengers type stay in the queue and history, and in an imported playlist if they imported one.
An imported fallback playlist, with the importer's nickname.
Three timestamps: the last use by anyone, the last use by the driver, and the first use of the player link. The driver's last use decides when the login is renewed and the credential deleted (older cars use the last use by anyone, see below); the last use by anyone also shows the server owner which cars sit unused; the first use of the player link stops a retried car creation from issuing the link again once it has been used.
Only after the driver logs in: the driver's QQ Music login credential, which contains the QQ number and a refresh token valid for about two months. It is used only to fetch this car's play links and playlists and to renew the login. It is never shown to other users or written to logs. It is stored unencrypted, so the developer, as server administrator, can technically read it. It is deleted at once when the driver logs out or deletes the car. An hourly check also deletes it once the driver has not used the car for 60 days (only requests made with the player link count) or the QQ authorization has expired. Cars saved by older server versions recorded only the last time anyone used the car (passengers included), and that time is used instead. If no time is recorded at all (a damaged or missing file), the 60 days count from the server's start while it runs the car; when it does not run the car (for example, invites were switched off), only the expiry applies.

Invite records keep a hash and the first 3 characters of the code, the developer's note, use count, expiry, the IDs of the cars it created, and for 24 hours the app's one-time request ID. A record is removed 7 days after the invite expires or is revoked. Some damaged data files are renamed and kept for 30 days, then deleted: a car's queue and history file and its imported playlist (when the server loads the car), its QQ login credential (whether or not the server runs the car), and the invite records (while invites are on). Others are not renamed: a damaged file with the car's name and rules stops that car from loading and is left as it is; a damaged record of deleted cars stops old links from saying the car was deleted, and while invites are on, the next car deletion rewrites it in full (the damaged content is lost); otherwise it is left as it is. Deleting the credential from the server does not revoke it at Tencent. To revoke it, use QQ → 安全中心 → 授权管理.

Who can access it. People in other cars cannot. People in the same car see the car name, queue, nicknames and requester IDs, never each other's random IDs. The developer, as server administrator, can read every file. Data sits on Alibaba Cloud disks; if disk snapshots are enabled, deleted data remains in them until they expire.

Server logs. There is no access log. The run log contains:

car IDs and names;
admin events, including the developer's invite notes;
fallback and imported playlist names, and importers' nicknames;
playback errors: messages sent by the app, and why the server could not get a play link;
QQ login, renewal and logout results;
what the hourly cleanup deleted (expired credentials, leftover folders, damaged files older than 30 days), and any file it could not read or delete;
the IP address (an IPv6 /64) of any address locked out for too many wrong keys or invite codes.

For cars created with an invite, the server does not write credentials, keys, QQ numbers or QQ nicknames to the log. App-reported playback errors are logged as sent; if one happens to contain a QQ number or credential, common forms (cookie and API fields, o0-prefixed QQ numbers) are masked first, but unrecognized forms are not. The server owner's own car differs: its player and join links, keys included, are printed at every start, and the owner's own QQ nickname is logged on QR login. Logs live in the systemd journal with the system's default settings and no set retention period; the oldest entries are dropped when it reaches its size limit. If rsyslog is installed (usual on Ubuntu), the same lines also go to /var/log/syslog, which the system rotates. Per-IP rate-limit counters stay in memory only, stop counting after at most 12 hours and are cleared hourly.

Third parties.

QQ Music (Tencent): search, lyrics, playlists, play links and QR login go through the server. The app streams audio and loads cover art directly from QQ Music's servers, and the passenger page loads covers from them too, so Tencent sees your device's IP address. No referrer is sent. Tencent's privacy policy applies. The app is not affiliated with Tencent.
Other music platforms: importing a NetEase Cloud Music, Kugou, Kuwo, Soda Music, Apple Music or Spotify link makes the server read that public playlist's titles and artists.
Alibaba Cloud hosts the developer's server.
Let's Encrypt issues the HTTPS certificates.
When you install your own server, the installer downloads Node.js from npmmirror.com and certbot from mirrors.aliyun.com (Alibaba Cloud), and other system packages from the server's own apt sources; these sites see your server's IP address. Nothing is downloaded again once a recent enough version is installed.
This site is hosted on GitHub Pages, which sees visitors' IP addresses. The site itself uses no cookies, scripts or external fonts.
Apple may share aggregated usage and crash reports with the developer if you opted in on your iPhone.

Deleting your data.

Settings → 我的车 → 删除这辆车 (Delete this car), then type the car name. This deletes all of the car's files at once, including the QQ credential, and the app forgets the link.
Some traces remain until they age out: the key hashes and the car ID for 30 days (so old links can say the car was deleted and new cars never reuse them), the car ID in invite records until those are cleared, lines already written to the logs, and any earlier disk snapshots.
退出 QQ 音乐登录 (Log out of QQ Music) deletes only the credential. 忘掉这辆车 (Forget this car) only removes the link from your phone.
A passenger's nickname stays in the play history until it is pushed out of the last 50 songs or the car is deleted. A passenger who imported a playlist is also named in it until the playlist is cleared or replaced or the car is deleted, and in that import's log line. A pasted song list is named after the importer, so clearing it logs their nickname too.
If you lost the link, or you are a passenger who wants your nickname removed, email the developer.
On a self-hosted server, the QQ login is in /opt/car-jukebox/config.json and everything else is in /opt/car-jukebox/data/. Remove the whole /opt/car-jukebox, or release the server (delete any disk snapshots separately).

Children. The app is not directed to children under 13.

Changes. If this policy changes, this page and the date at the top will be updated.

Contact. 540393671@qq.com