Contact
Talk to a human
We are a small team in early access, so we keep this simple: one address, read by the people who build the product.
We aim to reply within one business day. There is no phone line and no live chat — both would mean answering worse.
What to write about
Support
Something is broken, confusing, or not doing what you expected. Include your firm name and, if you can, the URL you were on. We answer our own support — you will not be routed through a tier-one script.
Sales and evaluation
You are assessing the product for a firm and want a walkthrough, a straight answer about a limit, or help deciding between plans. Open the demo first if you have not; the conversation is better when you have seen it.
Security
If you believe you have found a vulnerability, write to us with the detail and give us a reasonable window to respond before disclosing. We take reports from anyone and we do not threaten researchers.
Privacy and data requests
Access, export or deletion requests under GDPR or comparable law. We will verify who you are and respond within the statutory period.
Editorial and press
Corrections to an article, a factual concern, or a media enquiry. Our correction practice is set out in the editorial policy.
Answer it yourself, faster
A good share of what reaches us is already written down. The help centre covers task-level questions by module, the documentation explains how the product is put together, the roadmap says whether something is coming, and the security page is honest about our current posture.