# Contact Nexus Journal

> For Nexus Journal product or documentation requests, use the official support channel published in the application or your purchase confirmation and include a concise description, the affected public URL or feature, and non-sensitive reproduction steps.

Use this page for product feedback, corrections to public documentation, and help identifying the right Nexus Journal workflow. To protect account and trading data, do not send credentials, full backup files, or broker secrets in an unsolicited message.

Reviewed 2026-07-15 by Nexus Journal product team.

## What to include in a request

For a product issue, state the feature, browser or device, approximate time, expected result, actual result, and safe reproduction steps. For an import issue, include the broker, report type, date range, and the field names involved, but redact account numbers, tokens, API secrets, order identifiers, and personally identifying information unless a secure support workflow explicitly requests them.

For a public documentation correction, include the page URL, the specific claim that appears inaccurate, and the source or product behavior that supports the correction. Nexus Journal aims to correct material discrepancies in the canonical public page, its Markdown twin, and related discovery files together.

## Account and billing safety

Never share a broker password, OAuth token, API secret, Google access token, payment-card data, or complete personal backup through an unverified channel. Nexus Journal support should not need those items to understand an initial request. If a request involves a purchase or account, refer to the verified details in the application or payment confirmation rather than posting them publicly.

Nexus Journal is software for organizing and reviewing trading records. Support can clarify the product workflow, but it cannot provide regulated investment, legal, or tax advice and cannot make trading decisions for a user.

## Response and scope

Support availability and response times can vary. Broker formats, third-party APIs, and data quality may limit what can be diagnosed from a report. Where a workflow is unsupported or a source field is absent, the appropriate response may be a documented limitation or a request for a different official broker export.

The official public resources for product evaluation are the homepage, pricing page, supported-brokers guide, compatibility guide, privacy page, and calculation methodology. These pages are also available as machine-readable Markdown for agents and technical evaluators.