# Security and privacy

> How API keys and MCP tokens are protected, what an AI assistant can reach, how content is moderated, and what users should know about their data.

## API keys

- A key is shown once, when it is created. Moknah stores only a SHA-256 hash and the first characters for identification, so a lost key cannot be recovered; create a new one.
- A key can be limited to chosen services, to a total number of credits, to a list of IP addresses, and to an expiry date.
- A key can be revoked at any time in the dashboard. A revoked, expired or over-limit key is refused at once.
- When an account is deactivated, all of its keys stop working.

Practices to follow:

- Keep keys on a server. Never place one in a web page, a mobile app or a public repository.
- Use one key per integration, with a credit limit, so a leak or a bug has a bounded cost.
- Prefer the `Authorization` header. The `?api_key=` form for WebSockets puts the key in a URL.
- Rotate a key that may have been exposed: create a new one, switch, revoke the old one.

## MCP connections

- An assistant is authorized with OAuth 2.1 and PKCE: the user signs in to Moknah and approves the connection. The assistant never sees the password.
- Tokens are stored as hashes.
- An assistant acts as the user who authorized it and can reach only that user's content and their team's.
- Administrator privileges are removed for every MCP call, even when the user is an administrator.
- Deleting needs an explicit confirmation, and spending needs an explicit approval.
- Every tool call is recorded with the tool, its arguments in shortened form, the credits estimated and charged, and the result. Users see their own calls under **AI Assistant**, **Activity**.

## Callbacks

Article to Speech results are signed with HMAC-SHA256 so the receiving server can verify that they came from Moknah. See [Article to Speech](../api/article-to-speech.md#verifying-the-signature). Callback URLs that point to private network addresses are refused.

## Your content

- Content is private to the account that created it, and to its team where the team's permissions allow.
- Videos uploaded for burning subtitles, and the subtitled copies, are deleted right after use or after 10 minutes at most.
- Cloned voices that go unused are deleted automatically; see [Voice Cloning](../products/voice-cloning.md).
- An account can be deleted by its owner at https://moknah.io/account/delete/.

The full terms are in the privacy policy at https://moknah.io/privacy/ and the terms of service at https://moknah.io/terms/.

## Content moderation

Text sent for speech generation is checked automatically, in the web app, the API, the streams and MCP alike. Text that clearly breaks the content policy is refused (`CONTENT_REJECTED`). Text that may break it can be flagged for review by the Moknah team while the audio is still returned. The policy is at https://moknah.io/content-policy/.

## Voice rights

Clone only a voice you own or have permission to use.

## What this documentation does not contain

No secret, customer record or private configuration is published here. An AI system cannot obtain another user's data, keys or content through these documents or through the MCP server.

## Reporting a problem

Report a suspected vulnerability or a leaked key to support@moknah.io.
