Sending feedback
There is a Send feedback entry in the sidebar, and a Report this error button on the screen you get when something in the app breaks. Both open the same box: one field, and a choice between Something is broken and An idea.
It goes to the people who run this service. Every report is read.
What travels with a report
A report on its own is often not enough to act on — "it did not work" describes a hundred different defects. So a few facts about the situation go with it, and the box shows you all of them, in full, before you send anything:
| Screen | Which screen you were on, as the app's own name for it — never the address, so it says a page rather than which page. |
| Version | Which build you are running. |
| Window | How big the window was. |
| Input | Whether you were using a mouse or a finger. |
| Workspace | Which workspace you were in, if any. |
| Recording | What the app did in the last few minutes (see below). |
There is no switch to turn any of them off, and that is deliberate: an attachment you can leave out is one that turns out to be missing in exactly the report that needed it. What you are owed instead is that nothing is sent that you could not read first — so open the list and look.
The recording
The app keeps a short, rolling record of what it did — which screen you moved to, which gesture ran and what it answered, which request came back with an error, what kind of device this is. It holds a few minutes and then forgets the oldest entries.
It records structure and never content. That is not a policy, it is how the
recorder is built: everything it stores passes through a filter that keeps an
identifier or a single short word and replaces every other piece of text with
its shape — <text:23>, meaning there was a string, 23 characters long. The
title of your page, the text of a row, the subject of a meeting: none of them
survive it, whatever is on screen when you write.
Identifiers do survive, and that is deliberate too. An id is a handle, not content — without it, two reports about "a row" cannot be told apart. It also means a recording is something to send to the people running the service, and not something to hand to a stranger.
The recording stays on your device unless you send it. It never leaves on its own.
What happens next
The report is stored, and the people running the service are notified. Reports are read, sorted and closed when they have been dealt with.
What the product does not do is promise a reply. There is no ticket to follow and no status to check. If an answer is needed, it comes as an ordinary mail to the address on your account — from a person who decided to write, not from a workflow.
What is stored, and for how long
A report holds what you wrote, the facts in the table above, your account and the workspace you were in. It is kept until it has been dealt with and is no longer useful; deleting your account deletes your reports with it.
If you would rather say something without any of it being attached to you, use the address in the imprint instead.