OpenAI 2026 hackathon

TrustLens

Know what you're agreeing to before you click "Agree" . TrustLens reviews website policies and alerts you when they change.

Solo project by Nirvik PATEL · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #7,413 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

TrustLens is a self-reported Chrome extension built as part of an OpenAI 2026 hackathon submission. The author states it aims to help users understand website policies before agreeing to them by using AI to analyze policy pages and highlight important clauses. It claims to support policy change detection and transparency through source attribution.

The project description is entirely self-reported, unverified, and lacks evidence of revenue, customers, or traction. No funding, headcount, or commercial activity beyond the hackathon submission is evidenced.

Key open question

Is there any evidence that TrustLens has moved beyond a prototype or proof-of-concept stage, or whether it has been tested with real users?

Back to contents

What The Product Actually Is

The description states that TrustLens is a Chrome extension. It is built using:

  • Technology stack: Chrome, extension, manifest, Node.js, React, TypeScript, Vite
  • AI model used: o4-mini/gpt-os-120B via OpenAI API / Cloudflare API
  • Core functionality: Reviews website policies (Terms & Conditions, Privacy Policy, etc.) and highlights important clauses using AI.
  • Features include:
    • Automatic discovery of policy pages across websites
    • Policy change detection with summaries
    • Local storage for history, settings, and watchlist
    • Source attribution for AI-generated claims

Inference: The product is described as a browser extension that leverages AI to simplify legal document review.

Back to contents

Positioning & Claim Evolution

The author states the inspiration was personal — noticing how few people read terms and conditions due to length and complexity. TrustLens is positioned as a tool to help users make informed decisions before clicking "Agree".

Key claims from the description:

  • Users can see important information in one click.
  • AI reviews thousands of lines of legal text.
  • Policy watch feature detects changes and explains what changed.
  • Every AI-generated claim is linked back to its source for transparency.

Inference: The positioning is centered on user empowerment through AI-assisted policy understanding, with a focus on privacy, trust, and informed consent.

Back to contents

Target Customer & ICP

The description states that the author built TrustLens because:

  • "Most of us not have time to read them"
  • "Few days back i was signing up in one site and i accept the terms and condition without reading it as always i do"

Inference: The target customer is a general internet user who signs up for services frequently but does not read policy documents.

The description does not specify:

  • Demographics
  • Geographic focus
  • Industry verticals
  • Specific use cases beyond general sign-ups

Not evidenced: No evidence of segmentation, persona development, or specific buyer profiles.

Back to contents

Business Model & Pricing Evidence

The description states that TrustLens is a Chrome extension, and the author mentions building it as part of a hackathon. There is no mention of:

  • Monetization strategy
  • Pricing model
  • Subscription plans
  • Freemium vs paid tiers
  • Revenue streams

Inference: The business model is not described, nor is there any evidence of commercial viability or pricing.

Back to contents

Technical & Delivery Signals

The description states:

  • Built as a Chrome extension with React, Node.js, TypeScript, Vite
  • Uses AI models (o4-mini/gpt-os-120B) via OpenAI/Cloudflare APIs
  • Includes a custom website crawler to discover policy pages
  • Implements local storage for history and settings
  • Uses Codex (GPT-5.6 Terra) for planning and implementation

Inference: The technical approach appears to be AI-powered browser extension, with AI used for document analysis, change detection, and summarization.

Not evidenced:

  • No evidence of scalability or infrastructure
  • No mention of data handling or privacy practices beyond local storage
  • No evidence of API integrations or backend services

Back to contents

Traction & Maturity Signals

The description is entirely self-reported and lacks any evidence of:

  • User adoption or engagement
  • Customer feedback or usage metrics
  • Product iterations or improvements
  • Market validation or testing
  • Revenue or monetization

Inference: The project appears to be a prototype or hackathon submission, with no demonstrated traction or maturity.

Back to contents

Competitive Context

The description does not mention:

  • Competitors in the space
  • Existing tools for policy review or legal document analysis
  • Market size or competitive landscape

Not evidenced: No evidence of competitive positioning, market research, or awareness of existing solutions.

Back to contents

Key Risks & Red Flags

  1. Unverified claims: The description is entirely self-reported and unverified.
  2. No traction or commercial activity: No evidence of users, revenue, or adoption beyond the hackathon.
  3. AI reliability concerns: The author notes challenges in prompt refinement and change detection — suggesting potential inaccuracies or edge-case failures.
  4. Limited scope: Only a Chrome extension is mentioned; no support for other browsers or platforms.
  5. Lack of business model clarity: No indication of how the product will be monetized or scaled.

Inference: The project is likely in early development and has not yet demonstrated commercial viability or user traction.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the current status of TrustLens — is it a working prototype, or has it been tested with users?
  2. How does TrustLens handle false positives or misinterpretations from AI models?
  3. Has the extension been submitted to the Chrome Web Store or made available for public use?
  4. Are there any plans to monetize the tool, and if so, what model is being considered?
  5. What are the technical limitations of the current crawler and AI integration?
  6. How does TrustLens ensure compliance with legal and data privacy regulations?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The description provides no evidence of:

  • Revenue or financial performance
  • Customer base or user traction
  • Product-market fit or commercial viability
  • Team experience or prior success
  • Funding or investment history

Inference: Based on the self-reported, unverified description alone, TrustLens appears to be a conceptual or prototype-level project with no demonstrated commercial readiness. It is not evident whether it has moved beyond a hackathon submission or has any traction.

The author states that the project was built in a hackathon and does not provide evidence of further development or market validation. Any potential investment or partnership opportunity would require deeper due diligence into its current state, user testing, and commercialization strategy.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.