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.