Privacy policy

GlirOS is built to know as little about you as possible. Your chats, prompts, files, pictures and API keys stay on your own device: we never receive or store them. There are no ads, no analytics tools and no tracking; our web servers only count how often their pages are opened, without keeping anything about who opened them (section 9). This page says exactly what we do handle, why, and for how long.

1. Who is responsible

The controller is Gliros AS, org. no. 938 729 514, Kamfjordåsen 7, 3227 Sandefjord, Norway. For anything about your data, write to contact@gliros.com.

2. The apps

The web version (www.gliros.com/app)

• The GlirOS Helper and the browser models run on your device. Chats, files, pictures, media and settings are kept only in your browser’s own storage. Clearing the site’s data in the browser deletes them. Your ratings of models (the thumbs under answers) stay on your device too.
• AI models are downloaded straight to your browser from the host shown in Settings > Models; that host sees your IP address, as with any download.
• Web search and reading a linked page go through our server, because browsers can’t fetch other sites directly. Our server passes the search words or the page address to the search engine (DuckDuckGo, or Brave, Tavily or Serper when you add your own key) and hands back the result. The search engine sees our server, not you. Results from the free search, and the pages read, are kept in a short cache that isn’t linked to you; a copy is used for at most ten minutes and then deleted: it is removed at the next search or page read on gliros.com after those ten minutes, and in any case within a day. Searches with your own key are never cached, and the key is used for that one request and never stored.
• When the web version opens, it fetches GlirOS’s tool catalogue and calendar data from tools.gliros.com (an ordinary download; nothing about you is sent).
• Fetching a skill the first time the chat needs it: an ordinary download from tools.gliros.com; the server sees that something is downloaded, not your question. The skill is then kept in this browser.
• If you choose a cloud model (Google, OpenAI, Anthropic or another provider) with your own API key, your messages go straight from your browser to that company, under its terms. That company may be outside the EEA. The key stays in your browser.
• If a tool connects to a service with your own key or account (for example API-Football in Sports lookup), its requests go straight from your browser to that service, under its terms; they don’t go through our server. The key stays in your browser, and the tool itself never sees it.

The desktop app (Windows)

• Everything runs and is stored on your PC. It is installed from the Microsoft Store, without admin rights, for your own Windows user. Microsoft handles the download and the updates under its own privacy statement. We see only what Microsoft shows every publisher: totals (for example the number of installs) and error reports that Windows sends under your own diagnostic data settings. Your ratings of models (the thumbs under answers) stay on your PC too.
• It sends nothing unless you use something that needs the network: downloading a model or add-on, the daily check of the GlirOS tool catalogue (a plain download from tools.gliros.com), fetching a skill the first time the chat needs it (an ordinary download from tools.gliros.com; the server sees that something is downloaded, not your question), web search (from your PC to the search engine), a cloud model with your own key, a tool that connects to a service with your own key (from your PC straight to that service, the key kept in Windows Credential Manager), a connector (MCP) to a service you add yourself (below), a lookup by one of GlirOS’s own tools (below), sharing a link, linking the app to your account, or refreshing a paid tool’s licence with its seller (see section 5). Settings > Security can block all network traffic.
• A connector (MCP) to a service you add yourself: what the model asks the connector, and its answer, go between your PC and that service, on its terms. If you have to sign in to the service, you do it in your browser on the service’s own page; GlirOS never sees your password. The access token the service gives is kept in Windows Credential Manager and sent only to that service. You can sign out or remove the connector in Settings.

The camera and microphone are used only when you start them (for example Take a photo in Media Studio, or speaking text in). Picture and sound are handled on your device, not sent to us, and the camera turns off when you close the view. A picture is kept only if you choose Use this photo.

Lookups by GlirOS’s own tools

Some of GlirOS’s own tools (for example Markets, Sports lookup, Weather and Laws and rules) look things up through our server at tools.gliros.com, in the web version and in the desktop app. Only what the lookup needs is sent (the words, tickers, place or date it is about), never your chat text or anything that identifies your account. Our server answers from its own copy or asks the source the tool names on its page; that source sees our server, not you. The answers are kept in a cache that isn’t linked to you: a copy is reused for a time that fits the data, from 30 seconds for live scores to 30 days for place names and dictionary entries, and is deleted at the latest 30 days after it was fetched. To limit how often each address can ask, the server counts the requests under a code made from your IP address and a secret key, never the IP address itself, and deletes the count within three hours. Our web servers’ access log (section 9) records the lookup without its words, and the tools’ own code logs neither the words nor your IP address. We do this to give you the lookup you asked for.

3. Your GlirOS account

An account is optional. If you create one, we keep:

