ข้ามไปยังเนื้อหา

ยังไม่มีหน้านี้ในภาษาของคุณ คุณกำลังอ่านข้อความภาษาอังกฤษ

Legal

Third-party services

Services that handle data for us, and every service the app reaches on its own. Some of them see the address of your proxy, and some see your own address: each one is named with which.

Edition 3, in force since 18 October 2026

Who works with our data for us

Railway, our hosting provider, runs the site, the server and the database, so everything the server holds sits there. When downloads are open, the installers sit in open releases on GitHub, which sees the address of whoever downloads one.

Railway also logs every request to the site and the server with the IP address it came from. It shows us each entry for up to 90 days, depending on our plan with Railway.

A mail service and a payment service will be added to this page in the edition that starts sending them data.

What the app reaches through a profile's proxy

A profile with a proxy sends these requests through that proxy, and these services see the proxy's address.

  • Exit country lookup

    ipwho.is, ipinfo.io, ipapi.co, get.geojs.io, and api.ipify.org for the start page. They answer which address and country a site will see.

  • Engine component updates

    update.googleapis.com, edgedl.me.gvt1.com and the mirrors it names (redirector.gvt1.com, dl.google.com). The update check also carries the profile's language, your memory size and system version.

  • Extension updates

    update.googleapis.com, clients2.google.com and clients2.googleusercontent.com, if you installed an extension from the Chrome Web Store inside a profile: checking for and downloading its new versions, as Chrome does. The check carries the same memory size and system version as the component check, plus that extension's ID and version and the profile's language.

  • Network time

    clients2.google.com, for pages that warn about a wrong clock.

  • Google sign-in check

    accounts.google.com, the same check Chrome makes, with the Google cookies of that profile.

  • Site notifications

    android.clients.google.com and mtalk.google.com, the channel that site notifications arrive through.

  • Safe browsing lists

    safebrowsing.googleapis.com, the lists Chrome uses to warn about dangerous sites.

What the app reaches over your own connection

These requests do not go through a profile's proxy, and these services see your own address.

  • Your public IP address

    ipwho.is, ipinfo.io, ipapi.co and get.geojs.io, asked for your own address and country.

  • The proxy check on the start page

    api.ipify.org or ipwho.is, asked for your own address to compare it with the address of the profile.

  • Profiles without a proxy

    Everything in the list above goes out over your own connection.

  • Extensions from the store

    clients2.google.com, for downloading an extension and for the check for updates every few hours.

  • Network diagnostics and the clock

    1.1.1.1 (Cloudflare) and www.google.com, when you run network diagnostics or the app checks the clock.

What they receive from us

We send none of these services your email or anything else from your ARMANOS account. What they see is the request itself and the address it came from.

What there is none of

No analytics, no error reporter, no advertising network and no chat widget, on the site or in the app.

How this list is kept

A service appears on this page in the same edition that starts sending it data. The list is checked against the code of the app, the server and the site, so a new service cannot be added without a new line here.

What this page does not cover

  • It does not list the sites a profile opens, whether you open them or a flow does. Those visits are yours.
  • It does not list proxy providers. The proxy in a profile is one you chose, under your own agreement with its seller.
  • It does not list the addresses the owner of a workspace types into Event calls (webhooks). What goes there is on the Privacy Policy page.
  • It does not name the region where our hosting keeps the database. That is not stated here yet.
  • It does not say how long Railway keeps its request log on its own side beyond what it shows us. That is set by Railway.
  • It is not legal advice and does not claim compliance with any regime by name.

Where this is decided

Each line is a file you can open.

The engine's background requests and why each is kept
apps/desktop/src/lib/фон-движка.js · apps/desktop/test/фон-профиля-живьём.js
The exit country services
apps/desktop/src/lib/exitGeo.js
The store address for extension updates
apps/desktop/src/lib/обновление-расширений.js
This page against the code of the app, the server and the site
apps/web/test/чужие-службы-названы.js

Questions

Do these services get my email?
No. None of the requests on this page carries your email or anything else from your ARMANOS account.
Which of them see my real address?
The ones in the list of your own connection, and all of them for a profile without a proxy. With a proxy, the engine and the exit country services see the proxy's address.
Why does the app talk to Google at all?
The engine is built on Chromium, and these are the same background requests Chrome makes. Removing them would make a profile look different from Chrome to the sites it opens.

Editions of this document

  1. Edition 3, 18 October 2026: Named the log of requests Railway keeps, with the IP address of each request to the site and the server, and how long it can be seen.
  2. Edition 2, 12 October 2026: The line about GitHub now says it applies while downloads are open.
  3. Edition 1, 5 October 2026: First edition.

A line here is unclear?

Write to us and quote it. A legal page is worth only as much as its least clear sentence.