Skip to content
LuxOS
HomeFeaturesGalleryDownloadLuxAIDocumentationChangesDiscord
ENCS
HomeFeaturesGalleryDownloadLuxAIDocumentationChangesDiscord
  1. LuxOS
  2. Privacy Policy

Privacy Policy

How LuxOS and its apps – including LuxOS Mail – handle your data. Last updated: 19 November 2026.

LuxOS is designed so that your data stays on your computer. Most of LuxOS works fully offline. This policy lists every case where LuxOS software sends data from your computer to a server operated by LuxOS, and the cases where it connects to third-party services on your behalf.

  1. Who is responsible
  2. LuxOS Mail and Google user data
  3. Anonymous weekly count (countme)
  4. LuxAI account and the LuxAI assistant
  5. Feedback and bug reports
  6. Updates, Store and repositories
  7. Other online features
  8. This website
  9. Your rights
  10. Changes to this policy

1. Who is responsible

LuxOS and LuxOS Mail are developed and operated by Antonín Tomeček, Czech Republic (“LuxOS”, “we”). Contact for any privacy question or request: info@lux-ai.cz. Websites: luxos.lux-ai.cz and lux-ai.cz.

We do not sell personal data, we do not show ads, and we do not use your data for advertising or profiling.

2. LuxOS Mail and Google user data

LuxOS Mail is the mail app of LuxOS. It is a desktop mail client that runs entirely on your computer and connects directly to your mail provider over IMAP (reading) and SMTP (sending). If you choose “Sign in with Google” for a Gmail or Google Workspace address, LuxOS Mail uses Google OAuth to get access to your mailbox. This section describes exactly what happens with the data LuxOS Mail receives from Google.