E-mail from us. We send messages about your account, security, a change to these terms, an outage or a purchase; these can’t be switched off. Only if you say yes do we also send the newsletter, solution updates, or tips and information. Each is its own choice, and you can stop each at any time, from a link in every such e-mail or on the E-mail page of your account. We don’t track whether you open an e-mail or click its links.

We make encrypted backups of the account database every day. They are sealed to a key that is kept offline, and are kept 14 days (plus one weekly backup for 8 weeks). Something you delete can therefore remain in a backup until that backup is deleted.

4. Remote access (the relay)

When you reach your own PC from a browser, the connection is end-to-end encrypted between your browser and your PC. The relay in between only passes encrypted data on and can’t read it; it keeps nothing of what passes through, and no log of connections beyond error messages. To open the connection it checks your device’s key and a one-time ticket that is valid for 30 seconds. Your PC’s own GlirOS interface is shown inside the page through remote.gliros.com, a site of static files that stores nothing and sets no cookies; what you see there comes from your PC through the encrypted connection. Your account keeps the PC’s name, its public key and when it was last connected (without an IP address).

For GlirOS Plus we keep, per account, whether you have GlirOS Plus and until when. For the free trial we keep when it started and ended, and a one-way fingerprint (SHA-256) of the public key of each PC linked to the account, so that a trial is used only once per PC. The fingerprint is kept for two years after the trial ended, even if the account is deleted, and then deleted.

5. Paid tools from other sellers

A paid tool is sold by its maker, who is the controller for what they collect when you buy from them (see their privacy policy, linked with the tool). We don’t tell a seller who you are. To check your licence, the app contacts only the seller’s server, and only for tools you entered a licence key for, sending the licence key, the tool’s name, a random install number and the app’s version. We don’t see your payment or card details. See Paid tools.

If you sell a paid tool, we store the seller details you give in paid.json (your name or company, organisation number or “private individual”, address, country and a support e-mail) and show them with your tools in GlirOS, so buyers know who they are buying from (contract; see the creator terms). They leave the catalogue when the tool is taken out of it (at its next update, within a week), and we delete them when you delete your account.

Subscriptions you pay GlirOS for (today GlirOS Plus and the listing of a paid tool; see the subscription terms). Paddle.com is the merchant of record: it takes the payment and is the controller for the payment details, the billing address and the receipts it sends you (see Paddle’s privacy notice). We send Paddle your account e-mail address to prefill the checkout, and a random reference. If you change your account’s e-mail address, we also change it at Paddle, but only where Paddle still has your old account address; if you gave Paddle a different address at checkout, we leave it. From Paddle we keep the subscription’s and the customer’s ids, the status, the paid period and when it renews, ends or was refunded, and from our side when you accepted the terms. We never see your card. Why: to provide what you pay for (contract) and to keep the accounts the law requires (legal obligation). The subscriptions are in your data download. When you delete your account they are cancelled first; the rows then stay without the link to you, for the bookkeeping.

6. The community forum (community.gliros.com)

• We keep the display name you choose (never your e-mail address), your posts and edits with their times, reports you make, and any moderation of your posts or account. Posts can only be read by signed-in members.
• Why: to run the forum (contract) and keep it safe (legitimate interest).
• You can delete your own posts at any time; the text is removed. When you delete your account, your posts stay, but are anonymised: they show “Deleted user”, and your display name and the link to you are removed. So no one else can take your name straight away, we keep a code made from it (not the name itself) for 90 days. Your posts are included when you download your data.
• Reports are kept until they are handled and 90 days after; moderation actions are in the 30-day security log.
• Community tools (community.gliros.com/tools): when you list a tool, we keep what you enter (name, description, category, languages, the links to the file, a screenshot and your support contact), the tool’s id, version and fingerprint (SHA-256), whether it uses the internet, and when it was checked. Our server downloads the file from your host when you list it and once a night to check it, and keeps nothing of the file. Your listings are shown under your display name. They are deleted with your account, and included when you download your data. See the community tool terms.

7. Support (support.gliros.com)

Reading the articles needs no data from you and sets no cookies. If you use the contact form, your e-mail address, your name if you give it, the topic and your message are e-mailed to support@gliros.com through our mail queue (removed from the queue within a day) so we can answer you (legitimate interest; contract where it concerns your account). Messages are kept in the support mailbox for up to 6 months and then deleted. Nothing else from the form is stored. We never ask for ID or photos of you. If you send them anyway, we delete the attachment.

