WidgetStore · 组件世界

English · 简体中文版本 / 隐私政策

Privacy Policy

Effective date: 2026-11-18

We care about your privacy. This policy explains what WidgetStore collects, how we use it, and your rights.

1. Information we collect

Account information: sign-in method (WeChat, email or phone), nickname, avatar, email address or phone number.

Verified email: after signing in, you'll be asked to add and verify an email address. We use it only for account security (such as recovering your account and confirming it's you) and for important account or service notices. It is never shown publicly or used for marketing. Verification codes are stored only as hashes and expire after 10 minutes.

Usage data: the widgets you create and their settings, usage counts, membership period and order history.

Connected services: when you connect Notion or Obsidian, we store the authorization tokens and workspace details needed to provide the feature.

Connect GitHub (not used for sign-in): when you connect GitHub under Settings → Connected accounts, we receive your GitHub user ID, username, name, avatar, bio, follower count and public repo count, and store the access and refresh tokens GitHub issues to us (encrypted, used only on our servers). By default we request read access to your public profile and contributions only (read:user), and use it only to show your public GitHub data (contribution calendar, total stars, top languages, public repos) in your widgets, your page and My Data. Only if you separately turn on "Show private contribution counts in widgets" and authorize repo access again do we read daily counts that include private contributions; we never read code or show private repo names. Widgets and your page are public, so this data is visible to anyone who views them. If you turn on "Sync contributions to My Data daily", your daily contribution counts are written to a table in your My Data. You can disconnect at any time in Settings → Connected accounts — we revoke our access on GitHub and delete the tokens — or revoke it under Settings → Applications on GitHub.

