Effective 20 November 2026
Privacy Policy
1. Who we are and what this covers
This Privacy Policy explains how Ainex, operated in the United States (“Ainex,” “we,” “us”), collects, uses, shares and protects personal data when you use the Ainex desktop app, the website at ainex.app and its account pages (together, the “Service”). The domain ainex.si only redirects to ainex.app.
Ainex is the controller of the personal data described here. Questions and requests: support@ainex.app.
2. Data we collect
- Account data: username, email address, a one-way hash of your password, email-verification and password-reset codes, account status and the date you joined. If you sign in with Google, your Google account ID, email address, name and profile picture (see section 4).
- Purchase and credit data: the credit pack you choose, price, currency, payment-method type (for example “card”), order status, Stripe payment identifiers, receipts, your credit balance and every credit added or used. To prevent fraud we keep one-way hashes of the Stripe customer and card fingerprint. Card numbers are entered on Stripe’s page and never reach our servers.
- Desktop app sign-ins: for each computer you sign in on, the computer name, operating system, app version, when it signed in and was last used, and the IP address of the request.
- Technical data: IP address, an approximate country and city derived from the IP address with an offline database, browser and device type, language, the pages you visit on ainex.app, timestamps, and security signals such as failed sign-ins.
- What you ask Ainex to do: your messages, picture descriptions, reference images, files or parts of files you ask Ainex to read, what Ainex searches the web for and the pages it reads for you, pictures of your screen when you turn on Computer use, and voice audio during a voice call or dictation. Section 3 explains where each goes and what we keep.
- Support messages you send us.
3. Your content: where it goes and what we keep
- Conversations with the assistant: your messages, the assistant’s working context and any file content it reads are sent through our servers to the conversation model provider and the answer is streamed back. Versions of the desktop app after 2.0.0 send them to OpenAI, which processes them in the United States; versions up to 2.0.0 send them to Alibaba Cloud Model Studio, which processes them in mainland China. We ask OpenAI not to keep the conversation and its terms say it does not use it to train models; OpenAI keeps abuse-monitoring logs, which can include conversation content, for up to 30 days. If OpenAI cannot be reached, a conversation in those versions may be sent instead to Anthropic’s Claude model through OpenRouter, so that you can keep working. OpenRouter says it does not store messages or answers unless an account opts in, and we have not opted in; Anthropic says it does not use them to train models and deletes them within 30 days, or keeps them for up to two years when they are flagged for breaking its usage policy. In app versions where you choose the conversation model, a Claude model you pick is reached the same way, through OpenRouter, a DeepSeek model you pick is reached through DeepSeek’s own service, and a Gemini model you pick is reached through Google’s Gemini API. We ask Google not to store Gemini conversations, and Google’s terms for paid use say it does not use prompts or answers to improve its products; Google logs them for a limited time to detect misuse. When you attach a document while using a DeepSeek model, the document is uploaded to DeepSeek’s file service so the model can read it, set to be deleted after one day; we keep a fingerprint of the document for a little less than that so the same document is not uploaded twice. DeepSeek’s privacy policy says it collects, processes and stores data in the People’s Republic of China, keeps it for as long as the account it came through exists, and may use it to train its models unless the account holder opts out. We do not store the content of these conversations on our servers; we record the number of tokens used and the cost so we can charge credits. Your conversation history is stored on your own computer by the desktop app.
- Pictures: your description, the settings you choose and any reference image are sent to the image model provider you select. We store the description, settings, the generated picture and its cost in your generation history on our servers so the picture can be delivered to the app and shown to you again. Before a picture is made, the description is checked for content we don’t allow: first on our own servers, then by OpenAI’s moderation service, whichever image model you picked. If a request is refused, we keep its category (for example “sexual content”) and the time for 30 days, but not the description; several refusals in a day pause picture making on the account for a day.
- Voice calls: your voice is streamed to the voice service you choose in Settings (Google, Alibaba Cloud, ByteDance Volcengine, OpenAI or xAI; Google unless you pick another) for the duration of the call. We keep a record of the call — its length, the usage the provider reports, the credits charged — and the text and audio segments the billing system needs to settle the charge. When you ask for something to be done during a call, the request is passed to the assistant on your computer as a message, like one you typed.
- Dictation: when you dictate a message, the recording is sent through our servers to Alibaba Cloud Model Studio to be turned into text, or to DeepSeek when Alibaba Cloud cannot do it. We do not store the recording or the text; we record its length so we can charge credits.
- Web search: when the assistant searches the web or reads a page for you, the search words or the page address are sent through our servers to a search provider (Exa, or Parallel when Exa is unavailable, or DeepSeek when neither is), without your name or account details. We do not store the searches or the results; we record that a search was made and its cost. The results are then read by the conversation model like the rest of the conversation.
- Files on your computer: the desktop app opens, reads or changes files and runs commands only when you ask it to. Under the default permission setting, commands run in an isolated space that can change only the folder you are working in, and the app asks for approval before anything outside it. Some actions are always refused, such as formatting disks or reading saved browser passwords. Only the content needed for the task is sent to the conversation provider.
- Computer use (off by default): when you turn it on in the desktop app, Ainex can see your whole screen and click, type and press keys in other apps to do what you ask. It asks for your agreement once, when you turn it on, and not before each step; each step is shown in the conversation. While it works it takes pictures of your screen, which are sent through our servers to the conversation model provider together with the rest of the conversation, under the same terms as above. A picture can include anything visible on the screen at that moment, including other apps and windows. We do not store these pictures on our servers. You can turn Computer use off at any time in the desktop app’s extension settings.
- Skills and extensions you add (off unless you add them): when you search the extension directory in the desktop app, your search words are sent to the official MCP Registry. When you add a skill from GitHub or another address, the app downloads it from there. An extension you add connects to the service you chose or runs on your computer, and it receives what the assistant passes to it during a conversation. Those services are run by others under their own terms. Sign-in details for an extension stay on your computer.
- We do not use your content to train our own AI models. Each provider handles the data it receives under its own terms; see section 6.
4. Google user data
If you choose “Continue with Google,” Ainex requests only the basic sign-in permissions: your Google account ID, email address, name and profile picture (the openid, email and profile scopes). We do not request access to Gmail, Google Drive, Contacts, Calendar or any other Google service.
Data accessed: your Google account ID, email address, name and profile picture. Nothing else from your Google Account.
How we use it: only to create your Ainex account, sign you in, show your name and picture on your account page, and send you service emails such as verification codes and receipts. We use it for no other purpose.
Storage and protection: it is stored in your account record in our database on servers in the United States. It is transmitted only over encrypted connections (HTTPS), access to the database is restricted to the servers that run Ainex and to authorised staff, and staff access is recorded in an audit log.
Sharing: we do not sell Google user data and do not transfer or disclose it to third parties, except to the service providers that host our servers (Alibaba Cloud) and send our email (Resend) so they can perform those services for us, and where the law requires it. It is never sent to AI model providers.
No advertising and no AI training: we do not use Google user data for advertising of any kind, do not provide it to data brokers or information resellers, do not use it to determine credit-worthiness, and do not use it to develop, improve or train artificial-intelligence or machine-learning models. Ainex does not use any Google Workspace APIs.
Retention and deletion: we keep it for as long as your Ainex account exists. When you delete your account on the Account page, your Google account ID, email address, name and picture are deleted from our database. You can also ask us to delete it by writing to support@ainex.app from your account email.
Ainex’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
You can disconnect Ainex at any time from your Google Account’s security settings (Third-party apps with account access). Disconnecting stops Google sign-in; it does not delete your Ainex account, which you can do from the Account page.
5. How we use personal data
Where the law requires a legal basis, we rely on performing our contract with you, our legitimate interests in operating a secure and reliable service, compliance with legal obligations, and your consent where we ask for it.
- To provide the Service: create and secure your account, sign in the desktop app, run the conversations, pictures, web searches, dictation and voice calls you ask for, and deliver results.
- To charge and account for credits: price each request, deduct and return credits, process purchases through Stripe, send receipts, handle refunds and disputes, and keep financial records.
- To keep the Service safe: detect fraud and abuse, block abusive sign-ups by email domain or IP address, investigate security incidents and enforce our Terms.
- To run and improve the Service: fix errors, monitor reliability and provider costs, and understand which features are used.
- To communicate with you: verification codes, receipts, security notices and answers to your requests. We do not send marketing email without your consent.
6. Service providers who process data for us
Each provider receives only what it needs for its part of the Service and processes it under its own terms and privacy notice. With conversations, voice calls and some picture requests we also send a code made from your account ID by a one-way function, never your name or email, so that a provider can deal with misuse by one account without cutting off everyone else. Model providers may keep submitted data for a limited time for abuse monitoring under their API terms. We may change providers when needed for reliability, cost or safety, and will update this list when we do.
- Alibaba Cloud: the servers that host ainex.app and our database (California, United States); Model Studio for dictation, Qwen voice calls, Qwen Image and, in desktop app versions up to 2.0.0, assistant conversations (mainland China).
- OpenAI: assistant conversations in desktop app versions after 2.0.0, and checking picture descriptions for content we don’t allow (United States).
- OpenRouter and, through it, Anthropic or a cloud provider that hosts Anthropic’s model: assistant conversations in desktop app versions after 2.0.0 while OpenAI cannot be reached, and when you pick a Claude model (United States and the other countries where they operate).
- DeepSeek: assistant conversations and the documents you attach when you pick a DeepSeek model, and dictation and web searches when the usual providers cannot be reached (People’s Republic of China).
- Google: assistant conversations when you pick a Gemini model (the countries where Google operates).
- Image model providers, only for the model you pick: OpenAI (GPT Image), Google (Gemini image models), xAI (Grok Imagine), ByteDance Volcengine (Seedream), Recraft, Ideogram, Black Forest Labs (FLUX) and MiniMax (H3-Image, mainland China).
- Voice providers other than Alibaba Cloud, only for the voice service you use: Google (Gemini Live, the default, United States), ByteDance Volcengine (Doubao), OpenAI (GPT-Live), xAI (Grok).
- Search providers: Exa and Parallel, for web searches and reading web pages (DeepSeek as listed above when both are unavailable).
- Stripe: payments, receipts and fraud screening.
- Resend: sending verification codes, receipts and service email.
- Google: “Continue with Google” sign-in.
- Cloudflare: domain name service, and bot checks on sign-up forms when enabled.
7. Cookies and local storage
The website stores your sign-in token and language choice in your browser’s local storage. We do not use advertising or cross-site tracking cookies. Stripe’s checkout page and Google’s sign-in page set their own cookies under their own policies. The desktop app keeps its sign-in tokens and settings on your computer. Clearing them signs you out.
8. When we disclose data
We disclose personal data only to the service providers in section 6; when you ask us to; to comply with law, a court order or a valid government request; to investigate fraud, security incidents or harm; to enforce our agreements; or as part of a merger, acquisition or sale of the business, in which case this Policy continues to apply. We do not sell personal data and do not share it for targeted advertising.
9. How long we keep data
When a retention period ends, we delete the data.
- Account data: while your account exists.
- Records of visits to ainex.app: deleted automatically after 90 days.
- Desktop app sign-ins: until you sign the computer out, or the sign-in expires after 30 days without use and at most one year after it began.
- Generation history and pictures: until you delete them; deleted items are kept in a trash for 10 days and then removed.
- Orders, payments and the credit ledger: as long as needed for tax, accounting, refunds, disputes and fraud prevention, which can be several years after your account is deleted.
- Support messages and security logs: as long as needed to resolve the matter and protect the Service.
10. Security
We protect data with encrypted connections (HTTPS), hashed passwords, short-lived access tokens for the desktop app with refresh tokens that can be revoked, access controls and an audit log for staff actions, and payment handling by Stripe. No system is perfectly secure; if you suspect someone has accessed your account, change your password, sign out your computers from the Account page and write to support@ainex.app.
11. International processing
Our servers are in the United States. Conversation content is processed by OpenAI in the United States, or by Anthropic through OpenRouter when OpenAI cannot be reached (desktop app versions after 2.0.0), or by Alibaba Cloud in mainland China (versions up to 2.0.0), or by DeepSeek in the People’s Republic of China when you pick a DeepSeek model, or by Google when you pick a Gemini model; pictures from MiniMax are made in mainland China; and other providers may process data in the countries where they operate. These places may have data-protection laws different from yours. Where the law requires, we rely on the providers’ contractual commitments and other lawful transfer mechanisms.
12. Your rights and choices
On the Account page you can see your credits, usage, orders and signed-in computers, change your name and password, sign computers out and delete your account.
Depending on where you live, you may have the right to access, copy, correct or delete your personal data, to restrict or object to processing, to withdraw consent, and to complain to a data-protection authority. California residents may request to know and delete personal information and will not be discriminated against for doing so; we do not sell or share personal information as those terms are defined in California law. To make a request, email support@ainex.app from your account email. We may need to verify your identity and will answer within the time the law requires.
13. Deleting your account
You can delete your account from the Account page after confirming a code sent to your email. This removes your profile, sign-in details and Google connection. Orders and the credit ledger are kept as described in section 9. To have your generation history and pictures removed too, email support@ainex.app and we will delete them. Unused credits are lost when the account is deleted.
14. Children
Ainex is intended for people aged 18 and over. We do not knowingly collect personal data from children. If you believe a child has given us personal data, contact support@ainex.app and we will delete it.
15. Changes to this Policy
We will post any change here with a new effective date. If a change materially affects how we use your personal data, we will email account holders before it takes effect.
16. Contact
Ainex, United States. Privacy questions and requests: support@ainex.app.