ReportGem Support

Contact support

We review support requests during normal Hong Kong business operations. Response time depends on severity, investigation requirements, and the information provided. For an urgent security issue, put SECURITY at the beginning of the subject line.

OAuth, connection, and sign-in

1. Confirm you can sign in to the same ReportGem account on reportgem.com.
2. Disconnect the ReportGem plugin from the client and authorize it again if scopes changed or a token was revoked.
3. Approve only the scopes shown by ReportGem. Stop and contact us if the authorization page or redirect domain looks unexpected.
4. If the client reports 401, reconnect the account. If it reports 403, confirm that the account has an active entitlement and the requested scope.

Research access, quotas, and result issues

Some MCP tools require an active ReportGem entitlement and are subject to tool-unit, daily, monthly, concurrency, and cost controls. If a request is blocked, include the exact error code and request ID in your support email. Do not include tokens.

For an incorrect or incomplete result, include the query, expected company or topic, relevant date range, source title or URL, and why the result appears wrong. ReportGem is a research-discovery service; outputs should be checked against the linked source before relying on them.

Billing and entitlement support

Purchases and plan changes are completed directly with ReportGem, outside the ChatGPT or Codex plugin. For order questions, include the ReportGem account identifier, order number, purchase date, and issue. Do not email full card or wallet details.

Cancellation, renewal, and refund eligibility are governed by the terms shown at purchase, your order, applicable law, and the ReportGem Terms of Service.

Privacy and data requests

Email contact@reportgem.com with the subject Privacy Request to request access, correction, deletion, restriction, portability, or another right available under applicable law. Identify the relevant account and country or region. We may ask for reasonable identity verification.

See the Privacy Policy for details on information processed by the website, OAuth service, MCP server, and plugin.

Security reports

Send suspected vulnerabilities, credential exposure, unauthorized access, or abuse to contact@reportgem.com with SECURITY in the subject. Include reproducible steps and the affected URL or component, but do not access other users' data, degrade the service, or include active secrets.

If you believe a credential is exposed, revoke or rotate it immediately and then contact us. Do not continue testing on production after confirming a security issue.

OpenAI plugin review account

Reviewer credentials are provided only through the private OpenAI submission portal. They are not published on this page, in source code, or in plugin files. OpenAI reviewers who cannot access the submitted demo account should use the support email above and identify the plugin as ReportGem Research.

中文支持

ReportGem 网站、账户、研究服务、MCP 和 ReportGem Research 插件的官方客服邮箱为 contact@reportgem.com。建议邮件主题写明“ReportGem 客服—账户 / OAuth / 权益 / 账单 / 隐私 / 安全”。

请提供受影响的账户邮箱或手机号、发生时间、使用的客户端（如 ChatGPT 或 Codex）、工具名称、可用的请求编号和问题描述。请勿发送密码、访问令牌、刷新令牌、完整银行卡资料或私密来源文件。

遇到 OAuth 问题时，请先确认可登录同一 ReportGem 账户；如权限范围已更新或令牌被撤销，请断开插件后重新授权。401 通常需要重新连接账户；403 时请核对账户权益和所需权限。

插件中的调用可能受工具用量、日/月限额、并发和成本控制。购买和套餐变更在 ReportGem 直接完成，不在 ChatGPT 或 Codex 插件内完成。账单咨询请提供订单号和购买日期，不要发送完整支付信息。

隐私请求请使用主题“Privacy Request / 隐私请求”；安全漏洞、凭证泄露或未授权访问请在主题开头标明“SECURITY”，并避免访问他人数据或继续对生产环境进行破坏性测试。