Support and Contact
How users, OpenAI reviewers, and MCP client operators can get help with XMemo account access, OAuth connection, memory tools, privacy requests, and security concerns.
- Use the public support channel for product questions, setup problems, reviewer access, privacy requests, and security reports.
- Never include bearer tokens, OAuth codes, cookies, API keys, raw memory content, trace IDs, or customer secrets in a public support issue.
- OpenAI reviewers should use the provided demo account and the reviewer notes from the app submission package.
Public support channels
Use the XMemo contact aliases for private marketplace, account, privacy, and security requests. The public client issue tracker remains available for non-sensitive setup questions, reproducible bugs, and documentation requests.
- General support: support@xmemo.dev
- Marketplace review coordination: review@xmemo.dev
- Privacy requests: privacy@xmemo.dev
- Security reports: security@xmemo.dev
- Support URL: https://github.com/yonro/memory-os-cli/issues
- Include browser/client name, expected behavior, actual behavior, and redacted screenshots or recordings when useful.
- For account-specific or sensitive requests, provide only enough metadata for the operator to locate the case without exposing secrets in public.
Marketplace reviewer assistance
Reviewers should be able to authorize XMemo through OAuth, discover tools, run read/write test prompts, and reconnect without manual token handling.
- Use a dedicated reviewer workspace with synthetic sample memory.
- No extra MFA or external network access should be required for the reviewer demo account.
- If a review case is rejected, respond through the marketplace case thread with corrected evidence and a concise remediation summary.
Privacy and security requests
Privacy, deletion, export, redaction, and security concerns should be handled through authenticated account workflows or a private operator channel when public issue details would expose sensitive data.
- Do not post memory content, tokens, cookies, authorization headers, or private account identifiers in public support threads.
- Use redacted evidence, request timestamps, affected surface, and high-level reproduction steps instead.
- Operators should record completion evidence with counts, hashes, timestamps, and redacted references rather than raw customer data.
Public support path for ChatGPT app review, hosted MCP onboarding, privacy requests, and operational escalation.