Get in touch

We are a small team. The fastest way to reach us depends on what you need.

Contact form (recommended)

For most inbound, use the contact form on the marketing site:

It routes to the right person internally and is the most reliable way to get a response within 1 to 2 business days.

Reason	Email
Support, billing, account questions	support@toado.dev
Sales, partnerships, enterprise terms	sales@toado.dev
Security disclosures (please do not file public issues first)	security@toado.dev
General	hello@toado.dev

For product discussions, feature ideas, and informal questions:

GitHub Discussions. The whole community sees your post; you may get answers from other users faster than from us.
Roadmap for the public board.
Feature requests to file new ideas.

Channel	Typical response
security@toado.dev	Within 48 hours
support@toado.dev	1 to 2 business days
Contact form (toado.dev/contact)	1 to 2 business days
sales@toado.dev	Same day if possible, else 1 business day
GitHub Discussions	Best effort, often community-answered first

We are based in the EU and US time zones. Out-of-hours requests are picked up the next business day.

Browser-specific issues unrelated to our extension. We can only fix things on our side.
Custom integrations we have not built (use the MCP tools for programmatic access today, or talk to us about an enterprise scope).
Recovery of permanently-deleted data after the retention window.

If you believe you have found a security issue:

Email security@toado.dev with a description, reproduction steps, and (optionally) a suggested fix.
We respond within 48 hours.
We work with you on a coordinated disclosure timeline before publicizing.
We do not run a paid bug-bounty program in v1, but we publicly credit reporters who request it.

Please do not file public GitHub issues, social media posts, or blog posts about a vulnerability before contacting us.

See Security for the broader trust model.