Data accessed

  • Gmail mailbox (scope https://mail.google.com/): your folders (Gmail labels), message headers (sender, recipients, subject, date), message bodies and attachments, and message flags such as read/unread. LuxOS Mail can change mail only when you ask it to (mark as read/unread, move to Trash, save a draft you are writing to Drafts, save a sent message to Sent, mark a message as answered). This scope is needed because LuxOS Mail is a full IMAP/SMTP mail client that also sends the messages you write: Google only allows IMAP and SMTP access with this scope.
  • Your e-mail address (scopes openid and email – userinfo.email): only to check which Google account you signed in with, so the account in LuxOS Mail matches the address you entered.

LuxOS Mail does not request access to your contacts, calendar, Drive, or any other Google data.

How the data is used

LuxOS Mail uses Google user data only to provide its user-facing mail features on your computer:

  • to download your messages and folders and show them to you in the app,
  • to keep a local copy so you can read mail offline and search it,
  • to notify you about new mail while the app runs in the background,
  • to carry out actions you take, such as opening a folder, marking a message as read or unread, or moving it to Trash,
  • to send the messages you write (with their attachments) through Google’s mail server smtp.gmail.com, only when you press Send – including replies and forwards, and messages that waited in the Outbox while you were offline.

LuxOS Mail does not use Google user data for advertising, for selling or sharing with data brokers or information resellers, for determining creditworthiness or for lending, or to create, train or improve any artificial intelligence or machine learning model. Nobody at LuxOS reads your mail: the data never reaches us.

Where the data is stored

  • Only on your computer. Messages you have opened or downloaded and the folder list are stored in your home folder (~/.local/share/luxos-mail) so you can read them offline. Account settings (address, server names) are in ~/.config/luxos-mail.
  • The Google refresh token is stored in your desktop keyring (Secret Service / GNOME Keyring), which is encrypted with your login password. The short-lived access token is kept only in memory. Tokens are never written to log files or ordinary files.
  • The connection between your computer and Google (IMAP, OAuth) is always encrypted with TLS.

Sharing and transfer

Google user data is never transferred to LuxOS servers or to any third party. LuxOS Mail talks to Google (accounts.google.com, oauth2.googleapis.com, imap.gmail.com, smtp.gmail.com) directly from your computer. There is no LuxOS server in between, and no part of your mail, your address or your tokens is sent to LuxOS.

The only LuxOS server LuxOS Mail contacts is https://luxos.lux-ai.cz/mail-oauth.json, to download the public OAuth client IDs of LuxOS Mail (at most once a day). This request contains no user data.

LuxOS Mail does not pass Google user data to other apps. Exceptions are only actions you take yourself – for example when you save an attachment to a folder of your choice or open it in another app.

Limited Use disclosure

LuxOS Mail's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Removing your data and revoking access

  • Remove the account in LuxOS Mail (menu → Remove address…): LuxOS Mail deletes all locally stored messages, folders and settings of the account, deletes the token from the keyring, and asks Google to revoke LuxOS Mail's access (oauth2.googleapis.com/revoke). Nothing is deleted from your Gmail mailbox.
  • Revoke access in your Google Account at any time: myaccount.google.com/permissions → LuxOS Mail → Delete all connections. LuxOS Mail then stops receiving any data and asks you to sign in again.
  • Uninstalling LuxOS Mail does not delete your home folder; remove the account in the app first, or delete ~/.local/share/luxos-mail and ~/.config/luxos-mail.

Because LuxOS does not hold any of your Google data, there is nothing for us to delete on our side – but you are always welcome to ask at info@lux-ai.cz.

Other mail providers

The same rules apply to every account in LuxOS Mail (Microsoft, Seznam, your own server and others): mail and passwords or tokens stay on your computer and go only to your mail provider. To find the server settings for a new address, LuxOS Mail asks the provider's own autoconfig address, the public Thunderbird ISPDB (autoconfig.thunderbird.net, which receives only the domain part of the address, e.g. gmail.com) and DNS.

3. Anonymous weekly count (countme)

To know roughly how many computers run LuxOS, the package manager sends one anonymous request per week when it updates the package lists: the LuxOS version, the architecture, the update channel (stable/staging) and a rough age of the installation (first week, up to a month, up to six months, longer). No identifier, user name, hardware details or IP-derived data is stored – the server only keeps weekly totals, which are public on the usage page. Requests to this address are not written to access logs. It is on by default and can be turned off in Software Update (Privacy), in the installer, or with countme = false in /etc/lux/lux.conf. Nothing is sent from the live ISO.

4. LuxAI account and the LuxAI assistant

A LuxAI account is optional. LuxOS works without it.

  • Account data: when you create an account at lux-ai.cz we store your name, e-mail address, user name, password (in a protected form), your settings (for example the answer style), the version of the terms you accepted, monthly usage of the assistant, and – if you use them – your chat history on the website and files you save to the LSL IDE cloud. On your computer the sign-in is stored in ~/.config/luxai/account.json.
  • LuxAI assistant: what you ask LuxAI, Lux Code or the LSL IDE (your messages and anything you attach, such as a screenshot or a file) is sent to the LuxAI service at lux-ai.cz to generate the answer. Conversations in the desktop app are also stored locally in ~/.local/share/luxai. Web search by LuxAI goes through lux-ai.cz and, if that is not available, through DuckDuckGo; LuxAI asks before using the network.
  • LuxOS Care (if you are signed in): when Care finds a serious problem it does not recognise, it can send the problem title, its diagnosis and the offered options to LuxAI to suggest a fix. Installing community (AUR) packages (if you are signed in): the package build script is sent to LuxAI for a safety review.
  • LuxAI mailboxes (@lux-ai.cz): the mail server logs sign-ins (account and IP address) for security, for example to block password guessing.
  • Processing of answers (AI providers): LuxAI answers are computed by language models at providers to which the LuxAI service passes the text of your request and attachments only to produce the answer: Groq, DeepInfra, Amazon Bedrock, CoreWeave, Fireworks AI, Novita AI and Together AI.
  • How long conversations are kept: conversations on the LuxAI server are kept for as long as you have an account. When you delete a conversation or close your account, it is removed from the server within 3 days – this short delay exists only to protect against abuse of the service (for example to investigate criminal activity).
  • Deleting the account: write to info@lux-ai.cz from the address of your account. You can export your data from the account settings.

LuxOS Mail never sends Google user data to LuxAI, and LuxAI has no access to the mail in LuxOS Mail.

5. Feedback and bug reports

Feedback is sent only when you press Send in the Feedback app (or confirm it in LuxAI). The report contains your message, the kind of report and the app; optionally your e-mail address for a reply, a screenshot (off by default) and system information (on by default, can be unticked): operating system and version, hardware model, CPU, graphics, memory and disk space, desktop session, language, versions of key packages and the last error lines from the system logs. Your home path, user name, computer name, e-mail addresses, IP addresses (IPv4 and IPv6), names of Wi-Fi networks and token-like strings are removed from the log lines before sending. If you are signed in to LuxAI, the report is linked to your account; otherwise it is anonymous. Reports are read only by the LuxOS developer to fix problems. There is no automatic crash reporting.

LuxOS Discord support bot. In the #support channel of the LuxOS Discord server, in messages that mention the bot in #general, and in direct messages to the bot, an AI assistant answers questions. To write an answer, the text of your message, the title of your support post and the earlier messages between you and the bot in the same thread (at most the last 12) are sent to LuxAI, our AI service, together with excerpts from the public LuxOS documentation. LuxAI passes them to the AI model provider to generate the answer; your Discord name, ID and attachments are not sent to the model. Messages that look like they contain a password, key or token are not sent. When the assistant can't answer from the documentation or hands a question to the LuxOS team, we receive an e-mail with your Discord name, the link to the thread and the beginning of your question. Reports in #bug-reports are also checked by LuxAI for missing details and then e-mailed to the LuxOS team with your Discord name, the report text (passwords, keys and tokens removed), attachment links and the message link. The bot keeps no message contents of questions: it stores only counters, thread IDs with the ID of the person who asked and, until a bug report is forwarded, its text (deleted after 30 days), and which announcements it posted. Discord itself stores messages according to the Discord privacy policy. For help from a human without the AI, write to info@lux-ai.cz.

6. Updates, Store and repositories

Updates and apps are downloaded from the LuxOS repositories (luxos.lux-ai.cz/repo), from Arch Linux mirrors, and – when you use them – from Flathub and the AUR. These requests contain no user identifiers, only what any download contains (your IP address and the requested file). The Store has no accounts, ratings or tracking.

7. Other online features

Some apps contact third-party services when you use them: Weather (Open-Meteo; your location from the time zone, or from ipinfo.io only after you agree), Maps (OpenStreetMap tiles, Nominatim and Photon search, routing and public transport services; search suggestions for Czechia and Slovakia go through luxos.lux-ai.cz/geocode without logs; My Location only after you agree: the system location service GeoClue sends the Wi-Fi networks around you – their hardware addresses and signal strength, not your traffic – to the open database BeaconDB (beacondb.net), which answers where they are; nothing is submitted back to BeaconDB, and without an answer Maps uses ipinfo.io), the network connectivity check (ping.archlinux.org), time synchronisation and the installer's time-zone detection (ip-api.com, over plain HTTP: the installer uses the answer only if it is a known time zone, otherwise you choose one yourself). These services receive only what is needed for the request and their own privacy policies apply. LuxDrop and LuxOS Companion work only in your local network or over Bluetooth.

8. This website

luxos.lux-ai.cz uses no cookies, no analytics and no third-party trackers. The light/dark choice is stored only in your browser (local storage). Like any web server, it receives your IP address with each request in order to deliver the page.

9. Your rights

Under the GDPR you have the right to access, correct, delete or export your personal data, to restrict or object to its processing, and to withdraw consent at any time. Write to info@lux-ai.cz. You can also lodge a complaint with the Czech data protection authority, Úřad pro ochranu osobních údajů. We process account data to provide the service you asked for (contract), feedback and reports on the basis of your consent, and the anonymous count on the basis of our legitimate interest in knowing how LuxOS is used.

10. Changes to this policy

If we change how LuxOS handles data, we will update this page and the date at the top. Changes to how LuxOS Mail uses Google user data will always be announced before they take effect. See also the Terms of Use.

© 2026 LuxOSDocumentationLuxAIFAQChangesUsageDiscordRepositoriesLuxOS MailPrivacyTermsKernel on GitHublux-ai.cz