The task and the environment
Identify what you wanted to do, the Galactre path, browser or application environment and when the issue occurred.
GALACTRE / HELP & CONTACT
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
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
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.
Account access
Use Galactre’s login or registration flow. Identity, account permissions and administrator access are separate checks.
API & development
Compare your request with the current browser contract before reporting an integration failure. The published API uses same-origin sessions and CSRF protection.
Billing & credits
Use authenticated billing to inspect an invoice you own. Checkout progress, confirmed payment and recorded credit are separate states.
Privacy & security
Review the privacy notice and remove sensitive information from any general feedback. No dedicated vulnerability mailbox or private report endpoint is published in this release.
Product integrations
Start with the workflow and required interface. Ecosystem membership alone does not mean a native connector or commercial agreement exists.
02 / MAKE THE PROBLEM UNDERSTANDABLE
A small, precise reproduction is more useful than a large unfiltered export. Keep private data out of general feedback.
Identify what you wanted to do, the Galactre path, browser or application environment and when the issue occurred.
Use short, non-sensitive steps. State the expected result and the actual observed behavior separately.
Record a request ID, HTTP status or error code when available. Redact account secrets, payment details and private inputs.
Only send a report through an official destination for its sensitivity. A model conversation is not a private support ticket.
03 / SENSITIVE CONCERNS
A general chat or community draft is not a verified private disclosure channel.
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 noticeNo dedicated private security endpoint is published. Do not post secrets or exploit details publicly. Revoke exposed credentials through the service that issued them.
Keep invoice and transaction details inside the authorized billing workflow. Check the invoice owner, environment and outcome before initiating another payment.
Payment verification guide04 / CONTACT QUESTIONS
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.
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.
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.
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.
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.
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.
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