Contact
A real person reads these.
There is no support tier and no ticket queue. There is one inbox, and for now it is small enough that everything in it gets answered.
Where to write
No public address is set yet.
A single monitored address belongs here — one, not four departments that all forward to the same place. Until it exists, publishing something that bounces would be worse than publishing nothing.
What is worth writing about
Bugs, especially the ones that lost you work. Anything in the product that behaves differently from how this site describes it — that is a defect in one of the two, and both are worth fixing.
Also: the parts of the impact commitment you think are weaker than they sound. That page is written to be argued with.
What makes a bug report fixable
This app keeps everything in your browser, which makes bugs unusually hard to reproduce from the outside — there is no server log to read and no copy of your document to open. Four lines turn most reports into something that can be fixed the same day:
- What you did, in the order you did it — including the step that felt irrelevant.
- What you expected instead, even when it seems obvious.
- Which browser, and whether it also happens in a different one.
- Whether the console shows anything red. F12, then the Console tab.
If it lost work, say so first. That moves it ahead of everything else in the queue.
What will not get an answer
Partnership proposals for the tree planting from anyone who cannot point at published multi-year survival rates. The criteria are on the impact page, in the order they are weighted.
Status
There is no status page, because there is no server to be down: the app runs entirely in your browser. If it fails to load, the problem is either the page delivery or something in this device's stored data — the command palette's Reset workspace clears the second one, at the cost of everything stored locally.