Back to Aelix

Aelix Germany

Privacy policy

This notice describes information used by Aelix at aelixhub.com and Aelix Red at aelixhub.red, operated by Aelix, a business registered in Germany.

Version 13 September 2026 Both site editions

Accounts and social sign-in

The two sites share account identity. Their credit balances, subscriptions and public-generation preferences are separate.

When you choose Google sign-in, Aelix requests the openid, email and profile permissions. It uses your stable Google account identifier, email address, email-verification information and name to authenticate you and create or connect your Aelix account. It does not request access to Gmail messages, Google Drive files, calendars or contacts, and does not receive your Google password.

When you choose GitHub sign-in, Aelix requests the read:user and user:email permissions to read your profile and email addresses. It uses your stable numeric GitHub account ID, your primary email address when GitHub marks it verified, and your name or username to sign you in or connect your account. A verified primary email is required to create a new account. Aelix does not request repository access or receive your GitHub password.

Aelix stores the provider identifier and its association with your account, an optional provider email, and account information such as your email, display name and creation date. The sign-in integrations do not save Google or GitHub profile photos or retain access or refresh tokens. Password accounts store a password hash; accounts created only through social sign-in have no password hash.

A matching email does not automatically connect an existing account. You can sign in with your existing method and connect Google or GitHub from Account. Your display name can be changed in Account and may identify you as the author of creations you choose to share publicly.

Creative content and purchases

The service stores prompts, selected models and settings, uploaded reference media, generated outputs, generation status and error information, and credit-usage records to run creative tools and show your history. Chat features store messages and associated attachments. SuperAgent also stores conversation summaries and saved preferences or facts in its knowledge map; these can be included as context in later model requests.

For purchases and subscriptions, Aelix keeps payment-provider identifiers, subscription information and credit transaction records. Your account email may be used for checkout and verification emails, including when it originally came from Google or GitHub sign-in.

Service providers

Google and GitHub handle their respective sign-in flows. The integrations include Vercel for hosting and media storage, Neon for the account and application database, Stripe for payments, and Resend for verification email delivery. Creative and chat requests send the relevant prompts, context and reference media to Kie.ai and the selected AI services; applicable Red tools use RunPod.

The Discord link opens a separate service. Information you choose to provide there is handled through Discord.

Public sharing and media links

If you enable public generations, future applicable outputs, prompts, settings and reference media can appear in Explore with your display name and can be viewed, downloaded or reused by others. The preference is separate on each site. Disabling it affects future creations; it does not make existing public creations private.

Uploaded and generated media use public Vercel Blob URLs. Anyone who has one of these URLs may be able to access that media, even when it is not listed in Explore. Account access controls should not be understood as making every media URL private.

Cookies and browser storage

Aelix uses a sign-in cookie to keep you signed in for up to 30 days. Social sign-in also uses temporary cookies to check that the request belongs to your browser and session. These checks last up to 10 minutes, with a separate completion cookie lasting up to 2 minutes. Temporary cookies are cleared during completion and error handling.

Browser storage also saves some drafts, model preferences and an in-progress credit-transfer attempt. The installable app's service worker caches an offline notice; its current implementation does not cache chat or API responses.

Retention and available controls

Account, history, content and transaction records are stored to provide the features described above. Confirmed Studio uploads that remain unattached are scheduled for cleanup after six hours; attached media is retained for its associated content, and cleanup is asynchronous.

You can change your display name and future public-sharing preference in Account. SuperAgent provides conversation deletion and separate editing/deletion controls for saved memories. Deleting a conversation does not itself remove separately saved memories. Signing out clears the session cookie. Removing permission for Aelix in Google or GitHub does not itself delete information already held by Aelix.

The current site does not provide a self-service account-deletion, account-export or social-provider-disconnection control. These interface limitations do not limit your statutory rights.

Support

For support, privacy questions, data-access requests or account-deletion requests, contact aelixhub@gmail.com.

Read the Terms of service