Galactre
USD

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

Open Chat

GALACTRE / PRIVACY NOTICE

Your conversations. Clear data boundaries.

Understand the account, conversation, payment and operational data Galactre processes, the controls available to you and the limits of the current retention and contact policies.

Implementation review · 3 November 2026

Owner-scoped history

Conversation access is checked against its guest or account owner.

Bounded processing

Submitted text and bounded recent context are processed to deliver responses.

Available controls

Review conversation deletion, browser preferences and authenticated billing separately.

01

Scope of this notice

This notice covers the current Galactre website, browser chat and account billing implementation. It distinguishes actual behavior from policies that have not yet been published.

Identity and payment services participate in specific workflows. A complete operator contact, legal entity disclosure and processing register are not supplied by this release.

02

Information processed

The information needed depends on the feature. Public browsing, guest chat, account conversations and credit billing have different requirements.

  • Account context: identity subject, approved client and access information returned through the identity service. Login credentials are not sent in chat JSON.
  • Conversation content: submitted text, assistant responses, references and timestamps for history and continuation.
  • Operations: request references, access decisions, outcomes and usage records. Guest quota buckets use keyed session/IP hashes; infrastructure may have separate access logs.
  • Billing: invoice owner/references, credit quantity, amount, currency, status and verification evidence.
  • Account operations: key verifiers and scopes, team membership and invitation email/roles. Plaintext server keys and invitation tokens are shown once; only verifiers persist. Team membership does not share personal history, keys or balance.
  • Browser storage: essential session cookies, a per-tab pending response identifier for reconnect recovery and local preferences described on the Cookies and sessions page.

03

Why data is used

Relevant data establishes access, delivers responses, retains owned history, enforces configured limits, verifies payments and supports review of operational failures.

Public guides do not require a contact submission or community membership. Checklist and feedback controls do not send a report or prompt to a model. A complete jurisdiction-specific legal-basis register is not yet published.

04

Model processing and service providers

Submitted messages and bounded recent context may be processed by service providers to deliver responses. A model family name does not establish a separate residency or training policy.

This release does not publish a complete subprocessor list, processing-location register, provider retention schedule, no-training commitment or international-transfer mechanism. Do not assume zero retention, exclusive local processing or a residency guarantee.

Use minimal authorized context. Do not submit passwords, API keys, full payment details or private information you may not disclose.

05

Access and product boundaries

Assistant records can include the requested model, exact resolved release, version and release hash so earlier responses remain attributable after a default changes. Historical records are not relabeled as newer releases. These records follow the same ownership boundary as the conversation.

Conversation routes check the current guest or account owner. An identifier alone does not grant access. Shared ecosystem identity does not merge private product data.

Account and administrator permissions are separate. Billing invoices are scoped to the authenticated owner and configured workspace context; a payment reference is not an authorization credential.

06

Retention and deletion

Guest identities have a configured expiry. Losing the session can make history inaccessible earlier. Bounded cleanup during later guest activity removes expired data; removal is not promised at the exact expiry second.

Request results are encrypted and retained for the database-configured account period (initially 30 days), or until guest expiry. Maintenance clears expired request ciphertext while retaining idempotency tombstones; conversation deletion does not delete that separate replay record. Per-tab recovery stores an opaque request key, never the prompt or response.

Owners can delete conversations through supported controls. This removes their messages and conversation from the active store. Account history has no published automatic deletion schedule in this release.

Payment, usage, security and operational records are separate. A complete backup, restoration, downstream-provider deletion and audit-retention schedule is not yet published. Conversation deletion does not erase all those records.

07

Controls available to you

Use owned history controls to inspect or delete a conversation, and browser settings to manage preferences. Signing out, clearing browser data and deleting server records have different effects.

Access, correction, portability and statutory requests need a verified private process and identity checks. No self-service account-erasure/export endpoint or dedicated privacy mailbox is published. This does not limit rights provided by applicable law.

08

Safeguards and their limits

Conversation text uses encrypted storage. The implementation uses server-side sessions, CSRF for browser mutations, owner checks and server-managed integration credentials. Encryption at rest is not end-to-end encryption; authorized response processing needs the text.

Transport, storage, keys, backups and access controls must be configured correctly. Local HTTP development has different transport protection from HTTPS. No unsupported certification or absolute security claim is made here.

09

Identity and payment workflows

IAM Central processes authentication. Qrisbill supports credit checkout and verified payment outcomes. Inspect the destination, environment and issued invoice before paying.

Galactre retains references and verification status for billing. Do not send passwords, card numbers, bank secrets or unredacted receipts as prompts or public feedback.

10

Changes, questions and policy details

The review date identifies when this implementation notice was prepared. It does not certify that all future deployments have the same configuration. Check the current product interface for operational changes.

The Contact guide explains current channel availability. A verified private privacy/security contact and complete retention, subprocessor and transfer policies still need publication before those commitments can be relied on.

KEEP YOUR NEXT STEP CLEAR

Use the controls.
Understand the boundaries.