IDcognito

The description states that IDcognito is a tool designed to help people "see, understand, and shrink their digital exposure." Its centerpiece is an "Exposure Graph" which connects identity attributes to breach records, broker listings, search results, social profiles, and evidence-backed relationships. Selecting a node reveals supporting evidence, while one-hop expansion shows related people without confirming those connections.

A "Cleanup Copilot" converts findings into a prioritized, user-approved review queue. GPT-5.6 powers one deliberately bounded feature: Evidence Review, which examines evidence attached to observations and returns an advisory verdict (likely relevant, likely a collision, or insufficient evidence), along with citations, uncertainty, and a suggested human review step.

The system uses synthetic data generated by SynthWorld, an open-source deterministic generator for testing identity exposure. The shared judge build uses unmistakably synthetic data and performs no live real-person HIBP or Bright Data lookups.

Inference This is a privacy visualization and advisory tool built around a synthetic dataset and AI-assisted review process. It does not appear to be a production-ready service with live integrations, nor does it claim to perform actual identity cleanup actions.

The author states that they have worked in Enterprise Identity Management for years but found personal identity management even more complex due to social media and breaches. They note that most privacy tools produce flat lists of alarming findings without showing how those findings connect or how trustworthy each conclusion is.

This project evolved from earlier versions that tried to cover too much before having realistic test data, measurable ground truth, or an honest end-to-end harness. The current version was rebuilt around a simpler idea: people should be able to see their digital exposure as a connected evidence graph, and every product claim should be testable without using anyone’s real personal data.

Inference The positioning has shifted from trying to do everything to focusing on visualizing exposure through a connected graph with evidence-backed relationships. The emphasis is on transparency and testability rather than action or automation.

The description states that IDcognito helps people see, understand, and shrink their digital exposure. It targets individuals who are concerned about privacy and want to know what information is publicly available about them.

It appears to be aimed at users who are already aware of identity risks and are looking for tools to better understand and manage them.

Inference The target customer seems to be privacy-conscious individuals, likely tech-savvy or early adopters of privacy tools. There is no mention of enterprise customers or B2B use cases.

Not evidenced.

The description does not contain any information about pricing models, monetization strategies, or business model assumptions. No revenue streams, subscriptions, or paid features are mentioned.

IDcognito uses a FastAPI and SQLAlchemy backend with PostgreSQL adapter, plus a React, TypeScript, Vite, and react-force-graph-2d frontend. The judge deployment uses a deterministic in-memory adapter. Every external dependency sits behind a port, making the zero-key synthetic implementation a first-class path rather than a special demo branch.

GPT-5.6 is integrated through one EvidenceReviewer port using the OpenAI Responses API, strict structured output, store=false, bounded input, explicit uncertainty, one attempt, and sanitized failures. The public judge deployment uses the equivalently shaped deterministic golden adapter so shared credentials cannot consume API credits.

Codex served as the autonomous engineering collaborator, working from mechanistically checkable specifications: writing analytical assertions before implementations, running quality gates, inspecting browser screenshots, packaging deployments, auditing releases, and producing submission-video pipelines.

Inference The technical stack suggests a modern web application with backend APIs, frontend visualization, and AI integration. The use of synthetic data and deterministic adapters indicates strong emphasis on reproducibility and testing rather than live data handling.

Not evidenced.

There is no mention of actual users, customers, or real-world usage beyond the synthetic demo. No revenue figures, user growth metrics, or product adoption data are provided. The project is described as a hackathon submission with no indication of ongoing development or commercial traction.

Not evidenced.

The description does not reference competitors or market positioning relative to existing privacy tools or identity management platforms. No competitive landscape analysis or differentiation strategy is presented.

1. No real-world data integration: The system uses only synthetic data and does not perform live lookups against breach databases or broker services.
2. Limited AI scope: GPT-5.6 is used only for advisory review, not for identity confirmation or remediation.
3. No monetization strategy: No evidence of pricing, subscriptions, or revenue model.
4. Unproven user demand: No indication of actual users or market traction beyond the author's own claims.
5. Synthetic-only deployment: The public version is intentionally synthetic, which may limit its perceived value to potential investors or partners.

1. What are your plans for transitioning from synthetic data to live integration with breach databases and broker services?
2. How do you intend to monetize this product if it currently only works with synthetic data?
3. Have you received any feedback from users or potential customers beyond the hackathon context?
4. Is there a timeline for moving beyond the current synthetic-only demo toward real-world functionality?
5. What are your thoughts on privacy compliance and data handling in a live environment?