Get in touch, and know where the message actually goes
One form, six topics and a seventh for corrections to anything we have published. Below it are the specialist inboxes, so a security researcher or a rights holder does not have to route through a general queue, and a plain statement of what happens if the form cannot reach us.
Published Updated Published by The Foundable team
What we aim to reply in
| Topic | Inbox | Reply target |
|---|---|---|
| Support and product questions | hello@foundable.example | 1 business day |
| Pricing and billing | hello@foundable.example | 1 business day |
| Partnerships | hello@foundable.example | 3 business days |
| Press | hello@foundable.example | 3 business days |
| Hiring | hello@foundable.example | 5 business days, including a no |
| Factual correction to a published page | legal@foundable.example | 3 business days, with a dated fix |
| Security report | security@foundable.example | 1 business day to acknowledge |
- Support and product questions
- Inbox
- hello@foundable.example
- Reply target
- 1 business day
- Pricing and billing
- Inbox
- hello@foundable.example
- Reply target
- 1 business day
- Partnerships
- Inbox
- hello@foundable.example
- Reply target
- 3 business days
- Press
- Inbox
- hello@foundable.example
- Reply target
- 3 business days
- Hiring
- Inbox
- hello@foundable.example
- Reply target
- 5 business days, including a no
- Factual correction to a published page
- Inbox
- legal@foundable.example
- Reply target
- 3 business days, with a dated fix
- Security report
- Inbox
- security@foundable.example
- Reply target
- 1 business day to acknowledge
- Targets, not guarantees. A median response time is not published yet because there is not enough traffic for the median to mean anything.
Privacy, abuse and copyright reports currently arrive at legal@foundable.example. Separate privacy@, abuse@ and dmca@ addresses are named in our legal pages and are routed to the same place today; when they are separated, this table changes first.
Corrections are handled here, in public
This is the published channel for factual corrections to research protocols, guides and comparison pages. Include the page, the exact line and what you believe is wrong. A typographical fix is made and dated on the page; a change of meaning creates a new version with the earlier one kept available. We would rather publish a correction than defend a number.
What we do with what you send
- We use your email and message to answer you. Not for marketing, and not to add you to a list.
- There is no consent checkbox because there is nothing to consent to beyond a reply.
- If you send a security report, do not include live credentials or personal data belonging to someone else.
- Attachments are not accepted through this form; say what you have and we will tell you where to send it.
Send a message
We use these details to answer you and for nothing else. Target reply time: one business day for support and product questions, three for partnerships, press and hiring.
Related Foundable resources
Limitations and corrections
- There is no contact endpoint in this build yet. The form tries to post, and when it cannot, it says so instead of showing a success screen.
- When delivery fails, your message is kept in your own browser under fnd.contact.outbox and a prefilled email is offered. Nothing is transmitted to us until you send that email.
- The reply targets above are commitments we have not yet measured against traffic. No median or queue depth is published.
- Specialist inboxes for privacy, abuse and copyright are named but currently route to the legal address.
Corrected in public: tell us what is wrong at /contact and the change is dated on this page.
Prefer a person over a form?
The inboxes above are real addresses. Writing directly is fine and often faster.
AI output needs your review. No income is promised or guaranteed.