Privato

What the company appears to be: Privato is a self-reported family information management tool that organizes sensitive household data into trust-based circles (Core, Inner, Outer) and uses AI to answer questions about that data only within the user's authorized scope.

What changed: The project description shows a shift from a generic digital vault concept to one explicitly focused on family relationships and trust circles. It also introduces an AI layer that operates under strict authorization boundaries.

The single most important open question: Does Privato have any evidence of real-world usage, customer feedback or traction beyond the author's own prototype?

The description states that Privato is:

• A private information network for families
• Designed to organize sensitive household information
• Organized around three concentric trust circles (Core, Inner, Outer)
• Uses AI to answer questions about data only within authorized scope
• Built as a vertical slice using Next.js, React, TypeScript, Tailwind CSS, PostgreSQL, OpenAI, and ElectriPy AI runtime controls

This is a self-reported product that has not been independently verified for functionality or adoption.

The description states:

• Original positioning: "Digital vaults organize files. Privato organizes trust."
• Evolved claim: Instead of managing access one document at a time, users organize people into trust circles
• AI capability: "Ask Privato" that retrieves information only within the current person's authorized scope
• Security focus: "The safest AI authorization decision is the one the model never receives"
• Privacy model: Identity-aware AI retrieval with grounded citations and protection traces

These claims reflect an evolution from a basic file vault to a relationship-based access control system with AI-powered question answering.

The description states:

• Primary users: Families
• Specific use case: Organizing information for emergency situations
• Target audience: People who need to share sensitive household data intentionally with the right people
• Trust circles represent different levels of relationship intimacy (spouse, children, friends, caregivers)

No evidence provided about specific customer segments beyond "families."

The description states:

• No explicit business model or pricing information
• The project is described as a prototype built for a hackathon
• No mention of monetization strategy, subscription tiers, or revenue streams

Not evidenced.

The description states:

• Built with Next.js, React, TypeScript, Tailwind CSS, PostgreSQL, OpenAI, Zod, ElectriPy AI runtime controls
• Uses Drizzle ORM and Drizzle Kit
• Implements circle-based authorization deterministically across all application boundaries
• AI layer sits behind an application boundary with structured validation, retries, timeouts, circuit breaking, telemetry, and fallback behavior
• Architecture designed to prevent common failure modes in AI systems
• Includes tests and evaluation scenarios around privacy-sensitive AI system failures

The technical stack and architecture appear production-shaped but are self-reported.

The description states:

• The project is a prototype built for a hackathon (Build Week version)
• No evidence of revenue, customers, or adoption beyond the author's own account
• No mention of user feedback, usage metrics, or product-market fit indicators

Not evidenced.

The description states:

• Most digital vaults are designed around files, folders, and individual permissions
• Privato focuses on relationship-based access control instead
• The project is positioned as an alternative to enterprise access-control software
• No direct competitors named or described

No evidence of competitive landscape or market positioning beyond the author's own claims.

The description states:

• The project is a prototype built for a hackathon
• No evidence of real-world usage, customer feedback, or traction
• No mention of security compliance, zero-knowledge architecture, or independently audited security
• AI system operates under strict authorization boundaries but has not been tested in production
• No indication of scalability, performance, or long-term viability

Key risk: The project is unproven and lacks any evidence of real-world adoption or customer validation.

1. What specific family use cases did you test with during development?
2. How many people have actually used this prototype in a real household setting?
3. Have you conducted any user research or feedback sessions with families?
4. What are your plans for security auditing and compliance?
5. How do you plan to monetize this product if it moves beyond the prototype stage?
6. What is your roadmap for scaling beyond a single-user prototype?