Know how your data is used.
This policy covers AIXORIN at aixorin.com: Google and email sign-in, saved AI conversations and files, paper markets, test billing, and support.
Contact AIXORIN
For privacy questions, access or correction requests, or account and data deletion requests, email aix@aixorin.com. You do not need an AIXORIN account or a working sign-in to contact us. Signed-in members can also use Support. Include enough information to identify the account or issue, but never send passwords, verification codes, API keys or card details.
Google sign-in: data accessed and used
When you choose Continue with Google, AIXORIN uses Supabase Authentication and requests only the openid, email and profile permissions. Google provides basic identity information, including a Google account identifier, email address and verification status, name, and a profile picture or other basic profile fields when available. Supabase processes this information to authenticate you. AIXORIN uses the linked authentication identifier, verified email and available name to create or link your account, display your identity, save your workspace and enforce account access. This sign-in does not request access to Gmail messages, Google Drive files, contacts or calendars. Your Google password is entered with Google, not AIXORIN.
Account and authentication storage
AIXORIN stores its account identifier, linked Supabase authentication identifier, email, available name, role, account status and preferences. Supabase also holds your authentication account and associated identity information. The authentication response, including access and refresh tokens and any provider tokens or basic profile information supplied in that response, is encrypted in AIXORIN’s server-side session storage. For email sign-up, sign-in and password recovery, your email and any password you enter are passed through AIXORIN’s server to Supabase over HTTPS; AIXORIN does not save the password in its application database. Authentication and account data are used to maintain sessions, verify access, link existing work and administer account security.
Workspace content and activity
AIXORIN saves conversation titles, messages, AI responses, selected models, supported attachments and file metadata. File processing can create extracted text, searchable chunks and analysis metadata used to retrieve relevant content for your requests. The service also stores preferences, token balances and usage, paper trades and portfolios, marketplace listings and transactions, and operational timestamps and request identifiers. Feature-interest controls record your account identifier and interaction time to track likes and aggregate interest. This information supports saved work across devices, AI responses, usage limits, account administration and the simulated markets. Paper markets and token balances are testing features and do not represent real-money investments.
AI requests and model providers
In provider mode, AIXORIN sends your current prompt, relevant saved conversation history, and applicable uploaded content or extracted file context through OpenRouter to the provider serving the selected model. Model settings and technical request metadata accompany that request. AIXORIN saves the returned answer and usage information. Google sign-in profile data and authentication tokens are not automatically added to model prompts; personal information you put in a message or file can be included in that model request. Demo responses are generated locally by the application without a model-provider request. OpenRouter and downstream providers process requests under their own policies and settings. Retention and training practices can vary; AIXORIN does not provide a universal zero-retention or no-training guarantee for those providers. See OpenRouter’s privacy policy and the selected provider’s policy before submitting sensitive content.
Support, administrators and other members
Support tickets contain your account reference, subject, messages, replies, status and timestamps. Administrators can read and respond to tickets, manage member accounts and balances, and review account activity and audit records. Other members cannot open your private conversations, uploaded files or support tickets through the application. Your display name and listing details can be visible to other members in the Token Market. Emailing aix@aixorin.com sends your address, message and any attachments through email providers, including Zoho Mail for AIXORIN’s mailbox. Those messages are used to handle your request and remain separate from the in-app support inbox.
Hosting, service providers and security
AIXORIN is hosted through ChatGPT Sites using Cloudflare Workers, D1 database storage and R2 file storage. Hosting providers process website requests and stored content; Supabase processes authentication; OpenRouter and model providers process AI requests; Zoho processes support email; and Stripe processes configured test checkout. These services may process data in locations outside your country. Network requests expose technical information such as IP address and browser/request details to the services receiving them. AIXORIN uses hashed IP-based authentication rate-limit counters, request/error codes and audit records for service operation and abuse prevention. HTTPS, account-based access checks, secure HttpOnly session cookies and encrypted server-side authentication responses are implemented safeguards. Conversations and files are processed on the server and by relevant providers, so they are not end-to-end encrypted. No system can guarantee absolute security.
Browser storage and analytics
AIXORIN uses cookies for the sign-in flow and session, and browser-local storage for interface choices such as theme and reduced motion. Clearing browser storage can remove those choices or sign you out; it does not delete server-side account records. Hosting and authentication providers may maintain operational logs and traffic information under their policies. The AIXORIN application does not include an advertising tracker or a separate third-party analytics SDK. Google identity information is used for the account functions described here, not requested for advertising or model training.
Stripe test checkout
Billing is test-only. If Stripe test checkout is configured and you start it, AIXORIN sends Stripe your account email, account reference and selected test purchase or plan details. Stripe hosts the payment form; AIXORIN does not collect card numbers. AIXORIN stores customer, checkout, subscription and invoice references, test amounts and payment status to reconcile test entitlements. Use test card details only. See Stripe’s privacy policy for its processing.
Retention and deletion
Saved workspace data remains until removed using available controls or administrative processes. Conversations and uploaded files have separate deletion controls; deleting a conversation does not delete its usage or token-accounting history or separately uploaded files. File deletion can retain file metadata and does not remove content already copied into a conversation or sent to a model provider. Account deactivation is reversible and retains records. A separate administrator-managed account-erasure process removes the linked Supabase sign-in identity, active sessions, profile fields, conversations, uploaded files and support content after prerequisite checks and successful processing. It retains a limited retired account record, accounting and billing references, security/audit records and keyed identity hashes used to enforce account blocks. Feature-interest and rate-limit records can also remain. Erasure is not a guarantee that every record, service-provider copy, log or backup disappears. AIXORIN has not established a fixed retention period for every data category or provider-held copy; provider retention is governed by the applicable service’s policies and settings.
Your choices and requests
You can edit available profile settings and delete saved conversations or files through the workspace controls. Account erasure is administrator-managed; request it at aix@aixorin.com, including if your account is paused or inaccessible. Account requests may require identity verification and resolution of active operations, orders or test billing. You can also remove AIXORIN’s Google connection in your Google Account connections; revoking Google access does not itself delete stored AIXORIN records. Questions about copies held by a service provider may also require contacting that provider. This page’s updated date identifies the current published policy.
Have a question?
Use your support inbox or email aix@aixorin.com.