Contact
Talk to the people building it.
No tier-one script and no chatbot loop. Each address below reaches the team that owns the work — including when the honest answer is “not yet”.
- Answered by the team that ships it
- No chatbot loop
- Security reports prioritised
Product & accounts
Workspace, exports, billing
Access, invitations, photo uploads, renders, credits, invoices and general data requests.
[email protected]
Privacy & data
Access, deletion, processors
Subject access, deletion and processor questions, answered against the same records our policies describe.
[email protected]
Security disclosure
Private vulnerability reports
Report a vulnerability privately. Please do not test against customer data or live accounts.
[email protected]
What to put in the first email
It usually saves a round trip.
- The workspace name and the project, listing or export involved.
- What you expected, what happened, and when it happened.
- The browser, file type and size, or the API request id.
- Screenshots if you have them — never passwords, API keys or card numbers.
How a request moves
Three states, no black box.
- 1
Received
A person reads it. Anything automated says that it is automated.
- 2
Answered
A named owner replies with what we know, or a date we can defend.
- 3
Recorded
Answers that keep coming back are written into the public FAQ.
Response times are stated in the reply, not guaranteed on this page. Security reports are prioritised over general support.