Calendar subscriptions: when you add a calendar link under Settings → Connected accounts → Calendar subscriptions (such as Google Calendar's secret address in iCal format, an iCloud public calendar or an ICS link published from Outlook), we store the link encrypted, show only its host and last 4 characters, and never send the full link back. Our servers read the calendar from that link (read-only: we never create, change or delete events) and save only your subscription settings (name, color, visibility), not your events; events are cached for about 20 minutes and shown only to you while you're signed in (Focus, your start page, the browser extension popup, AI apps you connect). Widgets: calendar widgets in public places include only the calendars you set to "Show in public widgets" and show busy times only, unless you turn on "Show event titles in public widgets" in Settings and choose to show titles in that widget; locations and links are never public. Built-in holiday and solar-term calendars come from public government data. When you remove a calendar we delete its link immediately.

Connect Todoist / Linear (not used for sign-in): when you connect Todoist or Linear under Settings → Connected accounts, we receive your user ID, name, avatar and time zone (and, for Linear, your workspace name), and store your credentials encrypted, used only on our servers: for Todoist, the access and refresh tokens Todoist issues to us; for Linear, the personal API key you paste yourself (checked with Linear before it is saved, afterwards shown only as its last 4 characters and never sent back to your browser). We do not store your email address from them. What we read: your Todoist tasks for today / overdue (or the project or filter you choose) and the Linear issues assigned to you (in the states, team and cycle you choose). Task titles, due dates, priorities and states are shown only to you while you're signed in (Focus to-dos, your start page, the browser extension popup, AI apps you connect) and are cached for 90 seconds to 5 minutes only; we don't keep task content. What we write back: only when you check a task off in WidgetStore do we complete it in Todoist or move the issue to a Done state in Linear; only when you add a task in WidgetStore do we create it in Todoist or create an issue assigned to you in Linear; and only if you turn on "Log focus time on tasks" do we add a comment containing the number of minutes you focused. Widgets: task widgets placed in public places such as Notion or your page show counts only, unless you turn on "Show task titles in public widgets" in Settings and choose to show titles in that widget. If you turn on "Sync daily completions to My Data", the number of tasks you completed each day (no titles) is written to a table in your My Data. You can disconnect at any time — we revoke the Todoist tokens and delete the link (you delete a Linear API key yourself under Security & access in Linear) — or revoke our access in Todoist's app authorization settings.

Sign in with Google: when you choose Continue with Google or connect Google in Settings, we receive from Google your Google account's unique ID (sub), email address (used only if Google has verified it), name and profile picture. We use them to sign you in, find or create your account, and show the connected Google account under Connected accounts; a new account uses this email as its account email. We never receive your Google password and do not access Gmail, Drive, Contacts or any other Google data. You can disconnect at any time in Settings → Connected accounts, or remove access under Third-party apps & services in your Google Account. When you're signed out, some pages may show Google's One Tap prompt; if you've signed in with Google before and have one Google account, you may be signed in automatically — we tell you on the page and you can undo it. After you dismiss the prompt it stays away for a while, and after you sign out we won't sign you in automatically again until you choose Google yourself.

Device and access data: browser type, language, pages visited, referrer and error logs, used for analytics and troubleshooting.

Anonymous app usage statistics (from November 2026, desktop app, Android app, iOS app and browser extension): at most once a day per device, we receive the app version, operating system and version, processor architecture, interface language, install channel, time zone, whether you are signed in (not which account), how many times each section was opened, and whether the app crashed or quit unexpectedly last time (only the code location of the error). The device ID is a random number created on first launch, not a hardware identifier, and is not linked to your account. No content, URLs, file names, messages or passwords are ever included. Per-device records are kept for 90 days; after that only daily totals remain. You can turn this off at any time in each app's settings (desktop: Settings → Account & sync; Android: Me → About; iOS: Me → Settings; extension: Settings → Privacy).

“My IP” widget: the widget asks our check endpoint (widgetstore-edge on Cloudflare) and this site's Cloudflare edge, from your browser, for your public IP and the network details Cloudflare provides (country / region / city, time zone, ISP and ASN, connection protocol), and shows them only to you, the person viewing the widget. We don't log or store this information or link it to your account; to prevent abuse the endpoint only keeps a per-minute counter in memory (not the IP itself), cleared after a minute.

Payment information: payments are handled by Creem. We only receive the order ID, product, amount and payment status, never your card details.

2. How we use information

To provide, maintain and improve the Service, such as saving and displaying your widgets and applying membership benefits.

To process orders, refunds and support requests.

To understand product usage and find and fix problems.

To send service or account notices when necessary.

3. Service providers

We use the following providers to run the Service: Tencent CloudBase (accounts and data storage), Cloudflare (payment and sign-in service hosting; Turnstile bot protection on the sign-in page, to stop abuse of verification codes; R2 object storage for music files and cover art in Music, Asia-Pacific region), Render (website hosting), Creem (payment processing), Mixpanel (analytics), Resend (verification codes and other system emails, sent without tracking pixels; it also receives emails you send to our support address — we keep the sender, subject and text to handle your request, delete them under the same rules as feedback sent on the site, and record only the names and sizes of attachments), Google (Sign in with Google, only when you choose to sign in with or connect Google), GitHub (only when you connect GitHub, to read your public profile and contributions), and Todoist (Doist) and Linear (only when you connect them, to read your tasks and write back the changes you make).

These providers process your data only as needed to provide their services. We do not sell your personal information.

4. Cookies and local storage

We use browser local storage for sign-in state, language preference and cached data, and analytics tools may use cookies to distinguish visits. You can clear this data in your browser, but you may need to sign in again.

5. Storage and retention

Account and widget data are stored on Tencent Cloud (Shanghai, China). We keep this data while your account is active. After account deletion we delete or anonymize it within a reasonable period, except records such as orders that we must keep by law. Music files and cover art in Music are stored in Cloudflare R2 (Asia-Pacific region); see section 10.

6. Your rights

You may access, correct or delete your personal information, or ask us to delete your account. Email support@widgetstore.net and we will respond within 15 business days.

7. Children

The Service is not directed to children under 14. If we learn we have collected a child's information, we will delete it promptly.

8. Browser extension

The WidgetStore browser extension (Chrome, Microsoft Edge, Firefox) only communicates with widgetstore.net. It does not read your browsing history, does not run on other websites (unless you turn on the vault's login-field icon, see next paragraph), and contains no ads or third-party analytics.

Passwords & authenticator (from 1.2.0): the vault unlocks and decrypts in the extension's own page, end-to-end encrypted like on the website — we only receive ciphertext. While unlocked, the vault key is kept only in the browser's session storage (memory; deleted when the browser closes or the vault auto-locks), out of reach of web pages. Only if you turn on "Show the WidgetStore icon next to login fields" and allow the extension to read sites does it run a script on https pages that looks only at input-field attributes (type, name, placeholder) to show an icon in login fields. It fills your username, password and code only when you click the icon and the address matches one you saved. When you submit a new password it is held in your browser for up to 2 minutes to ask whether to save it; the vault opens only if you click Save. Page content and addresses are not sent to us; turning the option off removes the permission.

Sign-in: after you confirm the connection on our website, the extension receives a one-time code and exchanges it for a session (the refresh token is kept in the browser's extension storage and the access token only in session storage). It lasts 30 days and you can disconnect at any time in the extension's settings. The extension never handles your password.

Data the extension sends to us: the to-dos, habit check-ins, completed focus sessions and daily check-ins you make in the extension (the same as Focus space and check-in on the website, saved to your My Data); the address and title of a page when you click “Save to start page” (written to your start page by the website's save page); the selected text or page title when you click “Add to to-dos”; and what you type after the ws keyword in the address bar (used only to search the widget catalog and not stored with your account).

Data kept only on your device: extension settings, a snapshot of your start page as it last looked (layout, wallpaper, site links and widget content, so new tabs open instantly and work offline), the focus timer and changes waiting to sync. Removing the extension or clearing its cache in settings deletes them.

Bookmarks and most visited sites (optional, from version 1.0.2): the extension asks for permission to read them only when you click “Read bookmarks” or “Most visited” on your start page (your browser asks you to confirm), and reads them only when you click. What it reads is passed only to the start page you're using to show you; neither the extension nor our servers store it. Only the sites you tick and import (their address and name) are saved as part of your start page. For preview icons our icon service receives only the site's domain name, never the full address, and doesn't log it. You can take back both permissions any time in the extension settings. When you import a bookmarks HTML file on the website, the file is read in your browser and never uploaded.

Popup and settings (from version 1.1.0): the toolbar popup and the extension settings are pages on widgetstore.net shown inside the extension, so opening them requests those pages from us like visiting the website. When you open the popup, the current page's address and title are only handed to the popup to show “Save this page” and aren't sent to us unless you click Save. The extension also periodically downloads a configuration file from widgetstore.net that only contains feature switches and menu labels; the request carries no personal information.

Permissions the extension requests: storage (settings and cache), alarms (ending the focus timer on time), notifications (focus and break reminders), context menus, active tab (reads the current page's address and title only when you click the extension), search (the new tab's search box uses your browser's default search engine), and access to widgetstore.net (showing your start page, syncing data and connecting your account). Optional permissions: bookmarks and most visited sites, requested and read only when you import (see above); scripting (from 1.2.0, only to inject the extension's own vault autofill script); optional access to https sites (requested only when you turn on the vault's login-field icon, see above). We do not sell this data or use it for advertising.

Android app (net.widgetstore.app, from November 2026): Home, Library, Focus and Me are native screens, while the editor, dashboard and similar pages open widgetstore.net web pages inside the app; it signs in the same way as the browser extension (a one-time connection code is exchanged for a session; the refresh token is encrypted with the phone's system keystore, stays on that phone and is excluded from system backups). When you sign in through your browser, the one-time code that brings you back to the app is also bound to a secret only that phone knows, so another app that intercepts it can't use it. So it works offline, the app uses your session to sync your widget list, the widget library, tasks, agenda (from yesterday to 8 days ahead), focus sessions, habits and goals, and keeps them in the app's private storage on that phone (excluded from system backups); changes made offline are sent to us when you're back online. Widget images shown on your home screen are drawn and cached on the phone, and you can hide titles so widgets only show counts. Permissions: internet, network state, notifications (focus timer), camera (QR sign-in is processed on the phone without saving or uploading scan images; video is used when you start or answer a video call), microphone (when you start or answer a voice or video call) and foreground playback (ambient sound keeps playing with the screen locked; the sound is generated on the phone), foreground data sync (only to stay connected while you are in a Focus Room; this service itself does not capture camera or microphone input) and Live Updates (from Android 16, the focus timer, Focus Rooms and update downloads show on the lock screen and status bar; you can turn this off in system settings). Apart from the optional features described below, it doesn't read contacts, photos or location, and it has no ads or third-party analytics. When you use the app to sign in on a computer by QR code, we show you that computer's browser, system, masked IP and approximate city so you can confirm; the request is kept for a few minutes at most and deleted once used. When you share a link to WidgetStore from another app, its URL and title are saved to your dashboard's Read later list (you can undo this). Logging out deletes the session, the local database, web and image caches and widget images on that phone. The following features (from 1.2.0) are off by default and only start when you turn them on: phone calendar and contact birthdays (read on the phone only; events and contacts are never uploaded); health (steps, sleep and resting heart rate via Health Connect) and screen time (screen-on time and unlocks), calculated on the phone — only if you also turn on “Upload daily totals” are a few numbers per day saved to your My Data, never raw records or which apps you used; in couple & family spaces, the location you choose to share (city-level or precise) is kept as a single latest point for 12 hours with no history; automatic status (home / work / new city) is decided on the phone and only the status is uploaded; photos you send are compressed on the phone and kept for at most 48 hours, at most 6 per space; nudges, moods and anniversaries are visible only to members of the same space. Any member can leave at any time, which deletes their location, mood and photos in that space.

Mobile web calls and location: permissions are requested when you actively use the relevant feature and remain subject to system controls. Android grants approved camera, microphone or location (accuracy follows system permission; no additional precise or background access is requested) access only to foreground HTTPS pages on our site; leaving the page or moving to the background stops its capture. iOS calls also require system confirmation, and camera and microphone capture stops in the background. This update does not add iOS web location permission. Calls use encrypted WebRTC transport; location is sent only through the sharing feature you choose, never for background tracking.

Passwords & authenticator: the vault unlocks and decrypts in a local page bundled with the app (end-to-end encrypted; we only receive ciphertext). Fingerprint / face unlock uses the biometric permission, and the local unlock secret is protected by the phone's keystore and never leaves the phone. Only if you choose WidgetStore as your autofill service in system settings does "Fill with WidgetStore" appear in login fields of other apps and browsers; it fills only after you tap it and pick a login, and asks to save only when you submit a new password. So that it can list the right logins next to a field even while the vault is locked, the app keeps an index on this phone without passwords or authenticator secrets (names, usernames, addresses / app package names), encrypted with the phone's keystore and excluded from backups; it is deleted when you forget the device, clear the vault or sign out. All of this happens on the phone; field contents, addresses and this index are not sent to us.

Focus Rooms (from November 2026): messages go directly between devices, end to end — they never pass through our servers and are never stored. Setting up the connection does go through our server, and people in the same room can see each other's IP address. In detail: chat, status (focusing / on a break / away), today's focus minutes, the "working on" line if you choose to show it, and cheers are sent device to device over WebRTC data channels (DTLS-encrypted), so our servers never receive them; chat lives only in your browser's memory, disappears when you leave the room and is not stored anywhere (including your device). To set up the connection, our server (Cloudflare) relays connection details (which include IP addresses) and keeps track of who is in the room, but does not store those connection details; a room only stores its host, rhythm, locked / muted settings, removed accounts, and the names and random IDs of people who joined (used to verify reports), and is deleted when it's closed or after 7 days without anyone joining. To discover your public address, your browser contacts public STUN servers (Xiaomi, Mango TV, Bilibili, Cloudflare), which can see your IP address. From November 14, 2026, if two devices can't connect directly (for example when both are behind a mobile carrier's NAT), the connection is relayed through Cloudflare's TURN relay servers: content stays end-to-end encrypted (DTLS), so the relay can't read or store it and only sees both IP addresses and the amount of traffic. When a direct connection works, no relay is used. The same applies to Messages below. Your block list only stores the other person's random ID and name. When you report someone, only the messages you choose to attach are sent to us, to handle the report. At the end of each focus session, the minutes you were actually present are logged to your own Focus space as usual. Only join rooms with people you trust. Grow together: your energy, the virtual trees you plant and the co-planter names you choose to add are stored only in your own My Data (the forest table); the room's tree, energy balls and leaves are only sent between devices in the room.

Messages (from November 2026; end-to-end encrypted with offline delivery from 15 November 2026): you can only chat with mutual connections (members of the same family & friends space, or focus buddies you both added in a focus room). Messages are encrypted on your device and only your devices can read them: each device has its own key pair; the private key never leaves that device and can't be exported, and the public key is registered on our server (Cloudflare) so others can encrypt to it. If the other person is online, the encrypted message is passed straight to them; if not, the encrypted message is held on our server for at most 7 days and deleted as soon as each of their devices receives it (or after 7 days). We can't see the content — only who sent an encrypted message of what size to whom and when (not logged; it exists only while the message is held). Your chat history (text, images, files) is stored only on your own devices (browser or app storage); you can export or clear it at any time, and we can't recover it. Files and larger images are sent directly between the two devices while both are online (WebRTC, DTLS-encrypted, via Cloudflare's TURN relay if needed — the relay can't see the content), so the other person can see your IP address. Our server only knows you're online while Messages (or the desktop app) is open, and tells your contacts (you can go invisible). We also store your focus buddy list, pending buddy requests and the list of your device public keys; you can remove buddies, block people or remove devices at any time. If you report someone, only the messages you choose to attach are sent to us.

Group details and invitations: group names, member lists, announcements and member-chosen group nicknames are stored on the server and shared with current members. They are server-visible metadata, separate from encrypted chat bodies. Human members actively create invitations; the server stores only token hashes and expiration times. A recipient must sign in and explicitly confirm joining. Private group labels, saved groups and name-display preferences stay on the current account’s local device.

Spark transfers and gift packets: to fulfill gifting transactions, reconcile balances and accounts, and handle refunds and disputes, we store the transaction ledger, balances, participating accounts (sender, designated recipient and actual claimants), amounts, fees, creation and action times, and claim, decline, expiry and return status on our servers. This transaction data is processed by the server and is separate from end-to-end encrypted chat content. Chats between people carry only an end-to-end encrypted transaction reference; opening a card separately requests transaction details after server-side authorization. Unsending or deleting the chat reference, or clearing local chat history, does not cancel the transaction, trigger a refund or delete the server ledger. Transaction records follow this policy’s data retention and rights provisions, rather than the temporary chat ciphertext retention period of delivery or at most seven days.

9. AI apps and the open API

You can connect AI apps such as Claude, ChatGPT and Cursor (via MCP) or your own scripts (via personal API tokens) to your account. A connection exists only after you click Allow on our consent page or create a token yourself; you choose its permissions and can disconnect or revoke it at any time in Settings → API & AI connections.

When you ask, an AI app reads the data you allowed (for example widget settings, your personal page, start pages, to-dos and My Data records). That content becomes part of your conversation with the app and is handled under that app's own privacy policy. We never provide your data to anyone for model training.

We store hashes of tokens and authorizations (never the tokens themselves), the app name, permissions, creation and last-used times, daily call counts, and an activity log of each change (who, when, what changed and the content before and after, so you can review and undo it). Activity logs are kept with your account and deleted when you delete your account. AI apps cannot delete your data or access your account, payments or membership.

10. Music

Music files (from November 2026): the music files and cover art you upload to Music (/music) are stored in a private Cloudflare R2 object storage bucket in the Asia-Pacific region, with no public links. Track details such as title, artist, album, duration, lyrics, playlists and your usage are stored on Tencent Cloud with the rest of your account data. When you upload, your browser computes the file's SHA-256 fingerprint and reads its tags and cover art on your device, and the file goes straight from your browser to R2; our servers only issue short-lived upload and playback addresses and never relay, transcode or analyze the audio. Playback addresses are issued only to accounts that have the song in their library, and expire after a few hours.

Deduplication: a file with exactly the same content (the same fingerprint) is stored only once across the whole service. If someone else has already uploaded the identical file, your library simply gets an entry pointing to it, and your usage still counts the song's full size. Deduplication never exposes anyone's library to anyone else: other people can't see which songs you have or find out who else uploaded a given file, and only accounts that have a song in their library can get its playback address. So that nobody can “claim” a file just by knowing a fingerprint published online, when the identical file already exists your browser must answer with a few short pieces of your file that we pick at random (proof of possession). A wrong answer cancels that upload, and no upload or playback address is given before the proof passes.

Retention and deletion: when you delete a song, we immediately delete your entry for it and give back the space; if the song is listed in the Originals Market, it is withdrawn too. The stored file is deleted once no account refers to it any more (we re-check before deleting); if other accounts uploaded the same file, it is kept for them but is no longer linked to you in any way. Unfinished uploads are cleared within a day. When you delete your account, your library, playlists, listening history, market listings and sharing settings are deleted with it, and files are handled as above. Songs you download for offline listening are kept only in your browser; you can remove the download in Music or clear your browser data.

Listening history: a play counts once you've listened for 30 seconds or half the song, whichever comes first. We record each song's total plays, listening time and when you last played it; daily totals (plays, minutes and number of songs) and each song's plays that day; and your recent plays and what you're listening to now. Plays are queued on your device and uploaded in batches, and nothing is recorded when you're not signed in (for example, when listening in the Originals Market). By default only you can see this history (Music's stats and Year in Music, and AI apps you connect). We also create a Listening system table in your My Data (one row per day: plays, minutes, songs), which doesn't count toward your My Data quota.

Sharing switches: Music's settings have four switches (now playing, recent plays, top songs, and listening time and heatmap), all off by default. Only the items you turn on are made available to music widgets you place in public places such as Notion or your page; for items that are off, our servers return nothing at all. Widgets only receive song titles, artists and numbers, never files, playback addresses or cover art. The public version of Year in Music (/music/wrapped/<random ID>) shows only what you tick, is kept out of search engines, and can be turned off at any time.

Deleting listening history: you can delete the Listening table in My Data at any time (Music's own stats aren't affected, and today's row is recreated the next time you listen). Deleting a song doesn't delete its play statistics. To delete all play statistics in Music, email support@widgetstore.net; they are also deleted when you delete your account.

Originals Market: when you submit a song from your library to the Originals Market, you declare that you wrote and recorded it yourself and have the right to publish it. To handle copyright disputes, we keep the time of that declaration, the version of the market rules you agreed to and a hash of your IP address at the time (not the IP address itself). Approved works can be played by anyone; the page shows the title, artist, cover art and the name on your public personal page (nothing if you don't have one), and never your account ID. A work's play count is only a running total: we don't record who listened, and we don't tell you or anyone else. Reporting doesn't require signing in: we keep the reason, details, the email address the reporter gives (required for copyright complaints) and a hash of the reporter's IP address (to stop duplicate reports). Only our administrators see them, to handle the report and contact the people involved.

Send to a friend (peer-to-peer): when you send a song to a friend in Messages, the file goes directly from your browser to their device over a WebRTC data channel (DTLS-encrypted), never through our servers, and no link is created. As with Messages, the other person can see your IP address during a direct connection; if a direct connection isn't possible, it is relayed through Cloudflare's TURN servers, which can't see the content and only see both IP addresses and the amount of traffic (see section 8). The song your friend receives stays only in the page's memory; only if they choose to save it to their own Music is it stored as their own upload, in their library and counted against their quota.

11. Passwords and Authenticator (the vault)

End-to-end encryption (from November 2026): the passwords, two-factor codes (authenticator secrets), secure notes, cards and identities you keep in Passwords (/vault) are encrypted on your device with a key derived from your master password together with an Account Key that is stored only on your devices (Argon2id + AES-256-GCM). Our servers store only the ciphertext. Names, websites and usernames are encrypted too. We can't read this content and can't recover it for you: if you forget your master password and lose your Recovery Kit, the vault can't be opened.

What we can see: each item's random ID, whether it's a password-type item or an authenticator code (so limits can be counted separately), the ciphertext size, when it changed, and whether it's in Recently deleted. We record a few security events (vault created, master password changed, exported, vault closed), which you can see in your Account Center's security log, but never the content. AI apps, MCP and the open API can't read the vault.

Breach checks: when you use the breach check in Password health, your browser sends the first 5 characters of each password's SHA-1 hash directly to Have I Been Pwned (api.pwnedpasswords.com) using k-anonymity; it never sends the password itself or the full hash. You can turn this off in the vault's settings. QR codes you scan and files you import are processed on your device and never uploaded.

Retention and deletion: deleted items stay in Recently deleted for 30 days and are then permanently deleted; closing the vault deletes all items and keys. If you forget your master password and choose to empty the vault, its contents are moved out of your account and permanently deleted after 30 days. Everything is deleted when you delete your account.

12. Changes

We may update this policy. Updates will be posted on this page with a new effective date.

13. Contact

For privacy questions, contact support@widgetstore.net.

隐私政策

生效日期:2026-11-18

我们重视您的隐私。本政策说明 WidgetStore(组件世界)收集哪些信息、如何使用以及您享有的权利。

1. 我们收集的信息

账号信息:登录方式(微信、邮箱或手机号)、昵称、头像、邮箱或手机号。

绑定邮箱:登录后需要绑定并验证一个邮箱。我们只用它保障账号安全(例如找回账号、确认是您本人操作)和发送与账号或服务相关的重要通知,不会公开显示,也不会用于营销推广。验证码只以加密摘要形式保存,10 分钟后失效。

使用数据:您创建的组件及其配置、使用数量、会员有效期、订单记录。

第三方连接:当您连接 Notion 或 Obsidian 时,我们会保存为提供功能所必需的授权凭证和工作区信息。

关联 GitHub(不能用于登录):当您在「设置 → 账号关联」关联 GitHub 时,我们从 GitHub 获取您的 GitHub 用户 ID、用户名、名字、头像、简介、关注者数和公开仓库数,并保存 GitHub 发给我们的访问令牌和刷新令牌(加密保存,只在我们的服务器上使用)。默认只申请读取公开资料和贡献(read:user),只用于在您的组件、个人主页和「我的数据」里显示您的公开 GitHub 数据(贡献日历、Star 合计、常用语言、公开仓库);只有在您单独打开「组件里显示私有贡献数」并再次授权 repo 权限后,才会读取包含私有贡献的每日数量,我们不读取代码、不显示私有仓库名。组件和个人主页是公开的,以上数据会对看到它们的人可见。打开「每天同步贡献到我的数据」时,每天的贡献次数会写进您「我的数据」里的一张表。您可以随时在「设置 → 账号关联」断开,我们会撤销在 GitHub 上的授权并删除令牌;也可以在 GitHub 的「Settings → Applications」里撤销。

日历订阅:当您在「设置 → 账号关联 → 日历订阅」添加日历链接(如 Google 日历的「iCal 格式的私密地址」、iCloud 公开日历、Outlook 发布的 ICS 链接)时,我们把链接加密保存,界面上只显示网址开头和末尾 4 位,从不回传完整链接。我们的服务器按这个链接读取日历(只读,不会新建、修改或删除日程),只保存订阅设置(名称、颜色、是否显示),不在数据库里保存日程内容;日程只做约 20 分钟的缓存,只显示给登录的您自己(专注空间、起始页、浏览器扩展弹窗、您连接的 AI 应用)。组件:放在公开位置的日历组件只包含您打开了「在公开组件里显示」的日历,默认只显示忙碌时间段;只有您在设置里打开「允许在公开组件里显示日程标题」并在组件里选择显示标题时才显示标题,地点和链接从不公开。内置的节假日 / 节气日历来自政府公开数据。删除日历后我们立即删除它的链接。

关联 Todoist / Linear(不能用于登录):当您在「设置 → 账号关联」关联 Todoist 或 Linear 时,我们从对方获取您的用户 ID、名字、头像、时区(Linear 还有工作区名称),并加密保存凭据(只在我们的服务器上使用):Todoist 是授权后对方发给我们的访问令牌和刷新令牌,Linear 是您自己粘贴的个人 API Key(保存前先向 Linear 验证,之后只显示最后 4 位,从不回传给浏览器)。不保存您在对方的邮箱。读取:Todoist 里今天 / 已逾期的任务(或您选的项目、筛选),Linear 里分配给您的 Issue(您选的状态、团队、周期);任务标题、到期日、优先级、状态只在您登录后显示给您自己(专注空间待办、起始页、浏览器扩展弹窗、您连接的 AI 应用),我们只做 90 秒到 5 分钟的短缓存,不长期保存任务内容。写回:只有您在组件世界里勾选完成时,我们才在 Todoist 完成该任务 / 在 Linear 把 Issue 移到「完成」状态;只有您在组件世界里添加任务时,才在 Todoist 新建任务 / 在 Linear 新建分配给您的 Issue;只有您打开「把专注时间记到任务上」时,才在任务上加一条只含专注分钟数的评论。组件:放在 Notion、个人主页等公开位置的任务组件默认只显示数量,只有您在设置里打开「允许在公开组件里显示任务标题」并在组件里选择显示标题时才显示标题。打开「每天同步完成数到我的数据」时,每天完成的任务数量(不含标题)会写进「我的数据」的一张表。您可以随时断开,我们会撤销 Todoist 的令牌并删除关联记录(Linear 的 API Key 由您在 Linear 的 Security & access 里删除);也可以在 Todoist 的应用授权设置里撤销。

用 Google 登录:当您选择「使用 Google 账号登录」或在设置里关联 Google 时,我们从 Google 获取您 Google 账号的唯一标识(sub)、邮箱地址(仅在 Google 已验证时使用)、姓名和头像,用于登录、找到或创建您的账号,并在「账号关联」里显示已关联的 Google 账号;新账号会把这个邮箱作为绑定邮箱。我们不会获取您的 Google 密码,也不会访问 Gmail、云端硬盘、通讯录等其他 Google 数据。您可以随时在「设置 → 账号关联」解除关联,或在 Google 账号的「第三方应用和服务」里撤销授权。未登录时,部分页面可能会显示 Google 的「一键登录」提示(One Tap);如果您以前用 Google 登录过且只有一个 Google 账号,可能会自动登录,页面会提示并可以撤销。关闭提示后一段时间内不会再显示;退出登录后不会再自动登录,直到您再次主动用 Google 登录。

设备与访问信息:浏览器类型、语言、访问页面、来源与错误日志,用于统计分析和排查问题。

客户端匿名使用统计(2026-11 起,电脑版、Android App、iOS App、浏览器扩展):每台设备每天最多发送一次,内容只有客户端版本、系统和版本号、处理器架构、界面语言、安装渠道、时区、是否已登录(不含账号)、各功能被打开的次数,以及上次是否崩溃或异常退出(只有出错的代码位置);设备编号是第一次运行时随机生成的,不是硬件标识,不和账号关联;不包含任何内容、网址、文件名、消息或密码。明细保存 90 天,之后只保留按天汇总的数字。您可以在各客户端的设置里随时关闭(电脑版:设置 → 账号与同步;Android:我的 → 关于;iOS:我的 → 设置;扩展:设置 → 隐私)。

「我的 IP」组件:组件在您的浏览器里向我们的检测接口(Cloudflare 上的 widgetstore-edge)和本站的 Cloudflare 节点请求您的公网 IP 和 Cloudflare 提供的网络信息(国家 / 地区 / 城市、时区、运营商和 ASN、连接协议),只显示给正在看组件的您自己。我们不记录、不保存这些信息,也不把它和账号关联;检测接口为防滥用只在内存里按分钟计数(不保存 IP 本身),一分钟后清空。

付款信息:付款由 Creem 处理,我们只接收订单号、商品、金额和付款状态,不会获取您的银行卡信息。

2. 我们如何使用信息

提供、维护和改进本服务,例如保存和展示您的组件、开通会员权益。

处理订单、退款和客户支持。

统计产品使用情况,发现并修复问题。

在必要时向您发送与账号或服务相关的通知。

3. 第三方服务商

为提供本服务,我们使用以下服务商处理数据:腾讯云云开发(账号与数据存储)、Cloudflare(支付与登录服务托管;登录页的 Turnstile 人机验证用于防止验证码被滥发;R2 对象存储:音乐空间的音乐文件和封面,亚太地区)、Render(网站托管)、Creem(付款处理)、Mixpanel(访问统计)、Resend(发送验证码等系统邮件,邮件中不含追踪像素;接收您发到客服邮箱的邮件——我们会保存发件人、主题和正文用于处理您的反馈,删除规则与站内提交的反馈相同,附件只记录文件名和大小)、Google(「使用 Google 账号登录」,仅在您选择用 Google 登录或关联时)、GitHub(仅在您关联 GitHub 时,读取公开资料和贡献)、Todoist(Doist)和 Linear(仅在您关联时,读取任务并按您的操作写回)。

这些服务商仅在提供相应服务所需的范围内处理您的数据。我们不会出售您的个人信息。

4. Cookie 与本地存储

我们使用浏览器本地存储保存登录状态、语言偏好和缓存数据,统计工具可能使用 Cookie 区分访问。您可以在浏览器中清除这些数据,但可能需要重新登录。

5. 数据存储与保留

账号与组件数据存储在腾讯云(中国上海地域)。在您保留账号期间,我们会保存相关数据;账号注销后,我们会在合理期限内删除或匿名化处理,法律要求保留的订单等记录除外。音乐空间的音乐文件和封面保存在 Cloudflare R2(亚太地区),见第 10 条。

6. 您的权利

您可以访问、更正或删除您的个人信息,也可以要求注销账号。请发送邮件至 support@widgetstore.net,我们会在 15 个工作日内处理。

7. 未成年人

本服务不面向 14 周岁以下的儿童。如发现误收集了儿童信息,我们会尽快删除。

8. 浏览器扩展

组件世界浏览器扩展(Chrome、Microsoft Edge、Firefox)只和 widgetstore.net 通信,不读取你的浏览记录,不在其他网站上运行(你在保险库里打开「网页登录框旁的图标」时除外,见下一段),不含广告和第三方统计。

密码与验证器(1.2.0 起):保险库在扩展自己的页面里解锁和解密,和网站一样端到端加密,我们只收到密文。解锁后保险库密钥只放在浏览器的会话存储里(内存,浏览器关掉或自动锁定后删除),网页里的脚本读不到。只有你在保险库设置里打开「在网页登录框旁显示组件世界图标」并允许读取网站时,扩展才在 https 网页上运行一个只看输入框属性(类型、名称、提示文字)的脚本,在登录框旁显示图标;你点了图标、并且网址和你保存的网址匹配时才填入用户名、密码和验证码;你提交新密码后,它在你的浏览器里暂存最多 2 分钟,问你要不要保存,你点了「保存」才打开保险库。网页内容和网址不会发给我们;关掉这个选项会收回权限。

登录:你在网站上确认连接后,扩展收到一次性的连接凭证并换成登录状态(刷新凭证保存在浏览器的扩展存储里,访问凭证只保存在内存级存储里),30 天有效,可以随时在扩展设置里断开。扩展从不接触你的密码。

扩展发送给我们的数据:你在扩展里操作的待办、习惯打卡、完成的专注记录和每日签到(和网站上的专注空间、签到一样,保存到你的「我的数据」);你点「保存到起始页」时那一页的网址和标题(由网站的保存页面写进你的起始页);你点「添加到待办」时选中的文字或网页标题;你在地址栏输入 ws 后的搜索词(只用于搜索组件目录,不和账号关联保存)。

只保存在你设备上的数据:扩展设置、起始页快照(上一次打开时的样子:布局、壁纸、网站链接和小组件画面,用于新标签页秒开和离线显示)、番茄钟状态和还没同步的改动。卸载扩展或在扩展设置里清除缓存即删除。

书签和最常访问(可选,1.0.2 起):只有你在起始页上点「读取书签」或「最常访问」时,扩展才请求读取权限(浏览器会再确认一次),并且只在你点击时读取。读到的书签 / 网站只交给你正在用的起始页页面显示,扩展和我们的服务器都不保存;只有你勾选导入的网站(网址和名字)会作为起始页内容保存。预览图标时,我们的图标服务只收到网站的域名,不收到完整网址,也不记录。你可以随时在扩展设置里收回这两个权限。用网站导入书签 HTML 文件时,文件只在你的浏览器里解析,不会上传。

弹窗和设置页(1.1.0 起):工具栏弹窗和扩展设置页的界面是 widgetstore.net 的网页(在扩展里打开),所以打开它们时会像访问网站一样向我们请求网页。打开弹窗时,当前这一页的网址和标题只交给弹窗用来显示「保存这个网页」,不会发给我们,除非你点了保存。扩展还会定期从 widgetstore.net 下载一个只含功能开关和菜单文字的配置文件,请求里不带任何个人信息。

扩展申请的权限:存储(设置和缓存)、定时(番茄钟到点)、通知(专注 / 休息结束提醒)、右键菜单、当前标签页(只在你点扩展时读取当前页的网址和标题)、搜索(新标签页的搜索框使用浏览器的默认搜索引擎)、访问 widgetstore.net(显示起始页、同步数据、连接账号);可选权限:书签、最常访问的网站(只在你导入时申请和读取,见上一段);脚本注入(1.2.0 起,只注入扩展自带的保险库自动填充脚本);可选的「读取 https 网站」(只在你打开保险库「网页登录框旁的图标」时申请,见上文)。我们不出售这些数据,也不用于广告。

Android App(net.widgetstore.app,2026-11 起):首页、组件库、专注和我的是原生界面,编辑器、起始页等在 App 里打开 widgetstore.net 的网页;登录方式和浏览器扩展相同(一次性连接凭证换登录状态,刷新凭证用手机系统的密钥库加密后只保存在这台手机上,不进系统备份);用浏览器登录时,回到 App 的一次性凭证还绑定了只有这台手机知道的校验值,别的 App 截到也用不了。为了离线可用,App 用你的登录状态同步你的组件列表、组件库、待办、日程(前一天到 8 天后)、专注记录、习惯和目标,保存在这台手机的应用私有空间里(不进系统备份),离线时的改动联网后再提交给我们。桌面小组件显示的组件画面在手机上生成并缓存在手机上;你可以在 App 里关掉标题、只显示数量。App 申请的权限:联网、网络状态、通知(专注计时)、相机(扫码登录时在手机上识别二维码,不保存、不上传扫码画面;主动发起或接听视频通话时用于视频)、麦克风(主动发起或接听语音 / 视频通话时使用)、前台播放(环境音锁屏后继续播放,声音在手机上生成)、前台数据同步(只在你在专注自习室里时保持连接,本身不采集相机和麦克风)、实时动态(Android 16 起把专注计时、自习室和下载新版本显示在锁屏和状态栏,你可以在系统设置里关掉);除了下面说明的可选功能,不读取通讯录、相册、位置,不含广告和第三方统计。用 App 扫码登录电脑时,我们会把发起登录的电脑的浏览器、系统、打码后的 IP 和大概城市显示给你确认,这条登录请求最多保存几分钟、用完即删。你从其他 App 分享网址给组件世界时,网址和标题会存进你的起始页「稍后阅读」(可撤销)。退出登录会删除这台手机上的登录状态、本机数据库、网页和图片缓存、小组件画面。1.2.0 起的以下功能都默认关闭、由你主动打开:手机日历和联系人生日(只在手机上读取,不上传日程和联系人);健康(通过 Health Connect 读取步数、睡眠、静息心率)和屏幕使用时间(屏幕亮的时长、解锁次数)只在手机上计算,只有你另外打开「上传按天汇总」时,才把每天的几个数字存进你的「我的数据」,不上传原始记录和你用了哪些 App;情侣 / 亲友空间里,你选择分享的位置(城市级或精确)只保存最新一条、12 小时后失效,不保存轨迹;自动状态(到家 / 到公司 / 新城市)在手机上判断,只上传状态;发给对方的照片在手机上压缩后保存最多 48 小时、每个空间最多 6 张;「想你」、心情、纪念日只给同一空间的成员看到。任何成员随时可以退出,退出即删除其在该空间的位置、心情和照片。

手机网页通话与位置权限:只在你主动使用相应功能时请求,并受系统权限控制。Android 只向前台本站 HTTPS 页面提供获准的相机、麦克风或位置(精度由系统授权决定,不额外请求精确或后台权限);离开页面或进入后台会停止该页面的采集。iOS 通话同样需系统确认,进入后台会停用相机和麦克风;本次未新增 iOS 网页位置授权。通话内容经 WebRTC 加密传送,位置仅按你选择的分享功能发送给对方,不用于后台追踪。

密码与验证器:保险库在 App 打包的本地页面里解锁和解密(端到端加密,我们只收到密文);你打开指纹 / 面容解锁时用到「生物识别」权限,解锁用的本机秘密由手机系统的密钥库保护、只在这台手机上;只有你在系统设置里把组件世界设为自动填充服务,才在其他 App 和浏览器的登录框里显示「用组件世界填充」,你点了并选了一条才填入,你提交新密码时才问要不要保存;为了锁着时也能在登录框旁列出该填哪一条,App 在这台手机上存一份不含密码和验证码密钥的索引(名称、用户名、网址 / App 包名),用手机系统的密钥库加密、不进备份;忘记设备、清空保险库或退出登录时删除。这些都在手机上处理,登录框的内容、网址和这份索引都不发给我们。

专注自习室(2026-11 起):消息端到端直连,不经过我们的服务器,也不保存;连接握手需要经过服务器,同房间的人之间能看到彼此的 IP 地址。具体来说:同房间的人之间的聊天、状态(专注中 / 休息中 / 暂时离开)、今天的专注分钟数、你选择显示的「我在做什么」和鼓掌,都经 WebRTC 数据通道在设备之间直接传送(DTLS 加密),我们的服务器收不到;聊天只在浏览器内存里,离开房间就消失,任何地方都不保存(包括你的设备)。为了建立连接,我们的服务器(Cloudflare)会转发连接信息(其中包含 IP 地址)并记住谁在房间里,但不保存这些连接信息;房间保存的只有房主、节奏、是否锁定 / 禁言、被移出的账号,以及进过房间的人的名字和随机编号(举报核对用),房间关闭或 7 天没人进入后删除。为了发现自己的公网地址,浏览器会连到公开的 STUN 服务器(小米、芒果 TV、哔哩哔哩、Cloudflare),它们能看到你的 IP 地址。2026-11-14 起,两台设备直连不通时(比如两边都在手机网络的运营商 NAT 后面),连接会经 Cloudflare 的 TURN 中转服务器转发:内容仍是端到端加密的(DTLS),中转服务器看不到、也不保存,它只看得到双方的 IP 地址和流量大小;能直连时不会走中转。这同样适用于下面的「消息」。屏蔽名单只保存对方的随机编号和名字。举报时,只有你自己勾选附上的对方消息会发给我们,用于处理举报。每段专注结束时,你实际在场的分钟数会像平时一样记进你自己的专注空间。只和你信任的人一起进房间。「一起种树」:能量、你种下的虚拟树和你选择带上的同伴名字只保存在你自己的「我的数据」(森林表)里;房间里的树、能量球和叶子只在同房间的设备之间传送。

「消息」(2026-11 起;2026-11-15 起为端到端加密 + 离线投递):只有互相的关系才能聊天(同一个亲友空间的成员,或在自习室里互相加的「专注伙伴」)。消息在你的设备上加密,只有你们的设备能解开:每台设备有自己的密钥,私钥只在这台设备上、不能导出,公钥登记在我们的服务器(Cloudflare)上用来加密。对方在线时,加密后的消息经服务器直接转给对方;对方不在线时,加密后的消息在服务器上临时保管,最长 7 天,对方每台设备收到后立即删除,7 天没收到也会删除。我们看不到消息内容,只看得到谁在什么时候给谁发了多大的加密消息(不写日志,只在保管期间存在)。聊天记录(文字、图片、文件)只保存在你自己的设备上(浏览器或 App 的本机存储),可以随时导出或清空;我们恢复不了。文件和较大的图片在双方都在线时由两台设备直接传送(WebRTC,DTLS 加密,必要时经 Cloudflare 的 TURN 中转,中转看不到内容),这时对方能看到你的 IP 地址。我们的服务器只在你打开「消息」(或开着电脑版)时知道你在线,并告诉你的联系人(你可以隐身)。我们保存的还有专注伙伴名单、待同意的伙伴请求、你的设备公钥列表;你可以随时移除伙伴、屏蔽对方或移除设备。举报时,只有你勾选附上的对方消息会发给我们。

群资料与邀请:群名、成员名单、群公告、成员自行设置的群内昵称由服务器保存并向当前成员提供,属于服务器可见的群资料,不是加密聊天正文。邀请由真人成员主动生成,服务器仅保存令牌摘要和有效期;持有链接的人必须登录并主动确认加入。群备注、保存群聊和显示成员昵称偏好仅存在当前账号的本机设备。

火花转账与红包:为履行赠送交易、核对余额及账目、处理退款与争议,我们在服务器保存交易账本、余额、参与账号(发送人、指定接收人及实际领取人)、交易金额、手续费、创建与操作时间,以及领取、拒收、到期和退回状态。这些交易数据由服务器处理,不属于端到端加密聊天正文。人与人的聊天中仅传送端到端加密的交易引用;打开卡片时,服务器另行核验权限并返回交易详情。撤回或删除聊天引用、清空本机聊天记录,不会取消交易、触发退款或删除服务器账本。交易记录适用本政策的数据保留与权利规则,不适用聊天密文送达即删或最长七天的临时保管期限。

9. AI 应用与开放 API

你可以把 Claude、ChatGPT、Cursor 等 AI 应用(通过 MCP)或自己的脚本(通过个人 API 令牌)连接到你的账号。只有你在授权页点「允许」或自己新建令牌后才会连接,权限由你选择,可以随时在「设置 → API 与 AI 连接」断开或撤销。

AI 应用按你的指令读取你授权范围内的数据(例如组件配置、个人主页、起始页、待办和「我的数据」的记录),这些内容会进入你和该 AI 应用的对话,由该应用按其自己的隐私政策处理。我们不会把你的数据提供给任何人训练模型。

我们保存:令牌和授权的哈希值(不保存明文)、应用名称、权限、创建和最近使用时间、每日调用次数,以及每次修改的操作记录(谁、何时、改了什么、修改前后的内容,用于查看和撤销),操作记录随账号保存,注销账号时一并删除。AI 应用不能删除你的数据,也不能访问账号、付款和会员信息。

10. 音乐空间

音乐文件(2026-11 起):你在音乐空间(/music)上传的音乐文件和封面保存在 Cloudflare R2 对象存储(亚太地区)的私有存储桶里,没有公开链接;歌名、歌手、专辑、时长、歌词、歌单、用量等信息和其他账号数据一样保存在腾讯云。上传时,你的浏览器在本机算出文件的 SHA-256 指纹、读取标签和封面,文件直接从浏览器传到 R2;我们的服务器只签发短时间有效的上传和播放地址,不转发、不转码,也不分析音频内容。播放地址只签给曲库里有这首歌的账号,几小时后失效。

去重:内容完全相同的文件(指纹相同)在全站只保存一份。如果别人已经上传过和你一模一样的文件,你的曲库里只是多一条指向它的记录,你的用量仍按这首歌的完整大小计算。去重不会把任何人的曲库暴露给别人:别人看不到你有哪些歌,也无法知道某个文件还有谁上传过;只有曲库里有这首歌的账号才能拿到它的播放地址。为了防止有人只凭网上公开的指纹「认领」别人的文件,全站已有相同文件时,你的浏览器必须从你手里的文件中答出我们随机挑选的几小段内容(持有证明);答错这次上传即作废,证明通过之前不会给出任何上传或播放地址。

保留与删除:你删除一首歌时,我们立即删除你的这条记录并扣回用量;如果这首歌在原创市场上架,会同时撤下。存储里的文件在没有任何账号再引用它时删除(删除前会重新核对,确认没有引用才删);如果别的账号也上传过同一个文件,文件会为他们保留,但与你不再有任何关联。没有完成的上传在 1 天内自动清除。注销账号时,你的曲库、歌单、听歌记录、市场作品和公开设置一并删除,文件按上面的规则处理。你选择「下载到本机」的歌只保存在你的浏览器里,可以在音乐空间里删除本机下载或清除浏览器数据。

听歌记录:一首歌听满 30 秒或一半(先到为准)算一次播放。我们记录:每首歌的累计播放次数、收听时长和最后播放时间;每天的合计(播放次数、分钟数、听了几首)和当天每首的次数;最近播放和「正在听」。播放先在你的设备上排队,再分批上传;没登录时(例如在原创市场试听)不记录。这些记录默认只有你自己能看到(音乐空间的统计页和年度回顾、你连接的 AI 应用)。我们还会在你的「我的数据」里建一张「听歌记录」系统表(每天一条:播放次数、分钟数、歌曲数),不占「我的数据」的额度。

公开开关:音乐空间的设置里有「正在听」「最近播放」「最常听」「时长和热力图」四个开关,默认全部关闭。只有打开的项才会提供给你放在 Notion、个人主页等公开位置的音乐组件,没打开的项我们的服务器根本不会返回;组件只拿到歌名、歌手和数字,拿不到文件、播放地址和封面。年度回顾的公开版本(/music/wrapped/<随机编号>)只显示你勾选的项目,不让搜索引擎收录,可以随时关掉。

删除听歌记录:「我的数据」里的「听歌记录」表可以随时整张删除(删除后音乐空间里的统计不受影响,你下次听歌时会重新生成当天那一条)。删除歌曲不会删除它的播放统计。如需删除音乐空间里的全部播放统计,请发邮件到 support@widgetstore.net;注销账号时会一并删除。

原创市场:把曲库里的一首歌提交到原创市场时,你需要声明这首作品的词、曲和录音都是你本人创作、你有权公开发布。我们保存这份声明的时间、你同意的市场规则版本和你当时 IP 地址的哈希值(不保存 IP 本身),用于处理版权纠纷。审核通过的作品所有人都能播放,页面显示歌名、歌手、封面和你公开个人主页的名字(没有公开个人主页就不显示),从不显示你的账号 ID。作品显示的播放次数只是累计总数:我们不记录谁听了你的作品,也不会告诉你或任何人。举报不需要登录:我们保存举报原因、说明、举报人留下的邮箱(版权投诉必填)和举报人 IP 地址的哈希值(用于防止重复举报),只有管理员能看到,用于处理举报和联系相关方。

发给朋友(点对点):在「消息」里把歌发给朋友时,文件从你的浏览器直接传到对方的设备(WebRTC 数据通道,DTLS 加密),不经过我们的服务器,也不生成任何链接。和「消息」一样,直连时对方能看到你的 IP 地址;直连不通时经 Cloudflare 的 TURN 中转服务器转发,中转服务器看不到内容,只看得到双方的 IP 地址和流量大小(见第 8 条)。对方收到的歌只在页面内存里,只有对方选择存进自己的音乐空间时,才作为对方自己的上传保存到对方的曲库、占对方的额度。

11. 密码与验证器(保险库)

端到端加密(2026-11 起):你在「密码与验证器」(/vault)里保存的密码、两步验证码(身份验证器的密钥)、安全笔记、银行卡和身份信息,会在你的设备上用「主密码」和只保存在你设备上的「账户密钥」共同派生的密钥加密(Argon2id + AES-256-GCM),我们的服务器只保存密文。名称、网址、用户名也都在密文里。我们无法读取这些内容,也无法帮你恢复:忘了主密码又丢失了恢复包,就无法再打开。

我们能看到的只有:每个条目的随机编号、它是密码类还是验证器(用于分别计算额度)、密文大小、修改时间,以及是否在「最近删除」里。我们会记录创建保险库、修改主密码、导出和关闭保险库这几类安全事件(在账户中心的安全记录里可以看到),不记录内容。AI 应用、MCP 和开放 API 都无法读取保险库。

泄露检查:使用「密码健康」的泄露检查时,你的浏览器直接向 Have I Been Pwned(api.pwnedpasswords.com)发送每个密码 SHA-1 哈希的前 5 位(k-匿名),不发送密码本身或完整的哈希;可以在保险库的设置里关闭。扫描的二维码和导入的文件只在你的设备上处理,不会上传。

保留与删除:删除的条目在「最近删除」里保留 30 天后彻底删除;关闭保险库会删除全部条目和密钥。忘记主密码并选择清空时,内容会被移出你的账号,30 天后彻底删除。注销账号时一并删除。

12. 政策更新

我们可能更新本政策,更新后会在本页面公布并修改生效日期。

13. 联系我们

隐私相关问题请联系 support@widgetstore.net。