Contact
Where to send what.
Questions, security reports, and Cloud or waitlist requests all go to one address. Engine bugs go on GitHub, next to the code and the releases.
support@getarbor.devPick the right place
Each email link fills in the subject for you. Please keep tokens, credentials and private source out of every message and every public issue.
| If it’s about | Send it to | Include |
|---|---|---|
| An engine bug or a wrong answer | GitHub issues ↗ | The output of arbor --version, how you installed it (a release binary or install script, npm, Cargo, Scoop or Docker), your operating system, and the exact command with its output. For a missing or extra caller, a few lines of source that reproduce it and the relationship you expected. |
| A security issue | Email, subject “Security report” | The affected version or URL and a minimal reproduction. Please don’t open a public issue. The security page has the rest. |
| The previous Cloud | Your GitHub username, and whether it’s about your account, its data or billing. Closing the website does not itself delete existing data. | |
| Leaving the waitlist | Nothing else, but send it from the address you joined with. The privacy notice lists what the waitlist keeps. | |
| Anything else | Whatever helps us answer: what you tried, and what you expected. |