Venice source record.
This page presents a held funder-owned source excerpt. It does not decide whether any person or project qualifies, should apply, or will receive funding.
Bug Bounty Program | Venice AI
| Funder | Venice |
|---|---|
| Who this may be for | AI-interpreted · not the funder's words The page does not make clear who this is for. Written by a local AI model (qwen3.5:9b-q4_K_M) from the saved page only. It is an interpretation, not a statement by the funder and not eligibility advice. |
| Scope (our category) | Security, audits & bug bounties (matched words: bug bounty, vulnerability; meaning score 0.775) Assigned by us from the saved page: matched words, a meaning-similarity score, or (marked) an AI tie-break. Not a statement by the funder. |
| Saved page class | programme page Page class describes the saved route only. It does not state whether a programme is open, closed, suitable, available, or an endorsement. |
| Status | not stated by funder |
| Amount | not stated by funder |
| Deadline | not stated by funder |
| Eligibility | security researchers who responsibly disclose vulnerabilities in our products security researchers who responsibly disclose vulnerabilities in our products · saved page text; phrase proposed by a local model and verified verbatim by code |
| Held-source observation | Last material byte change observed 2 days ago · last observed 20260926T223936Z · source signal only |
| Held grant-history observation | No explicit programme-to-dataset mapping with a dated held record is available. This does not state there is no grant history. |
Held source excerpt
Bug Bounty Program | Venice AI Submit a Report USD-denominated rewards paid in USDC and/or VVV Bug Bounty Program Help us keep Venice secure. We reward security researchers who responsibly disclose vulnerabilities in our products. Submit a Report Learn More Process How the Program Works Our bug bounty program provides a structured way for security researchers to report vulnerabilities and earn rewards. Step 1 Discover Find a security vulnerability in a Venice product within scope. Step 2 Document Create a detailed report with proof of concept and reproduction steps. Step 3 Report Submit your findings through our secure reporting form. Step 4 Reward Eligible bounty rewards are denominated in USD and paid in USDC and/or equivalent VVV at Venice's discretion. Rewards Rewards Eligible bounty rewards are denominated in USD and paid in USDC and/or equivalent VVV at Venice's discretion. Rewards are based on demonstrated impact, exploitability, novelty, reproducibility, and report quality. Low Starts at $200 Minor but real security issues with clear reproduction, such as limited information disclosure or low-risk configuration gaps with demonstrated impact. Medium Starts at $750 Contained vulnerabilities with demonstrated impact, such as limited stored XSS, narrow authorization gaps, or abuse paths affecting a small set of users. High Starts at $2,500 Significant vulnerabilities affecting account security, authorization boundaries, billing integrity, or user data. Critical Case-by-case, scaled to impact Severe, novel vulnerabilities with broad user impact, such as authentication bypass, remote code execution, sensitive data exposure at scale, or VVV smart contract compromise. Coverage Program Scope Please review what is and is not covered by this program before submitting. In Scope Venice web application (venice.ai) Venice API (api.venice.ai) Venice Android app, iOS app, and official APK Authentication and session management Payment and billing flows User data handling and privacy controls Chat and conversation encryption VVV and DIEM smart contracts Out of Scope Non-CSAM related content generation Exfiltration of system prompts Social engineering or phishing attacks Denial-of-service (DoS/DDoS) attacks Unsubstantiated or non-deterministic IDOR, CORS, or BOLA issues Third-party or vendor-managed issues unless caused by Venice's integration or configuration Tokens or IDs that are public-facing by design, required to integrate with third-party services, such as Datadog RUM IDs, PostHog keys, Google API IDs, or Mapbox IDs Other pieces of metadata that are public-facing by design, such as model catalogs, pricing, AI character templates, or blockchain data Build artifacts, including but not limited to: deployment IDs, Vercel IDs, or Github hashes Issues requiring physical access, such as using the mobile app on a jailbroken iPhone Automated scanning without validation Spam, abuse, or reputation reports without a security vulnerability Security header, DNS, SPF, DMARC, CAA, or version disclosure reports without demonstrated exploitability or user impact Theoretical rate limiting or brute-force reports without demonstrated impact Guidelines Report Requirements All submissions must include a clear proof of concept, exact reproduction steps, and a description of the security impact. Proof of Concept Demonstrate actual exploitation with video, screenshots, or exact reproduction steps. Exceptions apply for self-evident issues like certificate problems. Specific to Our Environment Show the vulnerability exists in our actual application, not theoretical scenarios. Generic scanner output without validation is not eligible for rewards. Based on Your Testing AI-assisted reports are acceptable only if they are personally validated and reproducible. Unverified AI-generated reports will be rejected. FAQ Frequently Asked Questions Who is eligible to participate? How are rewards determined? What makes a good report? How long does the review process take? When will Venice respond to my report? Can I share my report publicly? What if my report is a duplicate? How are rewards paid? Ready to Report? Help Keep Venice Secure Found a vulnerability? Submit your report and help us protect our users. Eligible bounty rewards are denominated in USD and paid in USDC and/or equivalent VVV at Venice's discretion. Submit a Report Back to Venice © 2026 Venice AI. All rights reserved. Back to Venice Terms Privacy Discord
docs_evidence/funding-radar/official-pages/20260926T223936Z/venice.html · sha256 2f5b1976e3e8813fa8530b687fe1c9a7e2c2988446c1a10b4c59c70c776ce07d · saved and fingerprinted 20260926T223936Z · direct download of the public page · held page title and funding-related excerpt
The funder statement is retrieved evidence only. Held-source observation is a byte-change signal only. Neither signal determines eligibility, fit, application strength, likely outcome, or programme availability.