Account privacy.
This notice covers the AstraBlox cloud workspace. It supplements the general privacy policy and describes how the account features work.
Discord sign-in
AstraBlox uses Discord as its only public account sign-in method. Discord processes the authorization, and Supabase verifies your account. AstraBlox stores your stable Discord user ID, username, display name, avatar URL, account creation time, and sign-in and activity times. Discord may also provide an account email to the authentication service; it is not displayed in the owner dashboard. Your Discord password is entered only on Discord’s own website.
The browser uses a protected authorization-code exchange with PKCE. Its active AstraBlox session is kept in browser session storage. Sign out when using a shared device. Account suspension, bans, or session revocation can prevent further access.
Saved projects and conversations
Supported project metadata, AI conversations, preferences, and skill configurations are saved in the shared cloud database under your account. Access is checked by the backend for each request. Other users cannot read your account’s workspace.
A sanitized recovery copy may remain in this browser so unsaved work can be recovered after an interrupted connection. Recovery copies contain workspace content, so use a trusted device and clear browser site data when retiring it. Cloud saves keep a limited revision history. Conflicting saves are presented for your decision rather than silently overwriting work.
Connected providers
When you connect an AI or creative provider, its credential is sent over HTTPS and encrypted in the backend credential vault. Credentials are not included in synchronized workspaces and are never returned by the account or admin APIs. Connection names, model availability, status, and the last check time are stored as metadata.
Requests you send to a connected provider include the prompt, relevant conversation context, selected skill instructions, and any attachments needed for the request. The provider’s own privacy and usage terms apply. Disconnect a provider to remove its saved connection and credential from AstraBlox.
Owner administration and activity records
The application owner can review account identity information, account status, activity times, counts of projects, requests and skills, connection metadata, and operational records. The dashboard excludes provider credentials, private tokens, and private project or conversation content.
Request records track provider and model names, completion or failure, duration, and token counts when the provider supplies them. Operational error records use bounded, redacted summaries rather than full prompts or secret values. Sensitive administrator actions require confirmation and create an audit record.
Desktop companion and Discord activity
The website can connect to an installed AstraBlox desktop companion only after explicit pairing. Pairing grants access to the companion operations you request, including local Roblox Studio or Blender actions. Keep the pairing token private and rotate it if exposed.
Native Discord Rich Presence requires the desktop application and a running Discord client. It is optional. Project-name sharing is controlled separately and is off by default. Ordinary browser sessions do not publish native Discord activity on their own.
Your controls and questions
You can sign out, disconnect providers, manage your saved projects and conversations, and control optional Discord activity in the application. For account-data or privacy requests, contact the AstraBlox owner through the AstraBlox community. Account deletion and database retention requests currently require the owner’s assistance.