CamplaxSet up the addresses below, confirm their owners and response targets, and replace brackets before publishing. Do not direct customers to an unattended mailbox or promise a response time that the team cannot meet.
Support routes
| Need help with | Where to go |
|---|---|
| Existing project or account | Sign in and use the Support page so the request is associated with the right account. |
| Billing, cancellation, or refund | [[billing support email]]. Include the account email and charge reference; never send full card data. |
| Privacy request | [[privacy contact email]]. |
| Security vulnerability or incident | [[security contact email or disclosure form]]. Do not include credentials or exploit code in a public post. |
| Abuse report | [[abuse-reporting email]]. |
| Legal notice | [[legal notice address and email]]. |
What to include
Tell us the project name, the email on the account, a concise description, timestamps, and any safe-to-share request or incident identifiers. Redact secrets, access tokens, passwords, and payment-card numbers. We may ask you to verify account authority before discussing project information.
Support and incidents
For a service-wide problem, check the Status & Incidents page and then use the support route if your project needs individual help. Automated support tools cannot make billing, refund, legal, security, or account-access commitments; those cases must reach an authorised human.