---
title: "Contact Calamophyton support."
description: "Route product, documentation, legal, and security matters without exposing sensitive information."
updated: "1 September 2026"
candidate_route: "/docs/resources/support"
---

# Contact Calamophyton support.

Route product, documentation, legal, and security matters without exposing sensitive information.

## Choose the address for your inquiry

Send product, documentation, and access inquiries to support@calamophyton.com, legal and contract inquiries to legal@calamophyton.com, and vulnerability reports to security@calamophyton.com. legal@calamophyton.com serves as a contractual notice address only if an executed agreement expressly designates it.

On 1 September 2026, messages sent from an external account to the three addresses separately and together were received. The test verified delivery only, not response times, handling personnel or their authority, retention, or a secure transfer channel.

- [Write a product, documentation, or access inquiry](mailto:support@calamophyton.com?subject=Calamophyton%20product%2C%20documentation%2C%20or%20access%20inquiry&body=Organization%3A%0AInquiry%20type%3A%0ARelated%20page%3A%0ADescription%3A%0A%0ADo%20not%20attach%20customer%20source%20data%2C%20credentials%2C%20or%20sensitive%20information.) — support@calamophyton.com
- [Write a legal or contract inquiry](mailto:legal@calamophyton.com?subject=Calamophyton%20legal%20or%20contract%20inquiry&body=Organization%3A%0ASubject%3A%0ARelated%20agreement%20or%20document%3A%0ADescription%3A%0A%0ADo%20not%20attach%20legal%20originals%2C%20signature%20copies%2C%20or%20personal%20data.) — legal@calamophyton.com
- [Write a security report](mailto:security@calamophyton.com?subject=Calamophyton%20security%20report&body=Contact%20email%3A%0AAffected%20public%20page%20or%20feature%3A%0ANon-sensitive%20summary%3A%0ARequest%20a%20secure%20transfer%20path%3A%20Yes%0A%0ADo%20not%20include%20exploit%20code%2C%20credentials%2C%20customer%20data%2C%20or%20sensitive%20technical%20detail%20in%20this%20first%20message.) — security@calamophyton.com · keep the first message non-sensitive

> **Safe first contact:** Ordinary email is not a transfer path for customer source data, credentials, legal originals, executable exploit code, or sensitive technical detail. Include only enough information to identify the matter, then request a separate secure transfer path if one is needed.

## Provide a safe, reproducible report

- Time and relevant page or workspace path
- Status or error code displayed on the screen
- Expected behavior and observed behavior
- Redacted screenshot only when permitted by your organization

## Do not include secrets or source data

- Passwords, one-time codes, recovery codes, or tokens
- API keys, authorization headers, or internal secret locations
- Raw customer data or an unauthorized screen capture
- Exploit details in a general support message

> **Security reports:** Request a secure channel before sending sensitive technical detail.

## Report a documentation issue

For an error in facts, terminology, links, accessibility, or rendering, send the exact page path, the affected sentence, and the expected correction. Do not attach customer data or credentials.

- Exact documentation URL
- Affected title or sentence
- Browser and viewport when the issue is reproducible
- A redacted screenshot only when permitted

- [Write a documentation correction](mailto:support@calamophyton.com?subject=Calamophyton%20product%2C%20documentation%2C%20or%20access%20inquiry&body=Organization%3A%0AInquiry%20type%3A%0ARelated%20page%3A%0ADescription%3A%0A%0ADo%20not%20attach%20customer%20source%20data%2C%20credentials%2C%20or%20sensitive%20information.) — support@calamophyton.com

> **Documentation route:** Send the exact page and requested correction to support@calamophyton.com. Do not attach customer source data, credentials, or legal originals.

## Use the separate route for a vulnerability report

Report a suspected vulnerability affecting this site or its published developer materials to security@calamophyton.com. In the first message, include only the affected public page or feature and a non-sensitive summary. Request a secure transfer path before sending exploit code, credentials, customer material, or sensitive technical detail.

- [Write a vulnerability report](mailto:security@calamophyton.com?subject=Calamophyton%20security%20report&body=Contact%20email%3A%0AAffected%20public%20page%20or%20feature%3A%0ANon-sensitive%20summary%3A%0ARequest%20a%20secure%20transfer%20path%3A%20Yes%0A%0ADo%20not%20include%20exploit%20code%2C%20credentials%2C%20customer%20data%2C%20or%20sensitive%20technical%20detail%20in%20this%20first%20message.) — security@calamophyton.com
- [Security contact file](/.well-known/security.txt) — RFC 9116 security contact file

> **Verified boundary:** Message delivery was verified. This test did not verify response time, authorized handling, retention, secure transfer, resolution time, or closure procedure.

---

Published route: /docs/resources/support