> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atlasent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact

> How to reach AtlaSent for support, security, privacy, procurement, legal, and general inquiries.

<CardGroup cols={2}>
  <Card title="Get help" icon="life-ring" href="/trust/get-help">
    Sign-in help, support, security, privacy, procurement, and service-status paths that do not require Console access.
  </Card>

  <Card title="Procurement & diligence" icon="file-shield" href="/trust/procurement">
    Start here for security, legal, compliance, and controlled diligence materials.
  </Card>
</CardGroup>

## Who to email for what

| Topic | Email |
| - | - |
| Security vulnerability report | `security@atlasent.io` |
| Privacy / data subject request | `privacy@atlasent.io` |
| Compliance / regulated-data questions | `compliance@atlasent.io` |
| Sub-processor questions | `subprocessors@atlasent.io` |
| Legal / contracts / DPA / MSA | `legal@atlasent.io` |
| Procurement / vendor onboarding | `compliance@atlasent.io` |
| Product support / sign-in help | `support@atlasent.io` |
| Abuse / AUP report | `abuse@atlasent.io` |
| General / sales | `hello@atlasent.io` |

## Safe information to include

For support or access problems, include your company name, work email, issue category, a non-sensitive description, and a request/reference ID if one is safe to share.

<Warning>
  Do not send passwords, API keys, signing material, recovery codes, regulated data, customer production payloads, or other secrets through a public contact channel.
</Warning>

## Security reports

Use Responsible disclosure for vulnerability-reporting guidance.

## Service availability

Check Status before opening a service-availability request.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.