How to reach the Questro team: support, security reports, billing and refunds, privacy requests, and developer API questions, with what to include so the first reply is useful.
Questro is reached by email at support@questro.live. That single mailbox handles product support, security reports, billing and refund questions, privacy requests, and questions about the public developer API, and it is the address printed on the security, privacy, and terms pages. There is no phone line and no live chat: an event team is usually mid-setup when it writes in, and email keeps the links, screenshots, and event details in one place instead of scattered across a call. Questro is operated as a remote team, and the service is governed by the laws of Singapore as set out in the Terms of Service.
Name the tool — Timer, Q&A, Teleprompter, or AI Interpreter — and say whether the problem is on an operator or control page or on a public display page, because those are different URLs with different permissions. Paste the page URL, note the browser and device the screen is running on, and give the event date and time zone if the session has not happened yet, so anything time-critical is treated as time-critical. For AI Interpreter issues, include the source and target languages and roughly when in the session the problem appeared. Do not send passwords, and do not send an operator or control link in a public thread: those links grant control of the live room.
Report a suspected vulnerability or data-handling concern to the same address with enough detail to reproduce it, and do not test against a live event that other people are relying on. Privacy requests — access, correction, deletion, or questions about how data is retained — are handled by email as described in the Privacy Policy; account deletion is also available inside the app. Payments run through Lemon Squeezy, so subscription changes, invoices, cancellations, and refunds are handled through the customer portal linked from your billing settings, with the mailbox as the fallback when a charge does not look right. Developer questions about Personal Access Tokens, the REST endpoints under /api/v1, or outbound webhooks are welcome; the endpoint reference and OpenAPI specification live on the developers page.