Contact and collaboration

Send product, support, privacy or security requests to the published intake mailbox.

On this page
  1. Prepare your request
  2. Published intake
  3. Share only what is needed
  4. How website contact messages are handled

Prepare your request

Name the product (for example App Call Chat Free), your role (User, SME or Developer) and what you need. Do not include passwords, tokens or customer data.

Published intake

Website contacts for products, support, privacy and security intake use [email protected]. Sending a message does not create an order or grant product access.

Share only what is needed

Describe the issue first. Avoid attaching full personal records. If ownership needs verification, we will explain a suitable method through the published contact.

How website contact messages are handled

The contact form collects your name, email, role (User, SME or Developer), optional organization, subject and message to answer support requests. When delivery is configured, a Cloudflare Pages Function validates the request and Resend transmits email to [email protected] with your address as Reply-To. Form contents are not stored in a website database. Mail secrets and a verified sender must be present for online delivery; otherwise the page shows the mailbox so you can email directly. Do not send passwords, tokens or other people’s sensitive data.

Send a request

Use this form for User, SME or Developer requests. When configured on Cloudflare Pages, the browser sends through a Pages Function protected by Turnstile, then Resend delivers to [email protected]. Cache-based throttling is best-effort only. Until secrets, allowed origins, Turnstile keys and a verified sender are present, use the mailbox link if sending is unavailable.

Complete the security check before sending. Cloudflare Turnstile verifies the request; tokens cannot be reused.

Attachments are not accepted on this form.

Do not include passwords, tokens, one-time codes or other people’s sensitive data.