Updated: October 13, 2026
Privacy policy
This policy explains data used when you search, participate in the community, or contact us about a product.
Public search
When you submit a search, we process its text to create a semantic representation, query the knowledge graph, and return public metadata. Search does not require an account. Query text may be sent to OpenAI Embeddings and Qdrant; a fallback path may use Cloudflare Workers AI and Vectorize.
A2A conversations
When you actively send a message to the A2A service, OpenAI processes it to generate a reply and infer whether your underlying goal needs public AI technology discovery. A KG search may run when the described task calls for candidates or evidence, even without a literal search command. To support follow-up turns, up to the eight most recent messages are stored under an opaque conversation ID in Cloudflare Durable Objects SQLite and automatically deleted within 12 hours. Separately, completed A2A exchanges (your message and the service's reply) are stored in a private Durable Objects SQLite audit store for service-quality and intent-handling review. Only authorized administrators can view them in the analytics dashboard; the context ID is stored as a one-way hash, and audit records are automatically deleted after 30 days. Known health probes and protocol requests without a completed reply are excluded. A2A conversation text is not placed in public comments or anonymous visit analytics. Do not send passwords, API keys, or sensitive customer information. Agent Card discovery, ordinary crawling, and connectivity probes do not call an LLM.
Product inquiries and pilots
If you choose to submit the contact form, we collect the product you selected, your workflow or problem, your contact method, and any name or organization details you choose to provide so we can reply to that inquiry. We also record the form page, entry path, external referrer host, or UTM markers carried into the visit to understand which channels bring inquiries. First-party navigation is not labeled as acquisition. Since October 6, 2026, new inquiries are not linked to the website's anonymous visit identifier.
Contact details and message content are stored in a restricted Durable Objects SQLite inbox, not in the public community or knowledge graph. Only authorized administrators can access them. Your form consent covers storing those details to respond to the inquiry. Referral and campaign markers are used only for aggregated channel measurement, not for marketing; unrelated follow-up requires separate consent.
Retention and data requests
The inquiry inbox currently has no automatic deletion schedule. Earlier inquiries may still contain an anonymous visit identifier from the previous implementation; these records have not been retroactively scrubbed. Contact details and message content are used to handle the inquiry; referral and campaign markers are used only for aggregated channel measurement. To request access, correction, or deletion, email hello@zhiyong.dev for manual handling. Automated self-service deletion is not currently available.
Community feedback
Comments and topics you publish may be public and remain separate from the knowledge graph. To limit abuse and repeated likes, we use a random zhiyong_vid identifier in an HttpOnly cookie retained for up to one year. On kg.zhiyong.dev, this identifier can connect repeat-visit analytics with comment and like records; it is host-scoped, does not carry over to the zhiyong.dev root site, and does not directly reveal your real-world identity. Anonymous visitors may post up to five feedback items per day.
Usage analytics
We may record page paths, visit times, referrer host, country or region, and an anonymous visitor identifier to understand usage. On kg.zhiyong.dev, the same host-scoped identifier is also used for feedback abuse prevention, so those records can be linked within that host. Raw IP addresses are not stored in the admin analytics database or shown in the admin dashboard.
Third-party services and advertising
The site runs on Cloudflare infrastructure. External providers may process necessary network requests and operational logs under their own policies. Google AdSense ads may appear; Google and its partners may use cookies or similar technologies according to consent, device, and context.
Contact
For support or questions, visit the support page.