Skip to content
JevForAgents
BuildsPatternsGuideResourcesWhat is Jev
⌘K
SponsorsPricingSubmit a build
BuildsPatternsGuideResourcesWhat is JevSponsorsPricingAUP & ModerationSubmit a build
Site policy

Privacy Policy

Effective September 23, 2026. This policy describes how JevForAgents handles information collected at jevforagents.com.

Who to contact

JevForAgents is operated by an individual based in China. For privacy questions or requests, email l1137622803@gmail.com.

Information we receive

  • Build submissions: the website URL and optional X handle you choose to send by email. The submission form opens your email app; it does not store a submission on our server by itself.
  • Sponsor purchases: the email address, product URL, optional tagline, bid amount, Waffo order ID, payment status, and payment time needed to review and display a placement. We do not collect or store full card numbers.
  • Support messages: your email address and the information you include when you contact us.
  • Site usage: normal hosting and security logs, plus usage information collected by Microsoft Clarity. If live header statistics are enabled, we set a first-party random browser identifier to estimate currently active browsers; that cookie lasts up to two years. We store a hash of that identifier, not the identifier itself. We also count each page load or in-site page change as one view, including repeat visits, without tying the view total to a browser identity.

How we use information

We use these details to operate the site, review build submissions, create checkout sessions, confirm payments, rank verified sponsor placements, answer support requests, prevent abuse, and understand how the site is used. We do not sell personal information or use sponsor email addresses for marketing without a separate opt-in.

Service providers and public listings

Waffo Pancake handles checkout and payment card information as the payment provider. Supabase stores sponsor order records. Vercel hosts the website. Microsoft Clarity provides site analytics. We share only the information each provider needs for these functions. The public sponsor board displays the product URL, tagline, bid amount, and ranking; it does not display the buyer email address or order ID. Your product website may receive a visit when someone follows its listing link.

Retention and choices

We keep sponsor transaction records while needed for the active leaderboard, refunds, disputes, and applicable recordkeeping requirements. We keep support correspondence while needed to resolve the request and meet those requirements. You can ask to access, correct, or delete your personal information by emailing l1137622803@gmail.com. Some transaction details may need to be retained for legal or accounting reasons; we will explain any limit when responding. You can clear the visitor cookie in your browser and use your browser’s privacy controls for analytics.

Security and changes

We use HTTPS and limit database access to server-side credentials. No online service is completely risk free. If this policy materially changes, we will update this page and its effective date.

See also our Terms of Service and sponsor pricing.

JevForAgents

The practical database and guide to building AI agents with Jev.

Build with Jev

  • Codex
  • Claude Code
  • Browser Use
  • MCP
  • Agent Skills
  • Build Your Own Agent

Patterns

  • Browser Agents
  • Agent Routing
  • Tool Selection
  • Agent Evaluation
  • Guardrails
  • MCP / Skills
  • Search & Semantic Retrieval
  • Realtime & Audio Agents
  • Coding Agents

Database & Research

  • All Builds
  • Resources Library
  • Jev Engineering PDF Guide
  • Video Demos
  • GitHub Projects
  • Jev Agent Statistics Coming soon
  • Evidence Protocol

Community

  • Submit a Build
  • Contact support
  • Suggest a Correction
  • Sponsors Leaderboard
  • Sponsor Pricing
  • Terms of Service
  • Acceptable Use Policy (AUP)
  • Privacy Policy
  • Official Jev Docs ↗

Independent from TypeSafe AI. What is Jev · Agent builder’s guideOnline counts browsers seen within the last 75 seconds. Views count each page load or in-site page change, including repeat visits. We use a random first-party browser ID for the online count and do not store IP addresses.