Product help
For setup, browser behavior, backups, providers, local models or MCP. Include your browser, device, affected page, expected result and reproducible steps.
The right path.
No runaround.
Product question, commercial project or security concern? One public inbox uses three clearly labelled routes. Email opens in your own mail app—this page has no hidden contact form.
No account requiredNo hidden formDedicated security subjectsales@pui.ai
Enough context for the right conversation.
Each link opens the same configured public address with a distinct subject. That keeps the contact surface simple while making your intent clear.
Business and deployment
For a Business Pilot, self-hosted deployment or a separately scoped enterprise project. Describe the team size, operating model and desired outcome.
Responsible reporting
For a suspected vulnerability or unsafe product behavior. Start with the affected URL or feature, impact and minimal reproduction steps—never include live credentials.
WHAT TO INCLUDE
Context, not secrets.
A concise subject, the affected feature, browser or runtime, reproducible steps and any non-sensitive error text help establish the issue. For security reports, include the impact you believe is possible.
WHAT NOT TO SEND
Keep credentials out.
Do not email API keys, Bearer tokens, backup passphrases, full protected backups or unredacted private documents. Ask before sharing sensitive evidence or personal data.
Prefer self-service?
Documentation covers setup, browser storage, local models, MCP and recovery.