Send a report in GlirOS (the desktop app and the web version) is only sent when you choose to, after GlirOS shows you exactly what will go: the kind of report, your words, for a report about an AI answer also that answer, an e-mail address if you add one for an answer, the GlirOS version and platform, and the diagnostics text shown in the preview (for example recent error messages). It goes to support.gliros.com and is read by us in our admin site, with a short notice to support@gliros.com. It is not linked to your account, and no IP address is stored with it (the limit on how many reports can be sent keeps only a hashed value, for at most two days). We use it to fix problems and improve GlirOS (legitimate interest). Every report is deleted 90 days after it came in. GlirOS itself sends no analytics: nothing is sent unless you send a report.

8. Shared links (tools.gliros.com)

When you choose to share a tool’s result, we store what you share (the snapshot, its title, the tool’s name and version, the language and the dates) and show it to anyone who has the link until it expires (1 hour to 30 days, you choose), after which it is deleted. You can delete it earlier. Reports about a shared link are stored until they are handled. No IP address is stored, except in hashed rate-limit counters for about an hour.

Only signed-up users can share (an account with a confirmed e-mail address). The snapshot is sent to tools.gliros.com together with a one-hour token that carries an opaque account id (no e-mail address and no name), so the site can apply its limits and act on reports. It is kept until it expires or you delete it. Our account server counts how many tokens each account was given in the last 24 hours (not their content) and deletes the count after two days.

9. Server logs, and the status page

Our web servers write a standard access log (IP address, time, the address requested and the browser description) for security and operation (legitimate interest). It is kept for up to 30 days. Search words and page addresses from the web version are sent in the body of the request, so they are not part of the log. status.gliros.com shows only the state of our services and collects nothing about visitors.

Page counts. Our sites (www, support, community and the account pages) count the pages they serve: per hour, which site and which kind of page, whether the visitor was signed in or not, whether the request came from a search engine or other robot, the country and, if the visitor came through a link from another site, only that site’s name (for example github.com), never the rest of its address. The country is looked up from the IP address on our own server at that moment (with the free DB-IP country list, no outside service); the IP address itself is not stored with the count. Nothing else is kept: no account, no cookie, no browser description, and the counts cannot be linked to you or to each other. We use them to see how much the sites are used and to plan the servers (legitimate interest). Hourly counts are merged into daily counts after 90 days, and deleted after five years. To know how many different visitors a site has each day, and how many of them open each kind of page, the server mixes the IP address and the browser description with a random key made for that day, and keeps only the resulting code until the end of the day (UTC); then the codes and the key are deleted, and only the day’s numbers of visitors (per site and per kind of page) remain. So visits on different days can’t be linked, and no cookie is used for it. A signed-in visit is marked as coming from a new account while the account is less than seven days old; nothing else about the account is kept with the counts.

10. Who else handles data

• Hosting of our servers: [to be filled in: hosting].
• E-mail: Brevo (Sendinblue SAS, France) sends the e-mails our services send (sign-up, password and support mails, and the newsletter, updates and tips you said yes to), and tells us when an e-mail bounced or was reported as spam; Domeneshop AS (Norway) hosts our mailboxes.
• When our team uses the rewrite help on a message, its subject and text (never who it goes to) are sent to the AI company chosen in our admin settings.
• Only when you choose them: cloud AI providers, search engines (Brave, Tavily, Serper, your own SearXNG server; DuckDuckGo through us), model hosts, connectors (MCP services) you add, services a tool connects to with your own key or account (for example API-Football in Sports lookup), and sellers of paid tools — each under its own terms. Some of them are outside the EEA (for example in the USA); the transfer happens because you choose to use them.

We don’t sell data and don’t share it with anyone for advertising.

11. Cookies

We use only the cookies that are needed for signing in and for protecting forms, and no cookies at all on www.gliros.com, support.gliros.com, status.gliros.com and tools.gliros.com. That is why there is no cookie banner. The full list is on the cookies page.

12. Your rights

• Access and portability: home.gliros.com > My data > Download my data gives you everything linked to your account, including your forum posts, as a file.
• Deletion: home.gliros.com > My data > Delete my account deletes the account at once (forum posts are anonymised, see section 6).
• Correction, restriction, objection and anything else: write to contact@gliros.com. We answer within one month.
• You can complain to Datatilsynet, the Norwegian Data Protection Authority (datatilsynet.no).

13. Age

You must be at least 13 to create an account or use the forum. The apps themselves can be used without an account.

14. How we protect data

HTTPS everywhere; passwords hashed with argon2id and a secret key; sign-in, e-mail and linking tokens stored only as hashes; a separate database user with the least rights for each site; encrypted backups sealed to an offline key; access to our admin tools restricted and protected by two-step sign-in; remote access end-to-end encrypted. What is kept on your device can be read by others who use the same Windows account or browser. Use a private window on a shared computer, and lock your PC.

15. Changes

If we change how we handle data, we update this page and its date first, and e-mail account holders about changes that matter.