Privacy and analytics
JGuang uses anonymous first-party analytics to learn which resources are useful, which connection methods work best and what people search for that does not exist yet.
What we measure
- Anonymous page views and interface actions, such as copying an installation command or switching between the prompt, Skill and MCP methods.
- Anonymous counts of Registry downloads, Agent Skill downloads, MCP tool calls and Markdown documentation reads, including which resource or component they concern.
- Search terms on JGuang, lowercased and truncated to 50 characters, with the number of results.
- Country, the referring website's domain, the page language, the type of client (browser, coding agent, crawler or command-line tool), whether the device is a phone, tablet or computer, and whether the browser shows itself as signed in.
- Which components, documentation, downloads and outbound links are opened, which filters are used, and which previews fail to load — counted per resource, never per person.
Anonymous analytics limits
- Analytics do not use tracking cookies, local identifiers or fingerprinting scripts. Authentication uses necessary session cookies separately.
- Analytics events do not store IP addresses or full user-agent strings. Authentication may store them for session security and abuse prevention.
- Visitors are counted with a hash of the IP address, user agent, date and a private key. Because the date is part of the hash, it changes every day.
- Analytics are not used for advertising or user profiling.
Accounts and sign-in
- Accounts store your email, display name, verification status and linked login-provider information. JGuang does not use passwords.
- Necessary session cookies keep you signed in for up to seven days. Browsing and copying public content never needs an account; generating agent prompts, viewing component source and saving resources require sign-in.
- Account data is stored in Cloudflare D1. When enabled, Google processes Google sign-in and Resend delivers sign-in codes. Codes are stored hashed and expire in ten minutes. To prevent abuse, request counters are kept for at most two days, keyed by a one-way hash of the email address or IP address. Local development does not send emails and prints test codes only in the local terminal.
- Account records are retained until deletion. If you save resources, JGuang stores that list; generating agent prompts and viewing component source keep a short “recently used” history (the latest 50 entries), visible only to you and clearable at any time. You can edit your display name, manage sign-in methods and devices, and permanently delete your account on My account. Deletion removes your account, saved resources, history, login methods, sessions and legacy tokens; anonymous analytics cannot be tied back to an account and expire on their own schedule. Contact jiguangshe@gmail.com for access or help. Do not include passwords in your message.
- To count daily and returning signed-in users, JGuang records the calendar days on which each account opened the site (no pages or actions) for 90 days. Only totals — such as new accounts and active users per day — leave the database for the dashboard.
Where the data lives
- Events are stored in Cloudflare Workers Analytics Engine for three months and then deleted automatically. JGuang reads them through a read-only Grafana Cloud dashboard.
Your choices
- If your browser sends Do Not Track or Global Privacy Control, pages do not report views or interface actions.
- Requests to Registry files, Skills, the MCP server and Markdown documents are counted anonymously on the server regardless of browser settings, because these tools do not run page scripts.
Questions? Email jiguangshe@gmail.com.