The Memoket API handles credentials and recording-derived data. Please do not open a public GitHub issue for a suspected vulnerability, access token, webhook secret, raw payload, transcript, or other personal data.

A verified private vulnerability intake is not currently published. Request a secure reporting channel through the official Memoket website without including vulnerability details, credentials, request payloads, or recording content in the initial message.

Once a secure channel is confirmed, include a concise impact summary, affected endpoint, reproduction steps, and relevant request IDs. Use synthetic data and redact credentials and recording content.

Documentation errors that do not expose sensitive information can be reported through GitHub Issues.