# Contact

> How to reach Mnemo: support, sales, security disclosure, and partnerships. Founder-led — email shah@mnemohq.com and get a reply within one business day.

Canonical URL: https://mnemohq.com/contact

Mnemo is founder-led. There is no ticket queue and no chatbot in front of a human — you are writing to the person who builds the thing.

The general address is shah@mnemohq.com. It reaches a monitored mailbox and is the right choice when you are not sure which of the addresses below applies. Expect a reply within one business day; Mnemo operates on Pakistan Standard Time (UTC+5), so a message sent late in the US afternoon is usually answered the following morning your time.

## What to write about

- Product support — an API call behaving unexpectedly, a retrieval result you cannot explain, quota or rate-limit questions, SDK bugs. Include your workspace ID and the request ID from the response so the failure can be traced end to end. Email shah@mnemohq.com.
- Sales and evaluation — pricing beyond the published tiers, volume commitments, security questionnaires, DPAs, procurement paperwork, or an architecture walkthrough with your team. Email sales@mnemohq.com.
- Security disclosure — send vulnerability reports to security@mnemohq.com. Coordinated disclosure is welcome and reports are acknowledged within one business day.
- Privacy and data requests — access, export, correction, and deletion requests go to privacy@mnemohq.com, which is also the Data Protection Officer address. Contract and legal questions go to legal@mnemohq.com.
- Partnerships and integrations — framework maintainers, agent platforms, and tooling vendors who want a first-class Mnemo integration should write to shah@mnemohq.com with a sentence on what your users would gain.

## Elsewhere

- X: https://x.com/shhahhussain — release notes, benchmark writeups, and the fastest route to a short answer.
- GitHub: https://github.com/shhahhussain — the SDKs, the MCP server, and the open parts of the stack.
- Live service status: https://status.mnemohq.com — check here before reporting an outage.

## Before you write

Three places answer most incoming questions faster than an email round trip: the API documentation for endpoint behaviour and authentication, the benchmarks page for the full per-category LongMemEval breakdown and how to reproduce it, and the trust and security page for encryption, data residency, and compliance status.

## Explore Mnemo

- [Mnemo API documentation](https://mnemohq.com/docs)
- [Pricing](https://mnemohq.com/pricing)
- [Benchmarks](https://mnemohq.com/benchmarks)
- [Company Brain for Slack](https://mnemohq.com/brain)
- [Ask Mnemo widget](https://mnemohq.com/widget)
- [Data-source connectors](https://mnemohq.com/connectors)
- [Framework integrations](https://mnemohq.com/integrations)
- [Trust and security](https://mnemohq.com/trust)
- [Contact](https://mnemohq.com/contact)
- [llms.txt](https://mnemohq.com/llms.txt)
- [OpenAPI 3.1 specification](https://mnemohq.com/openapi.json)

---

This is the Markdown representation of https://mnemohq.com/contact, served by content negotiation on `Accept: text/markdown`. Machine-readable index: https://mnemohq.com/llms.txt · https://mnemohq.com/openapi.json · https://mnemohq.com/sitemap.xml
