With TAP support

Get help

Email support@zephyr-cloud.io for product support, billing, privacy, security or abuse. State the category and affected product in your subject. This shared destination does not require a paid seat or a With TAP account.

Use product support for product errors and access questions; billing support for payment, duplicate charges, cancellations and refunds; privacy support for personal-data requests; security reporting for suspected vulnerabilities or account compromise; and abuse reporting for harmful or unlawful use. These destinations must be available without a paid product seat. Public booking guests must be able to reach privacy and abuse reporting without creating an account.

Include the affected product, a brief description, what you expected, the approximate date and timezone, and a purchase/invoice, operation or public page reference if available. For a cancellation or refund, say explicitly which one you want; if both, request both. A billing administrator may need to verify workspace authority. A guest should identify the relevant booking through its authorized recovery flow, rather than sharing another guest's private answers.

Do not send passwords, card numbers, session cookies, recovery tokens, API keys, provider tokens, full mailbox exports or private documents in an initial report. Remove personal information from screenshots. We may ask for narrowly relevant details through an appropriate verified channel. We verify authority before providing private data or changing access; possession of an email address or public page URL alone is insufficient.

If a payment is pending, retain and resume its original purchase rather than making a second payment. If paid access is lost, billing recovery remains the route for an authorized billing administrator. Cancellation, refund, seat changes and data deletion are separate requests and confirmations.

Service expectations

With TAP is dogfood software we use ourselves. Support is best effort. We offer no guaranteed response time, resolution time, uptime SLA, round-the-clock monitoring or emergency service in this plan. We prioritize by impact and available capacity. This does not limit legally required response or remedy obligations. Check critical work and keep copies of important material.

For a security or abuse report, identify the public endpoint or operation and the issue, minimizing disclosure of other people's information. Do not exploit a suspected issue to access more data, disrupt service or contact affected users. For a privacy request, state the right or outcome you seek and the relevant workspace or booking, without sending unnecessary identification documents. We will explain any proportionate identity/authority verification and applicable next steps.

If dissatisfied, reply with the existing case reference and ask for review. Applicable rights to complain to a supervisory authority, seek a legal remedy or dispute a charge remain available. Do not rely on these channels for emergency assistance.