Galactre
USD

Choose how catalog prices and estimates appear. Checkout and account records remain in IDR.

Open Chat

GALACTRE / HELP & CONTACT

A clearer question.
A better next step.

Find guidance for conversations, account access, development and billing. Start with the right product workflow and prepare the information that makes a problem understandable.

01 / START WITH THE RIGHT WORKFLOW

What do you
need help with?

Choose a topic for the checks and guides that match your situation. Nothing is sent when you select a topic or copy its checklist.

Chat & models

Troubleshoot a conversation

Start with the current model status and the message shown by chat. A quota, access rule or unavailable model needs a different next step from a response-quality issue.

  1. Check whether the selected model is available and eligible for your session. Guest chat currently uses Lunar.
  2. Read any limit or wait message before retrying. Keep a safe request ID if one is shown.
  3. For answer quality, prepare a short non-sensitive prompt, expected result and the actual response.
  4. Do not repeatedly resend a request with an uncertain outcome; review the conversation or status first.

02 / MAKE THE PROBLEM UNDERSTANDABLE

Useful details.
Only what is needed.

A small, precise reproduction is more useful than a large unfiltered export. Keep private data out of general feedback.

The task and the environment

Identify what you wanted to do, the Galactre path, browser or application environment and when the issue occurred.

A minimal reproduction

Use short, non-sensitive steps. State the expected result and the actual observed behavior separately.

Safe diagnostic evidence

Record a request ID, HTTP status or error code when available. Redact account secrets, payment details and private inputs.

A verified destination

Only send a report through an official destination for its sensitivity. A model conversation is not a private support ticket.

03 / SENSITIVE CONCERNS

Choose the channel
as carefully as the details.

A general chat or community draft is not a verified private disclosure channel.

Privacy and account data

Review the privacy notice and owned conversation controls. Do not include another person’s records or account credentials in a general example.

Read the privacy notice

Security reports

No dedicated private security endpoint is published. Do not post secrets or exploit details publicly. Revoke exposed credentials through the service that issued them.

Billing references

Keep invoice and transaction details inside the authorized billing workflow. Check the invoice owner, environment and outcome before initiating another payment.

Payment verification guide

04 / CONTACT QUESTIONS

Know the next step.
Keep expectations clear.

Which model details should I include in a diagnostic brief?

Use the resolved model_id and model_version from the response, along with a safe request ID and the approximate time. Mention whether you selected a family default or a pinned release. Never include credentials, session cookies or private prompt instructions.

Where is the official contact email or support form?

A verified public mailbox and working contact submission endpoint are not configured in this release. This page provides self-service guidance and copyable checklists; it does not pretend to send or queue a message.

Will GT Chat create a support ticket or change my account?

No. A model conversation can help explain a problem but does not create a support ticket, grant account access, settle an invoice or execute an administrative action. Use the appropriate authenticated product controls.

Does copying a checklist send my information?

No. Copying is a local action. No report, payment, prompt or account data is submitted by these controls. You decide whether to keep or share the checklist through a verified destination.

What should I do when a payment outcome is uncertain?

Inspect the owned invoice in authenticated billing and use its status verification or reconciliation workflow. Avoid a duplicate payment based only on a delayed browser response. Do not share a full receipt or payment details in a public report.

Is there a support response time, emergency line or bug bounty?

No public response-time commitment, emergency contact or bug bounty program is published by this release. Do not assume a similarly named account or community link is an official private channel.

Where can I prepare general product feedback?

The Community page has a local editable feedback brief and participation guidance. It does not submit a ticket or publish your report. Remove private information and verify the destination before sharing.

CONTINUE WITH A USEFUL GUIDE

Find the context.
Move forward with clarity.