Control
Tenant isolation
Business access is scoped to active membership and the Event’s permanent Business ID. One entertainment company is not authorized to read another company’s Events.
Security by architecture
One Event. Clear ownership. Intentional access.
Galaxy Cue separates identity, Business relationships, Events, documents, and roles so the system can stay powerful without exposing one company’s work to another.
This page describes the current Galaxy Cue product architecture operated by Galaxy Cue LLC. Security is a continuing, risk-based process—not a certification or a promise of absolute security.
Control
Client-owned access
A Client Account is authorized to read only Events assigned to that authenticated identity and only fields intentionally projected to the Client Portal.
Control
Passwordless authentication
Supabase Auth remains the session authority. Magic Links and email codes create the same verified passwordless session.
Control
Private provider credentials
Email, social, payment, and server credentials are designed to remain in protected server environments rather than public browser code.
Control
Client-safe documents
Business-only fields and internal notes are excluded from Client projections. Private files use short-lived signed access where supported.
Control
Hosted payment safety
Third-party payment providers collect sensitive payment data. Galaxy Cue tracks Event payment requests and verification without intentionally storing card numbers.
Identity and access
A Client Account is a global authenticated person. A Business Connection links that account to one entertainment company. An Event is a project scoped to exactly one Business. These records are related by permanent IDs rather than repeated contact fields.
Business permissions and Client permissions are evaluated separately. Authentication proves identity; database authorization decides which rows and actions that identity can access.
Event data boundaries
Business OS may show client-facing and Business-only Event information for authorized members. Client Portal receives only client-facing data for Events managed by the signed-in account. Workflow stages are calculated from authoritative Event documents and server actions rather than browser labels.
Files and documents
Event files belong to the Event and include an explicit Business-only or Client-shared visibility choice. Private Storage objects are opened with temporary signed URLs. Completed forms remain attached to the Event record.
Connected providers
Galaxy Cue never asks a Business to place secret API credentials in public page code. Transactional email, marketing email, and social provider connections use server-side secrets. Payment checkout remains on the selected payment provider’s secure page.
Deletion and retention
Danger Zone actions require typed confirmation and server authorization. Cancelled incomplete Events follow their configured retention period. Completed Events remain archived until an authorized user intentionally removes them. Financial snapshots may be retained where required for accounting history.
Read the Data Deletion page for the request process.
Report a security concern
If you believe you found a security or privacy issue, contact Galaxy Cue through the verified support channel associated with your account. Do not include passwords, full payment information, private access tokens, or provider secrets in a message.
Before public launch, Galaxy Cue LLC must publish a monitored security contact that also works for locked-out reporters, name the incident-response owners, bind appropriate cyber coverage, and complete the documented database-hardening review. A public policy does not replace those operational controls.